|29 May 2012||#1|
| || |
BSOD ntoskrnl.exe (nt+0x66580), any insight would be helpful
Hi, Seven forum users. I could really use some help in identifying why my brand-new i5 rig keeps crashing.
I'm running a fresh install of Win 7 on a new solid state drive. The installation was from Win 7 Home Premium DVDs.
I did run the BSOD Dump & System File Collection app (EXE file) , as per the posting instructions here. Alas, the Windows_NT6_BSOD_jcgriff2 was not generated, so I am only enclosing my last 4 minidump files in zip format.
-64 bit Win 7 Home Premium, installed from oem DVD 3 weeks ago.
-hardware is essentially brand new
-Intel i5-2500K @ 3.3 GHz
-Asus mobo, AMD 6800 eyefinity radeon video card
This is a copy-paste of my most-recent WhoCrashed dump analysis report:
On Tue 5/29/2012 9:50:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052912-31699-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800455FD60, 0xFFFF, 0x0)
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
|My System Specs|
|29 May 2012||#2|
| || |
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.
*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.
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/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"IRP Logging and Force Pending I/O Requests. 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.
Driver Reference Table (DRT)
Using Driver Verifier (Windows Drivers)
|My System Specs|
|Similar help and support threads for2: BSOD ntoskrnl.exe (nt+0x66580), any insight would be helpful|
|Random BSOD Reporting ntoskrnl.exe+75c40 & ntoskrnl.exe+7efc0||BSOD Help and Support|
|Laptop stuck in BSOD boot loop; StartupRepair, other tools not helpful||BSOD Help and Support|
|WLM & Insight Not Working||Browsers & Mail|
|This confounds me. Requesting insight?||Chillout Room|
|Insight to having 2 monitors....||Chillout Room|
|need some insight on this..||Performance & Maintenance|
|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 08:07 AM.