Windows_NT6_BSOD_jcgriff2 doesn't work

I'm trying to get the information needed for creating a BSOD thread. So I downloaded the Windows_NT6_BSOD_jcgriff2.exe file and started it as Admin.

I have left it running for > 10 hours. It's stuck on "Searching for Drivers"

I had a look in the command file and it's running this command

cmd /c where /r %systemdrive%\ /f /t *.sys > "%userdir%\$sys_list.txt"

So I ran this in a cmd window so I could see what's happening...
The problem seems to be that where.exe is stuck in a loop

? ? ? "C:\ProgramData\Application Data\Application Data\Application Data\Application Data\Programdata\Application Data\Programdata\Programdata\ApplicationData\Microsoft\Microsoft Antimalware\Definition Updates\{39E0C6B3-7D07-4303-8A71-377FC690083D}\MpKsl04e20958.sys"

29904 2012-01-24 04:05:23 "C:\ProgramData\Application Data\Application Data\Application Data\Application Data\Programdata\Programdata\Application Data\Application Data\Microsoft\Microsoft Antimalware\Definition Updates\{39E0C6B3-7D07-4303-8A71-377FC690083D}\MpKsl04e20958.sys"

The whole file is in attachments

Why is this happening and how do I fix it?

// Anders

In the interim you can try this method


To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Ok.
Stupid question: Should I create a new thread or should I continue on this?

// Anders

andis59 said:

Ok.
Stupid question: Should I create a new thread or should I continue on this?

// Anders

We are easy, I would continue here.

Well, I did some reasoning with myself and figured that it would be better to start a new thread. There is really two questions here.

The new thread is this:
https://www.sevenforums.com/crashes-d...ml#post1761425

Hope that this doesn't complicate things....

// Anders

andis59 said:

Well, I did some reasoning with myself and figured that it would be better to start a new thread. There is really two questions here.

The new thread is this:
https://www.sevenforums.com/crashes-d...ml#post1761425

Hope that this doesn't complicate things....

// Anders

These crashes were caused by memory corruption (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!!!


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.

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+



2-Driver verifier

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.

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

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 "Special Pool", "Force Pending I/O Requests" and "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).

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

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


These drivers need updating

Code:

RVIEg01.sys    4/13/2001 5:16:37 AM    0xbedc4000    0xbedeb2c0        0x000272c0    0x3ad6d205                        
RVIEg01VST.sys    4/13/2001 5:18:22 AM    0x8b9cb000    0x8b9f2380        0x00027380    0x3ad6d26e                        
OEM13Vfx.sys    3/5/2007 5:45:03 AM    0xa1d36000    0xa1d37d00        0x00001d00    0x45ebf4af                        
OEM13Vid.sys    5/28/2008 8:18:20 PM    0xa1cfc000    0xa1d35940        0x00039940    0x483e045c                        
aksfridge.sys    1/16/2009 5:09:32 AM    0xbec1a000    0xbec73000        0x00059000    0x49705cdc                        
Apfiltr.sys    3/24/2009 11:25:22 AM    0xa40c8000    0xa40fd000        0x00035000    0x49c90972                        
spldr.sys    5/11/2009 11:13:47 AM    0x8bfc9000    0x8bfd1000        0x00008000    0x4a084ebb                        
pavboot.sys    6/29/2009 6:49:56 AM    0x8b5cd000    0x8b5d2580        0x00005580    0x4a48aa64                        
hardlock.sys    7/9/2009 5:29:12 AM    0xbec73000    0xbed02800        0x0008f800    0x4a55c678

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Hello zigzag3143,

Thank you for the detailed description of what to do.

I have run Memtest86+ during the night (12 passes) and no errors
I'm in the process of running Verifier. Nothing has happened so far...
Although most of my BSOD has happened during night. Maybe some scheduled task that crash the system. I will see this night if anything happens...

One question. You have listed a number of drivers that you say needs updating. From where are you getting this information? I'm using DriverEasy and it says nothing about these drivers!?

// Anders

andis59 said:

Hello zigzag3143,

Thank you for the detailed description of what to do.

I have run Memtest86+ during the night (12 passes) and no errors
I'm in the process of running Verifier. Nothing has happened so far...
Although most of my BSOD has happened during night. Maybe some scheduled task that crash the system. I will see this night if anything happens...

One question. You have listed a number of drivers that you say needs updating. From where are you getting this information? I'm using DriverEasy and it says nothing about these drivers!?

// Anders

\All of the "driver sweepers" use their own proprietary database of the most current drivers. I simply look at the date of the ones installed. If they are before July 13, 2009 (windows 7 released date) they are considered old and need updating. If there are no more recent drivers then they need to be re-installed us compatibility mode to enable them to work properly in win 7

Ok, so now I have gotten BSOD (two of them)

On the first it reported
Error 0x000000C4 (0x000000E0, Ox00000040,0x00000004, 0x00000000)
It also said that a memory dump file was written. I can't find the file!?

On the second it reported
Error 0x0000007A (0xC0417DE8, 0xC0000056, 0xA219C860, 0x82FBDDE3)
This time it said:
Physical memory dump FAILED with status 0xC000009C

I then tried sysdm.cpl and checked the setting for Startup and Recovery Settings, it was set on create kernal dump so I changed it to Small memory dump (128 kB)

Now when I click on OK I get this error message

It is not certain that it is possible to record information that facilitates identification of system failure, because the current paging file is disabled, or less than 1 megabyte. Click OK to return to the screen with virtual memory settings, enable the swap file and set the size to a value larger than 1 megabyte. You can also click Cancel to change the options for memory dumping.

I checked Virtual memory and it 6336 MB

What is going on?

// Anders

NB! All Windows messages has been translated using Google Translate. I'm running a Swedish version of Windows 7 Professional SP1

andis59 said:

Ok, so now I have gotten BSOD (two of them)

On the first it reported
Error 0x000000C4 (0x000000E0, Ox00000040,0x00000004, 0x00000000)
It also said that a memory dump file was written. I can't find the file!?

On the second it reported
Error 0x0000007A (0xC0417DE8, 0xC0000056, 0xA219C860, 0x82FBDDE3)
This time it said:
Physical memory dump FAILED with status 0xC000009C

I then tried sysdm.cpl and checked the setting for Startup and Recovery Settings, it was set on create kernal dump so I changed it to Small memory dump (128 kB)

Now when I click on OK I get this error message

It is not certain that it is possible to record information that facilitates identification of system failure, because the current paging file is disabled, or less than 1 megabyte. Click OK to return to the screen with virtual memory settings, enable the swap file and set the size to a value larger than 1 megabyte. You can also click Cancel to change the options for memory dumping.

I checked Virtual memory and it 6336 MB

What is going on?

// Anders

NB! All Windows messages has been translated using Google Translate. I'm running a Swedish version of Windows 7 Professional SP1

In order to write a dmp file the page file must be as large as the ram you have, on the same HD as the OS, and UAC needs to be enabled.