BSOD while Idling overnight

bullfights · 08 Feb 2015

Hey guys,

Was logged off last night about 9 pm and woke up at 7 am turned on monitor and had BSOD. Its happened last couple days and seems to only happen while Idling or after restart. Its the same PC I've been having issues with for the last year just don't have the funds to upgrade anything, else I would and toss this to someone else.

Included the SF files, which includes last 5 dumps, I think I just might have to keep dealing with this for a bit more.

Thanks

Arc · 08 Feb 2015

All the bugchecks are different, as well as the probable causes. So it gives a hint of failing hardware, apparently; which is supported by one bugcheck, too.

Code:

BugCheck 3B, {c0000005, fffff96000222e1d, fffff88002561980, 0}

Probably caused by : hardware ( win32k!DEVLOCKBLTOBJ::bLock+379 )

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

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

Stress test the CPU.

Hardware - Stress Test With Prime95

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

*** Also, Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept then restart.

And if you have libusb | SourceForge.net installed by any chance, uninstall it, at least as a test.

Let us know the results.

______________________________________

Code:

BugCheck A, {fffffa000eac8368, 2, 0, fffff80004891625}

Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+1e3 )

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

Code:

BugCheck 50, {fffff88047c12128, 0, fffff88006c06e87, 5}

*** WARNING: Unable to verify timestamp for looxcie-libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for looxcie-libusb0.sys

Could not read faulting driver name
Probably caused by : usbprint.sys ( usbprint!USBPRINT_CallUSBD+90 )

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

Code:

BugCheck D1, {1, 2, 1, fffff8800538fb53}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+93 )

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