Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD | KMODE_EXCEPTION_NOT_HANDLED | ntoskrnl.exe+7cd40 | 0x0000001E


03 Apr 2012   #1

Windows 7 Ultimate x64 SP1
 
 
BSOD | KMODE_EXCEPTION_NOT_HANDLED | ntoskrnl.exe+7cd40 | 0x0000001E

I've been getting the same BSOD for the past couple of days.

Things I've already done (to no avail):
  • Ran memtest 4.20 overnight - NO ERRORS
  • Replaced avast antivirus with Microsoft security essentials
  • Ran a quick scan with MSE - NO PROBLEMS
  • Updated ATI drivers to latest Catalyst 12.3
My specs are the following:
  • Custom built PC, less than 2 months old
  • Motherboard: Gigabyte 880GM-UD2H
  • Windows 7 Ultimate x64 SP1 OEM
Any help would be greatly appreciated. This is driving me crazy.


BSOD dumps attached.

My System SpecsSystem Spec
.

03 Apr 2012   #2

Win 8 Release candidate 8400
 
 

Since your ram appears to be ok I would start with driver verifier.
These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.


* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.




Memtest.
Quote:
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



Driver verifier

Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
My System SpecsSystem Spec
Reply

 BSOD | KMODE_EXCEPTION_NOT_HANDLED | ntoskrnl.exe+7cd40 | 0x0000001E




Thread Tools



Similar help and support threads for2: BSOD | KMODE_EXCEPTION_NOT_HANDLED | ntoskrnl.exe+7cd40 | 0x0000001E
Thread Forum
BSOD related to KMODE_EXCEPTION_NOT_HANDLED caused by ntoskrnl.exe BSOD Help and Support
BSOD while gaming, KMODE_EXCEPTION_NOT_HANDLED ntoskrnl.exe BSOD Help and Support
Solved BSOD While Idle or playing, ntoskrnl.exe+7cd40 BSOD Help and Support
KMODE_EXCEPTION_NOT_HANDLED ntoskrnl.exe 0x0000001e BSOD Help and Support
Random 0x0000001e KMODE_EXCEPTION_NOT_HANDLED BSOD Help and Support
Solved Random BSOD, error 0x0000001e KMODE_EXCEPTION_NOT_HANDLED ntoskrnl.exe BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 02:05 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33