Frequent BSODs on new PC -- ntoskrnl.exe

ashground · 04 Sep 2010

Disconnect all USB devices for the time being.

Install these Realtek drivers: Realtek

If that doesn't help, please enable driver verifier: Driver Verifier - Enable and Disable

Disconnected everything except my mouse. Installed the Realtek drivers. Still got two more BSODs, both while no one was on the computer and nothing was running.

I've already enabled driver verifier once... is there any rationale for enabling it again?

Latest dumps are attached.

Before Win 7 64, I was running Windows Server 2008 R2, which was rock-solid stable. Which is why I'm kind of shocked I'm having so much trouble. More and more I'm thinking I should really just wipe out my system and reinstall everything.

ttran · 04 Sep 2010

The only thing that I can see from the dump is the process running at the time of crash, it is mvraidsvc.exe, which is The process Marvell RAID Event Logging Agent belongs to the software mvraidsvc Application by unknown. I don't know what it is, but if you know what it is and if you don't need it, you might want to re-install or remove it.

BUGCHECK SUMMARY:

Code:

BugCheck 7F, {8, 80050031, 6f8, fffff80002fc2069}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Followup: MachineOwner
---------
PROCESS_NAME:  mvraidsvc.exe

Regard,

Tuan

ashground · 04 Sep 2010

It's the Marvell RAID utility, installed with the RAID drivers. It was also installed after I started getting the BSODs. I don't really see any way to get rid of it without uninstalling the drivers.

ttran · 04 Sep 2010

You can try to re-install the driver with the utility to see if it fix. Are you using any 3rd party firewall?

ashground · 10 Sep 2010

An update to the insanity.

I got fed up, and I reinstalled Windows. Wiped everything clean, started totally fresh.

Shortly after installing Windows, and before I had a chance to install anything, I got a BSOD.

I installed the latest drivers for absolutely everything on my motherboard, as well as my latest graphics card drivers. I didn't install any other hardware -- no printers, no webcam, nothing.

Another BSOD.

Exactly the same as before -- no clue as to what crashed, and happening totally randomly, usually while I'm away from the computer. So, I'm going to put my money on this being a hardware issue.

Since my RAM tests earlier were fairly inconclusive, I took out one of the two sticks of RAM. I'm going to run on one stick until I see another BSOD or a week passes without one. Then I'll run with only the other stick. If I see a BSOD on one stick and not the other, I know it's the RAM. If I see BSODs on both (or no BSOD at all), it's likely either the motherboard or the graphics card -- and since the computer is getting a BSOD while idling, and not while playing games, the motherboard seems like the most likely fault point.

Does this sound reasonable?

CarlTR6 · 10 Sep 2010

Yes, it does make sense. You can run Memtest on each single test, too.