What Is BSOD Code E3?

Maybe your like

Menu Log in Sign up

Home
Forums
Software, Programming and Coding
Operating Systems
Windows
Crash Analysis and Debugging

Eeyore888

As in the title, what is BSOD code e3? Don't remember ever getting this one before... I had media player open with a paused video, firefox, and running FAH with beta flags i7 4770k @ 4.3ghz 1.2v 55c load temp Z87-UD5H bios F6j G.Skill trident x 1866 @ 2133 10-11-10-27 1.68v 2x 660ti @ stock with 100% fan running 65c and 60c load temp Corsair Force 3 120g OS SSD G.Skill Phoenix III 240g storage SSD Win 7 ultimate 64 I know the other codes from a site that help a lot for OC'd systems... " 0x101 = increase vcore 0x124 = increase/decrease vcore or QPI/VTT... have to test to see which one it is 0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore 0x1E = increase vcore 0x3B = increase vcore 0x3D = increase vcore 0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage 0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances 0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x 0x109 = Not enough or too Much memory voltage 0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU) 0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r " https://forum.lowyat.net/topic/2833263/all #1 · Jul 29, 2013 As in the title, what is BSOD code e3? Don't remember ever getting this one before... I had media player open with a paused video, firefox, and running FAH with beta flags i7 4770k @ 4.3ghz 1.2v 55c load temp Z87-UD5H bios F6j G.Skill trident x 1866 @ 2133 10-11-10-27 1.68v 2x 660ti @ stock with 100% fan running 65c and 60c load temp Corsair Force 3 120g OS SSD G.Skill Phoenix III 240g storage SSD Win 7 ultimate 64 I know the other codes from a site that help a lot for OC'd systems... " 0x101 = increase vcore 0x124 = increase/decrease vcore or QPI/VTT... have to test to see which one it is 0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore 0x1E = increase vcore 0x3B = increase vcore 0x3D = increase vcore 0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage 0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances 0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x 0x109 = Not enough or too Much memory voltage 0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU) 0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r " https://forum.lowyat.net/topic/2833263/all See less See more Sort by Oldest first Oldest first Newest first Most reactions #2 · Jul 29, 2013 Hi, e3 = 0xE3: RESOURCE_NOT_OWNED in regards to its bugcheck. Essentially it means that a thread tried to release a resource it did not own. It's more than usually related to a device driver issue. Do you have the dump to attach? I can take a look for you. Regards, Patrick #3 · Jul 30, 2013 I've never had to save the dump, so I don't know where or how to. Could it just be that a thread was corrupted while Folding@Home was running? #4 · Jul 30, 2013 If you're generating minidumps, they are located in %systemroot%\Windows\Minidump #5 · Jul 30, 2013 File extension dmp? #6 · Jul 30, 2013 Correct. Zip any dumps in that directory up and attach here. #7 · Jul 30, 2013 Minidump.zip 56k .zip file Those are the last three entries on their. I believe the most recent is e3 and the other two are from 124 which is vcore being too low. I've increased vcore since and haven't had a 124 BSOD yet.

Attachments

Minidump.zip 56.4 KB Views: 50

#8 · Jul 30, 2013 Hi, Latest dump is of the RESOURCE_NOT_OWNED (e3) bugcheck. If we take a look at the callstack: Code: Code: 7: kd> kv Child-SP RetAddr : Args to Child : Call Site fffff880`0498b668 fffff800`02cdd324 : 00000000`000000e3 fffffa80`0fc80ef0 fffffa80`10b0f4b0 fffffa80`0d234230 : nt!KeBugCheckEx fffff880`0498b670 fffff880`04a6b11c : fffffa80`108fe000 00000000`753b2450 fffffa80`108fe000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x19edc fffff880`0498b6d0 fffff880`04a9f05e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`0498b810 : dxgkrnl!DXGADAPTER::ReleaseDdiSync+0x34 fffff880`0498b700 fffff880`04a92093 : 00000000`ffffd833 00000000`00000000 fffff880`0498bb60 00000000`00000003 : dxgkrnl!DXGADAPTER::DdiEscape+0x15e fffff880`0498b730 fffff960`001e1822 : 00000000`0008ec80 fffffa80`10b0f4b0 00000000`7efdb000 00000000`00000020 : dxgkrnl!DxgkEscape+0x7af fffff880`0498bab0 fffff800`02c7ee93 : fffffa80`10b0f4b0 fffffa80`10b0f4b0 fffff880`0498bb60 00000000`00000000 : win32k!NtGdiDdDDIEscape+0x12 fffff880`0498bae0 00000000`7540148a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0498bae0) 00000000`0008e2e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7540148a We can see that we have dxgkrnl (Direct X Kernel) calls being made. The process running at the time of the crash was: Quote:

PROCESS_NAME: FahCore_17.exe Click to expand...

With this said, it likely was at the time due to your overclock being unstable and not properly handling load. Have you had it since? If not, nothing too much to worry about. It's difficult to troubleshoot overclocked systems. Regards, Patrick #9 · Jul 30, 2013 I haven't bumped up the vcore since. But I have bought an air condition so my load temps are down 10c xD Thank you for the help! Insert Quotes Post Reply

posts 28M members 617K Since 2004 The premier forum for overclocking experts and enthusiasts. Discuss hardware optimization, custom builds, benchmarking, cooling solutions, and pushing the boundaries of computing performance. From beginner guides to extreme overclocking, join our technical community to master system tuning. Show Less Full Forum Listing Explore Our Forums Intel CPUs Hardware News NVIDIA PC Gaming Water Cooling