Windows 7: Windows 7 - Fresh Install BSOD whilst applying windows updates

DarrenF · 12 Jan 2013

I built up a new PC before Christmas. These were the components:

Asus P8Z77-V Motherboard
Intel i5 3570K 3.4GHz
2 x G-Skill 8GB DDR3 1600Mhz
PowerColor HD 6870 1GB GDDR5 Dual DVI HDMI PCI-E Graphics Card
OCZ 120GB Agility 3 SSD

Not really used it that much and have had random crashes since built. Today, I decided to start afresh and reformatted the C drive and re-installed Windows. Although the OS installed without a hitch, at various times throughout the Windows Update process, the machine would crash a BSOD would appear.

I have attached the files as requested.

Can anyone advise me on what is the best approach to resolving this issue?

Cheers

Darren

**Arc** · 13 Jan 2013

Hello DarrenF.

Four crashes, four different stopcodes.

Code:

BugCheck 34, {50853, fffff8800317e738, fffff8800317df90, fffff80002cd1eee}

Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceSharedLite+4e )

Followup: MachineOwner
---------
BugCheck 1E, {ffffffffc0000005, fffff80002c8e284, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXRstor+0 )

Followup: MachineOwner
---------
BugCheck 1A, {31, fffffa800ef4fac0, fffff8800e0ed000, fffff8a00a7584e0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+7271 )

Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff960000f6b32, fffff8800785ffa0, 0}

Probably caused by : win32k.sys ( win32k!FreeObject+12 )

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

Whereas ntkrnlmp.exe and win32k.sys, none of them cannot be the real probable cause of a crash. Do these tests, one by one.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

DarrenF · 13 Jan 2013

Thanks for the response - I will run those test and report back when complete

DarrenF · 13 Jan 2013

Ok, so I enabled the Driver Verifier and the end result is that as soon as the PC boots up, it just freezes. I suspect I get five seconds of the desktop appearing where i can move the mouse before this happens. So no BSOD, not sure if this is good or bad news and the only way to progress is to perform a hard reset.

So what next? Will any error information be caught or will I have to boot in safe mode and enable each driver one by one to determine which is causing the issue?

**Arc** · 14 Jan 2013

Boot into safe mode and disable DV. Then enable it again, making it sure that you are not selection any microsoft and unknown provided drivers.

Have you taken the other tests already?

DarrenF · 31 Jan 2013

Just thought i would update this. I ran the MemTest app with all four memory sticks fitted and pretty much immediately errors were showing up. I then went on to run the test against each stick individually and identified one stick was faulty. I removed this and the machine has been fine for over a week now (The corrupt stick has been sent back for an exchange).

Thanks to Arc for his help in diagnosing this issue.

Darren

**Arc** · 31 Jan 2013

Good to know that your PC is running fine now

If there is any further issue, let us know.

Windows 7: Windows 7 - Fresh Install BSOD whilst applying windows updates

Windows 7 - Fresh Install BSOD whilst applying windows updates problems?