BSOD - Why?

Associate
Joined
12 Jan 2009
Posts
358
Hey,

So I've been getting a few BSOD over the last 3 days (havnt changed any hardware).
The BSOD usually happens within 30 min of booting. Then for the rest of the day I have no problems.

After viewing the minidumb files I get the following results below.
I am unsure how to interpret them. Some help would be greatly appreciated! :)

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

Use !analyze -v to get detailed debugging information.

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

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

Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {fffff8800313b560, 800000015dae3963, fffff8800313b2f0, 0}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+4a1a64 )

Followup: MachineOwner

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002eb2b7b, fffff8800ef9ac70, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {e8, 2, 1, fffff80002eabba0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------
 
Back
Top Bottom