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 associated with ntoskrnl.exe file

16 May 2012   #1
aruv

64 bit
 
 
Random BSOD associated with ntoskrnl.exe file

I ran the program BlueScreenView and it noted that the cause of my random BSOD crashes was associated with ntoskrnl.exe. Yet when I did a google search online there was no definitive answer as to why this is occurring.
I have attached the files, per the tutorial, and I'm hoping this forum could help me narrow this problem down.

My system (1 week old)
ASRock Z77 Extreme4
i3-2100
G.Skill 8GB Ram
Crucial M4 main drive (WD EARS(2tb), Hitachi(2tb), Seagate (2tb), and 2 external 3TB drives)
Using SpeedFan I haven't noted a single heat issue.
OS is Windows 7 x64
It is a Dell OEM version.

Any help would be great.


My System SpecsSystem Spec
.
16 May 2012   #2
JMH

Win 7 Ultimate 64-bit. SP1.
 
 


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 a 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.

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/Win7 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"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these

- Concurrency Stress Test
- DDI compliance checking

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.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)


Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)
My System SpecsSystem Spec
17 May 2012   #3
aruv

64 bit
 
 

Thank you for the reply. Ran Memtest86 and immediately I had 100k errors. Shut computer off and pulled one stick out, reran test and let Memtest run for 15 minutes no errors. Took suspected bad stick, put in a different slot, ran test, and boom 100k errors in less than 5 minutes. Emailed GSkill for an RMA. Thanks.
My System SpecsSystem Spec
.

17 May 2012   #4
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

Good luck!
My System SpecsSystem Spec
Reply

 Random BSOD associated with ntoskrnl.exe file




Thread Tools




Similar help and support threads
Thread Forum
BSOD random most times ntoskrnl.exe+748c0 and ntoskrnl.exe+74ec0
BSOD random, probably under heavy load situations. I dont know how to do. DM log collector file attached many thanks
BSOD Help and Support
Random BSOD error driver ntoskrnl.exe (address ntoskrnl.exe+74ec0)
Hey guys so I've been getting some random BSOD errors every few days or so. I usually leave my computer on when I am at work or sleep and either when I come home or wake up my computer is off. So I turn it on and it says that the computer didn't shut down properly when I start up. I downloaded...
BSOD Help and Support
Random BSOD's DRIVER_POWER_STATE_FAILURE ntoskrnl.exe (SF File incl)
Since the last 9 Months my PC is having BSOD’s randomly. DRIVER_POWER_STATE_FAILURE Caused By Driver: ntoskrnl.exe In the previous 9 months I spend over 200 hours trying to solve this issue but without success so posting this here is like my last hope… In Attachment my...
BSOD Help and Support
Random BSOD Reporting ntoskrnl.exe+75c40 & ntoskrnl.exe+7efc0
I'm getting random Blue Screens and can't figure out why. I'm not running any hardcore programs. I'm mostly just using Microsoft Office and Firefox. The BSOD's seem to happen when I'm in Outlook, Excel or Firefox. Haven't been able to determine exactly which at the time as I'm moving back and...
BSOD Help and Support
BSOD ntoskrnl.exe file
Hello, recently I've been getting BSoDs constantly lately and I have gotten nowhere near fixing this I feel like. When I run "WhoCrash" and analyze the dump file(s), I get this reading: On Fri 11/16/2012 9:26:10 PM GMT your computer crashed crash dump file: ...
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 19:39.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App