Random BSOD's at random times on new PC

[CrazyGuy158]

Hello. I built a PC two days ago and today I have had 4 BSOD's so far and I fear there will be more of them.

Today, the 28th, I've have 4 or 5 bsods and most, if not all, have had the 0x109 stop code.

 

[Arc]

Post it following the Blue Screen of Death (BSOD) Posting Instructions .

 

[CrazyGuy158]

Done.

 

[Arc]

OK, let us look ....

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 109[/COLOR], {a3a039d89915a630, b3b7465eeb9375aa, fffff80002e21fa0, 1}

[COLOR=Red]Probably caused by : Unknown_Image[/COLOR] ( ANALYSIS_INCONCLUSIVE )

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

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) [COLOR=Red]A driver has inadvertently or deliberately modified critical kernel code
 or data.[/COLOR] See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) [COLOR=Red]A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted.[/COLOR] Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) [COLOR=Red]A hardware corruption occurred, e.g. failing RAM holding kernel code or data.[/COLOR]
Arguments:

So we may do two things here ....

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

2. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Run memtest, for at least 8 passes. Preferably6 overnight.

Let us know the results.

 

[CrazyGuy158]

How come I didn't come across any errors whilst running the Windows Memory Diagnostic tool?

 

[CrazyGuy158]

A small update to this matter.

On the 27 of August, I had four BSOD's, and only one had the 0x109 stop code. Then I mistakenly flashed a bios upgrade where I had picked the latest bios for the rev I don't have. My motherboard comes in two revs, 1.0 and 1.1, and I have rev 1.0 but the bios was for rev 1.1. Anyways, I thought all was smooth sailing from now on, but the day after, which is today, I've had six BSOD's up until 2.57 pm.

After the last BSOD (at 2.57pm) I cracked my PC open and checked the mobo, to find out that I had another rev than what I had flashed a bios for. I immediately booted up and flashed the right bios (the latest version), did an SFC scan which found a few corrupted files and then I uninstalled Norton.

I haven't had a BSOD thus far, but I fear this is far from over. I'm not gonna be so quick and blame the RAM until I'm absolutely positive it is the RAM. It can very well be a driver error or some third-party program messing up, couldn't it?

 

[Arc]

Most probably.

Checking your dumps, I havent got any proof to blame the RAM. It is just the usual cause, so suggested.

The windows tool is not a very efficient one, whereas memtest is, and it does not harm.

If it is free from ctashes ATM, wait and observe.

 

[CrazyGuy158]

Since 2.57 pm (14.57), it's been completely crash-free. I'm going to wait and observe, and see how it is tomorrow. It seems to wanna crash a lot after I've woken up.

 

[CrazyGuy158]

Oh, wow. Four more blue screens and three of them were 109's. I contacted the place I bought the RAM from.

 

[Arc]

STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTION http://www.carrona.org/bsodindx.html#top

Usual causes: Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)
----------------------------------
So there is other things to blame, too. Not only the RAM.
Have you ever tried Driver Verifier as suggested in post #4?
Driver Verifier - Enable and Disable

It may be simply a device driver, too!

 

[CrazyGuy158]

I am currently booted on one ram stick to see if I get any blue screens. The driver verifier thing, how can it help me if I already got frequent bsods?

 

[Arc]

It will determine the faulting drivers... but how much you will cooperate is on you.

If it is being caused by a driver, no RAM change can solve the issue.

Have you taken the memtest yet? So that you are deciding that it is being caused by the RAM?

 

[CrazyGuy158]

I'll do the driver verifier thing. How will I know what driver is bad if it finds any bad drivers?

 

[Arc]

Applying driver verifier, use the computer normally. It will crash in many operations. From those crash dumps, the faulting drivers will be found out.

 

[CrazyGuy158]

Driver Verifier is disabled now. I got a blue screen as soon as I logged in to Windows, and I let it reboot three times and got three blue screens, all relating to gdrv.sys, which I heard is a part of Dynamic Energy Saving Advanced by gigabyte?

 

[CrazyGuy158]

I uninstalled all gigabyte crapware and removed gdrv.sys from C:\Windows

I still won't keep my hopes up, though.

 

[Arc]

Continue with DV, it may produce some more things.

And, well done on removing Gigabyte bloatware.

 

[CrazyGuy158]

Continue with DV, it may produce some more things.

And, well done on removing Gigabyte bloatware.

Hopefully that fixed it. I'm gonna run DV if I run into another bsod

Right now I have some gaming to do ^^

 

[CrazyGuy158]

Another BSOD this morning (as I almost expected)

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

BCCode 0x0fc

Driver Verifier time.

 

[CrazyGuy158]

This. Is. Weird!

I ran memtest over night for 7 passes (both sticks) and it picked up no errors. I ran 6 blended torture tests with Prime95, stable as a damn rock.

What else could cause my bsods?