BSOD - Why?

[Redmelo]

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
---------

 

[harshuk]

Try reseating your memory I had something very similar happen on my previous comp and it solved it.

 

[EyepodI]

You have an Nvidia graphics card? Try re-installing driver for it.

A google search for nvlddmkm.sys reveals quite a few issues of BSODs

http://www.google.co.uk/#output=search&sclient=psy-ab&q=nvlddmkm.sys&oq=nvlddmkm.sys&gs_l=hp.12..0l4.1899.1899.0.3262.1.1.0.0.0.0.1295.1295.7-1.1.0...0.0...1c.2.9.psy-ab.ZnVTxWtVyiA&pbx=1&bav=on.2,or.r_qf.&bvm=bv.45373924,d.d2k&fp=d0fcf84eb7d61be0&biw=1920&bih=955

 

[Redmelo]

Thanks for the replies!

I have reinstalled the nividia drivers, to an older version, but the problem persisted.
Will reseat the RAM tomorrow and hope that helps.

It is really strange how it only happens within 30 min or less from boot. Then its rock solid for the remainder of the day (knock on wood).

 

[Redmelo]

It turns out reseating the RAM worked. How does something like this happen?
I have not touched the RAM in ages, why would it suddenly not work right?

 

[Scotteh]

Maybe wasn't put in right?

 

[bledd]

The contacts can oxidise slightly, reseating them kind of 'scratches' away the oxidation for a better connection.


Or... Maybe wasn't put in right?