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 - NTOSKRNL.EXE (KMODE_EXCEPION_NOT_HANDLED) on Fresh OS Install

05 Sep 2011   #1

Microsoft Windows 7 Enterprise 64-bit 7601 Multiprocessor Free Service Pack 1
 
 
BSOD - NTOSKRNL.EXE (KMODE_EXCEPION_NOT_HANDLED) on Fresh OS Install

I got BSOD while I was watching a movie on Netflix and playing World of Warcraft. I was setting up my settings for Media Monkey and got this blue screen of death.
I recently did a fresh install on my computer no more than a week ago. I am running Windows 7 Enterprise 64 Bit with Service Pack 1. I have all the latest updates and drivers installed. My PC specs are in my profile as well.

My System SpecsSystem Spec
05 Sep 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Mmatus89 View Post
I got BSOD while I was watching a movie on Netflix and playing World of Warcraft. I was setting up my settings for Media Monkey and got this blue screen of death.
I recently did a fresh install on my computer no more than a week ago. I am running Windows 7 Enterprise 64 Bit with Service Pack 1. I have all the latest updates and drivers installed. My PC specs are in my profile as well.

These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem. (possibly from your RTCORE64.SYS FROM 2005)


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
07 Sep 2011   #3

Microsoft Windows 7 Enterprise 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

I did the memory test, memory came back good. I uninstalled the RTCORE64.sys that came with MSI afterburner and it seemed to be working. I tried the Driver Verifier, followed the instructions, and got another blue screen. It wouldnt even get past the Starting Windows Screen. I did a fresh OS install and I got another blue screen today saying this.

Dump uploaded below.

P.S. I'm starting to suspect it might be an OC issue. I had the PC running real smooth at 3.9 ghz. I stressed test the ram and the CPU for 6 hours straight and worked nicely. When I tried to bump it to 4.0 i stressed tested it for 3 hours and I assumed it worked fine. I am testing more with it. Any info on the minidump would also be helpful.
My System SpecsSystem Spec
.


Reply

 BSOD - NTOSKRNL.EXE (KMODE_EXCEPION_NOT_HANDLED) on Fresh OS Install





Thread Tools



Similar help and support threads for2: BSOD - NTOSKRNL.EXE (KMODE_EXCEPION_NOT_HANDLED) on Fresh OS Install
Thread Forum
Solved Random BSOD on fresh installed Desktop: (ntoskrnl.exe) BSOD Help and Support
BSOD ntoskrnl.exe fresh windows 7 install BSOD Help and Support
BSOD playing Guild Wars 2, recent SSD install and fresh install of W7 BSOD Help and Support
Solved BSOD on fresh install when install updates, misc error codes BSOD Help and Support
BSOD after fresh install, ntoskrnl.exe BSOD Help and Support
Fresh Install...NTOSKRNL.exe? BSOD Help and Support
Random BSOD - Fresh install, fresh system 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:49 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