Blue Screens

Rance · 16 Apr 2011

Hello, about a week ago I did a reinstall of my OS after a series of problems. (Can read up on that here.)

So over the course of the week, I was letting things run, checking for any errors that may pop up before I attempted to get Windows re-registered with my product key and all. During that time I have ran into a couple of BSOD at different points and time, at first it seemed that the screens only happen during moments of inactivity, like the times I have my computer on and I kind of just pass out watching tv or whatever. I come back to it to shut it down and it goes BSoD on return... and only once during those time it happen right when I started up a game. Also this morning, when I turning it back on I had to go into repair mode and have the system resolve that issue before I could log back into the OS. So thats when I decided to do the full on Crash/Debugging report.

Windows 7 Set Up:
-Windows 7 x64
-Re-installation of Windows 7 Home Premium (previously OEM)
-Re-installation happen about 8 days ago.
-I got the computer itself about a year ago.

Additional info attached.

zigzag3143 · 16 Apr 2011

Rance said:

Hello, about a week ago I did a reinstall of my OS after a series of problems. (Can read up on that here.)

So over the course of the week, I was letting things run, checking for any errors that may pop up before I attempted to get Windows re-registered with my product key and all. During that time I have ran into a couple of BSOD at different points and time, at first it seemed that the screens only happen during moments of inactivity, like the times I have my computer on and I kind of just pass out watching tv or whatever. I come back to it to shut it down and it goes BSoD on return... and only once during those time it happen right when I started up a game. Also this morning, when I turning it back on I had to go into repair mode and have the system resolve that issue before I could log back into the OS. So thats when I decided to do the full on Crash/Debugging report.

Windows 7 Set Up:
-Windows 7 x64
-Re-installation of Windows 7 Home Premium (previously OEM)
-Re-installation happen about 8 days ago.
-I got the computer itself about a year ago.

Additional info attached.

Several of these point to memory corruption (probably from a driver). I would run memtest to test the memory, and run driver verifier to find out which driver.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

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.

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

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.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\041411-18423-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0324b000 PsLoadedModuleList = 0xfffff800`03488e50
Debug session time: Thu Apr 14 08:48:46.444 2011 (GMT-4)
System Uptime: 0 days 0:10:30.083
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa80054b8c20, fffffa80054b8cb0, 4090009}

GetPointerFromAddress: unable to read from fffff800034f30e0
GetUlongFromAddress: unable to read from fffff800034611b0
Probably caused by : memory_corruption ( nt!MmCleanProcessAddressSpace+244 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa80054b8c20, The pool entry we were looking for within the page.
Arg3: fffffa80054b8cb0, The next pool entry.
Arg4: 0000000004090009, (reserved)

Debugging Details:
------------------

GetUlongFromAddress: unable to read from fffff800034611b0

BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  fffffa80054b8c20 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  WmiPrvSE.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800033ee6d3 to fffff800032bb740

STACK_TEXT:  
fffff880`0bb62998 fffff800`033ee6d3 : 00000000`00000019 00000000`00000020 fffffa80`054b8c20 fffffa80`054b8cb0 : nt!KeBugCheckEx
fffff880`0bb629a0 fffff800`0328e828 : fffffa80`054b8c30 00000000`00000000 00000000`20646156 00000000`00000000 : nt!ExDeferredFreePool+0x12c4
fffff880`0bb62a50 fffff800`0359eabf : fffff8a0`0360a060 00000000`00000001 00000000`00000000 fffffa80`0846b060 : nt!MmCleanProcessAddressSpace+0x244
fffff880`0bb62aa0 fffff800`0357795b : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x92f
fffff880`0bb62b60 fffff800`032ba993 : fffffa80`086fd060 00000000`00000000 00000000`000c3901 fffffa80`0846b060 : nt!NtTerminateProcess+0x25b
fffff880`0bb62be0 00000000`770df97a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0027f6b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770df97a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MmCleanProcessAddressSpace+244
fffff800`0328e828 48f7867004000000ffffff test qword ptr [rsi+470h],0FFFFFFFFFFFFFF00h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!MmCleanProcessAddressSpace+244

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc791bd

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x19_20_nt!MmCleanProcessAddressSpace+244

BUCKET_ID:  X64_0x19_20_nt!MmCleanProcessAddressSpace+244

Followup: MachineOwner
---------