Repeat OS install BSOD

[raffiican]

Hello; I am new to the forum and have tried to follow the guidelines for posting this crash, however if I have missed anything I apologize in advance.

I have fresh-installed the OS on 3 different drives, having had failures (BSOD) on all three at some point during windows updates, or when installing other programs. This happens very quickly after installing the OS, and I suspect a hardware issue.

Windows 7 Home Premium 64-bit OEM OS (as purchased with MOBO/HDD and installed by me)

Installation is fresh, and tried on multiple drives with formatting
tried Memtest for hours...passed
tried OCCT tests on GPU and CPU...always passes with no errors
main BSOD comes when doing windows updates after fresh install.
Zip dump folder attached.

Thanks in advance to anyone with help on this issue....the PC is completely unusable as it is and I really appreciate any help!

Mike.

 

[zigzag3143]

Hello; I am new to the forum and have tried to follow the guidelines for posting this crash, however if I have missed anything I apologize in advance.

I have fresh-installed the OS on 3 different drives, having had failures (BSOD) on all three at some point during windows updates, or when installing other programs. This happens very quickly after installing the OS, and I suspect a hardware issue.

Windows 7 Home Premium 64-bit OEM OS (as purchased with MOBO/HDD and installed by me)

Installation is fresh, and tried on multiple drives with formatting
tried Memtest for hours...passed
tried OCCT tests on GPU and CPU...always passes with no errors
main BSOD comes when doing windows updates after fresh install.
Zip dump folder attached.

Thanks in advance to anyone with help on this issue....the PC is completely unusable as it is and I really appreciate any help!

Mike.

Mike Hi and welcome


These were all caused by memory corruption. Possibly because of your avg.


I would run memtest ad remove AVG ad replace with Microsoft security essentials.

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.



AVG - Download tools

http://www.microsoft.com/security_essentials/

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\032311-21840-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02859000 PsLoadedModuleList = 0xfffff800`02a9ee90
Debug session time: Thu Mar 24 02:42:10.036 2011 (GMT-4)
System Uptime: 0 days 2:14:31.004
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 32203, 2, 130c04}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000032203, page frame number
Arg3: 0000000000000002, current page state
Arg4: 0000000000130c04, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000295ef5c to fffff800028d9640

STACK_TEXT:  
fffff880`06a486f8 fffff800`0295ef5c : 00000000`0000004e 00000000`00000099 00000000`00032203 00000000`00000002 : nt!KeBugCheckEx
fffff880`06a48700 fffff800`0288efe8 : 00000000`00020000 fffffa80`009cd860 00000000`00000000 fffff880`06a488d0 : nt!MiBadShareCount+0x4c
fffff880`06a48740 fffff800`02bea139 : fffff980`1a2c0000 fffff8a0`09558580 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2ca47
fffff880`06a48a20 fffff800`028fce9b : 00000000`00000000 fffffa80`03cdf2f0 00000000`00000000 00000000`00040000 : nt!CcUnmapVacb+0x5d
fffff880`06a48a60 fffff800`0291e464 : 00000000`00000001 fffffa80`03e9cf20 fffffa80`040e4600 fffffa80`03e9ce00 : nt!CcUnmapVacbArray+0x1bb
fffff880`06a48af0 fffff800`0291ed4e : fffffa80`040e4600 fffffa80`040e4600 fffff880`009e9180 fffffa80`03e9ce00 : nt!CcDeleteSharedCacheMap+0x154
fffff880`06a48b50 fffff800`0291f388 : fffff880`00000000 fffff880`06a48c58 fffffa80`041cc160 fffff800`02ad8101 : nt!CcWriteBehind+0x54e
fffff880`06a48c00 fffff800`028e3a21 : fffffa80`03d4fac0 fffff800`02bcff01 fffff800`02ad8180 fffffa80`00000002 : nt!CcWorkerThread+0x1c8
fffff880`06a48cb0 fffff800`02b76cce : fffff880`0318be88 fffffa80`04fcc040 00000000`00000080 fffffa80`03ceb040 : nt!ExpWorkerThread+0x111
fffff880`06a48d40 fffff800`028cafe6 : fffff880`02f63180 fffffa80`04fcc040 fffffa80`03d07680 fffff880`01239384 : nt!PspSystemThreadStartup+0x5a
fffff880`06a48d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`0295ef5c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

 

[raffiican]

Update

Hello, first off thank you so much for your reply...it is very much appreciated.

I uninstalled AVG and installed Windows Security Essentials. I had already run memtest on the system, however I tried it again per your recommendation.

What I found was that memtest would run and pass 8 times with no errors before I finally shut it down. However, the next time I ran memtest on a 'cold boot' (after sitting for hours off)...it logged errors quite soon...in fact it was 'stuck' on test #2, looping through the test logging millions of errors without moving to the next test, and would not esc out...I had to manually power down.

I completely changed the ram to some 1600mhz (2x2gb) Corsair that I have laying around and tried again...this time it ran again for 7 1/2 hours with zero errors. But once again when I restarted memtest after sitting overnight it logged errors very quickly and started looping, this time on test #3 (millions of errors counted).

It also logged errors on both slots.

I removed one stick of ram and tried again, same thing...when the pc is 'warm' it will run for hours without a fail, but 'cold-booted' memtest fails quickly, sometimes it will just log some errors (eg. 1 pass it logged 131) and keep going, other times it will get stuck in a loop and I have to power down.

I moved that stick of ram through the available slots, and switched to another stick of ram and repeated the tests, moving it through the slots (2 slots only, as my MOBO manual shows slot A1 and B1 as `single ram`slots) with the same results.

So...with 4 separate ram sticks all behaving the same way in both slots either in pairs or separately and it happening mostly cold...It would seem I have a MOBO problem...or CPU possibly. I am not sure how the CPU interacts with the ram and if it is even possible that it could be a CPU fault. I have worked the CPU over pretty hard in OCCT, however since the problem seems to mostly occur on a cold boot perhaps this isn`t a good test. What do you think...


Thanks again for your help, I really appreciate it!

Mike.