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: Consistent BSODs - Please Help! Have posted all necessary log files


11 Jan 2011   #1

Windows 7 Home Premium, 64-bit
 
 
Consistent BSODs - Please Help! Have posted all necessary log files

Hi,

I've been having consistent BSODs lately. I posted in this thread and the problem appeared to be an Intel driver.

However, I've updated that driver and I'm still having BSODs.

I've posted the 2 latest minidump files (minidump1 and 2) and the 2 latest perfmon/Windows_NT6_BSOD_jcgriff2 files in this message (diagnosis1 and 2).

Thank you very much in advance for your help!

My System SpecsSystem Spec
.

11 Jan 2011   #2

64-bit Windows 8.1 Pro
 
 

The dmp(s) point to ntkrnlmp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. We need to enable Driver Verifier to help pinpoint the faulting module...

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

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050033, 406f8, fffff80002c92ec0}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Followup: MachineOwner
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050033, 406f8, fffff80002c42ec0}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Followup: MachineOwner
---------
My System SpecsSystem Spec
11 Jan 2011   #3

Windows 7 Home Premium, 64-bit
 
 

Hi,

What do I do if it crashes? Is there a file or something I should load afterwards to show the cause?

And what do I do if it doesn't crash?

What I'm trying to ask is: what is the point of the verifier? Do I follow it up by running some kind of analysis file that will tell the actual cause?

I haven't noticed anything specific that causes it. For instance, yesterday when there was the BSOD, I wasn't even using it at the time - I came back to the laptop to find the "Windows has recovered from a serious error" message.
My System SpecsSystem Spec
.


11 Jan 2011   #4

64-bit Windows 8.1 Pro
 
 

We are trying to crash the system .. that is the reason we are enabling driver verifier ... we use software available from Microsoft that enables us to read the .dmp files, and hopefully fix your problem ... it is call wndbg and is freely available ... but we need the new .dmp files from c:/windows/minidump ... once your system crashes, you need to upload the new ones as an attachment to your next post...
My System SpecsSystem Spec
11 Jan 2011   #5

Windows 7 Home Premium, 64-bit
 
 

Ok, will do that.

Thanks very much for your help, and I'll post the next minidump file when the system crashes.
My System SpecsSystem Spec
11 Jan 2011   #6

Windows 7 Home Premium, 64-bit
 
 

Hi,

I tried running the Driver Verifier.

When I restarted the computer, the first time it told me that Windows failed to start up and asked if I wanted to launch Windows Repair or start normally. I chose start normally.

Then on the next restart, there was a BSOD before I could even load firefox to post here. The error was:

Invalid_kernel_handle

The BSOD didn't restart the computer itself like it normally does, so I had to turn it off. However, when the computer loaded again there wasn't any minidump file.

Then, it has BSOD'd again. This time it says: A device driver attempting to corrupt the system has been caught. The fauly driver currently on the kernel stack must be replaced with a working version.

The computer hasn't restarted again automatically and I doubt there'll be a minidump when I force the shutdown.

Please could you tell me what I can do now? How do I turn off the verifier to stop the BSODs and how can I get a minidump file when it won't restart automatically (it's just frozen after Collecting data for crash dump and Initializing disk for crash dump).

Thanks.
My System SpecsSystem Spec
11 Jan 2011   #7

64-bit Windows 8.1 Pro
 
 

boot into safe mode, and check for the minidump file... then disable driverfier...
My System SpecsSystem Spec
11 Jan 2011   #8

Windows 7 Home Premium, 64-bit
 
 

Hi,

I'm in safe mode at the moment but as mentioned, there are no minidump files because the BSODs won't restart themselves.

How can I get a minidump when the BSODs freeze?

And how can I disable driver verifier?
My System SpecsSystem Spec
11 Jan 2011   #9

64-bit Windows 8.1 Pro
 
 

My System SpecsSystem Spec
11 Jan 2011   #10

Windows 7 Home Premium, 64-bit
 
 

Ok,

I've done that now and I'm going to restart.

What should I do now to diagnose the problem seeing as though this route didn't work?
My System SpecsSystem Spec
Reply

 Consistent BSODs - Please Help! Have posted all necessary log files




Thread Tools



Similar help and support threads for2: Consistent BSODs - Please Help! Have posted all necessary log files
Thread Forum
Random Restarts 4 Dump Files Posted BSOD Help and Support
Solved Various BSODs are back, not consistent, seems random BSOD Help and Support
Solved Consistent BSODs, Inconsistent STOP codes, and more BSOD Help and Support
Solved BSOD! Please help? Files included & posted according to instructions. BSOD Help and Support
Solved Consistent BSODs for over a year. BSOD Help and Support
Consistent BSODs for Gaming & Video BSOD Help and Support
Consistent BSODS and Hard Freezes 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 12:50 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