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

[lunarsea]

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!

 

[Tews]

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

*******************************************************************************
*                                                                             *
*                        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
---------

 

[lunarsea]

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.

 

[Tews]

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

 

[lunarsea]

Ok, will do that.

Thanks very much for your help, and I'll post the next minidump file when the system crashes.

 

[lunarsea]

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.

 

[Tews]

boot into safe mode, and check for the minidump file... then disable driverfier...

 

[lunarsea]

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?

 

[Tews]

View attachment 131087

 

[lunarsea]

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?

 

[Tews]

Ill call in some help from one of out BSOD experts...

 

[Jonathan_King]

Hello,

Enable driver verifier again, and this time just keep trying to use the computer; sometimes it may take as many as six tries, but if you get to 10 with no luck, give up on it.

After your system generates a dump, or if you get to 10 tries without one, upload a full system report: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Perhaps Event Logs will contain helpful clues.

Also, ZoneAlarm may be at fault here. Install this hotfix: http://support.microsoft.com/kb/981180

If that doesn't help, uninstall ZoneAlarm and Avira. Replace them with MSE: http://www.microsoft.com/security_essentials

MSE will ask to turn on the Windows Firewall; click Yes to allow it.

 

[lunarsea]

Hello,

I have applied the hotfix so hopefully that will fix the problem. If not, I'll enable driver verifier again and post the results here if/when I get any.

Thank you both very much for your help.