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: Random BSOD, error 0x0000001e KMODE_EXCEPTION_NOT_HANDLED ntoskrnl.exe

15 Oct 2011   #1

Windows 7 Ultimate x64
 
 
Random BSOD, error 0x0000001e KMODE_EXCEPTION_NOT_HANDLED ntoskrnl.exe

Hi!

Since I've upgraded my PC with a new motherboard, CPU, a second Nvidia GTX 580 graphics card (to make it SLI) and a cooler system for the CPU, I've been having random BSOD crashes.

I reinstalled my OS after changing the hardware, and since then I've been having these BSOD.

The BSOD refers the cause to a driver named ntoskrnl.exe.
I've included the DMP files and a system health report on this message.

You can find my system spec on my profile.

Thank you for your help guys!


My System SpecsSystem Spec
.

15 Oct 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by riotpowder View Post
Hi!

Since I've upgraded my PC with a new motherboard, CPU, a second Nvidia GTX 580 graphics card (to make it SLI) and a cooler system for the CPU, I've been having random BSOD crashes.

I reinstalled my OS after changing the hardware, and since then I've been having these BSOD.

The BSOD refers the cause to a driver named ntoskrnl.exe.
I've included the DMP files and a system health report on this message.

You can find my system spec on my profile.

Thank you for your help guys!
These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*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 or 6 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.

RAM - Test with Memtest86+



2-Driver verifier

Quote:
I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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 (an estimate on my part).

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.
Driver Verifier - Enable and Disable
My System SpecsSystem Spec
21 Oct 2011   #3

Windows 7 Ultimate x64
 
 

It seems to be that the problem has been solved.
After upgrading the firmware on my SSD (OCZ Vertex 3), I haven't been experiencing any BSOD's since then (four days ago).

Thanks anyway guys!
My System SpecsSystem Spec
.


Reply

 Random BSOD, error 0x0000001e KMODE_EXCEPTION_NOT_HANDLED ntoskrnl.exe




Thread Tools



Similar help and support threads for2: Random BSOD, error 0x0000001e KMODE_EXCEPTION_NOT_HANDLED ntoskrnl.exe
Thread Forum
BSOD Seemingly At Random, error KMODE_EXCEPTION_NOT_HANDLED BSOD Help and Support
BSOD | KMODE_EXCEPTION_NOT_HANDLED | ntoskrnl.exe+7cd40 | 0x0000001E 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
BSOD! Error 0x0000001e. Someting with ntoskrnl.exe BSOD Help and Support
Random BSOD's, error 0x0000001e, 0a, caused by ntoskrnl.exe+7cc40 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 10:23 AM.
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