Various (seemingly unrelated) BSOD on new build. 0x0000003B

[sharf224]

Alright, I just built a new computer (not my first by any means) and this is the first time I've had any kind of trouble. On the first day of starting the machine up I was getting blue screens of all different errors (one of the most common was 3B) and they were all seemingly unrelated. Some errors said not enough disk space, which is impossible, I have plenty. Several involved the kernel, one even involved ntfs.sys. They all suggested a bios update though, so I flashed the bios and the problem went away for 2 days. Then this morning when I went to boot, I couldn't get the system to get much past the welcome screen before blue screening. Every time the error was different, except for 3 3Bs. I formatted the drive, reinstalled Windows 7 (lost the old dump files), and it is happening again.

So It would seem that it is time to RMA some parts, but I cannot pinpoint any truly suspect part.

What I have done so far:
Run a memory diagnostic tool, no errors.
Run chkdsk, no errors.
Updated all drivers to the latest, removed all software except windows and drivers.
Updated windows to the latest updates.
Used BlueScreenView to try and debunk some issues.
used SF Diagnostic Tool to provide the following file.

I am out of ideas on this, especially since I can be running a very intense game, and leave the computer running for days, and then have a random blue screen kill it. It seems that the blue screen is caused by windows update though, as that is the only problem that runs/installs anything new right around the time of the blue screens.

Any help would be greatly appreciated!

 

[Dsprague]

It looks like your video card driver is causing problems:

fffff880`08796178  fffff880`111274f1Unable to load image \SystemRoot\system32\DRIVERS\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
 nvlddmkm+0xbd4f1

Driver Reference Table - nvlddmkm.sys

looking at the time stamp on the driver we can see it is old:

kd> lmvm nvlddmkm
start             end                 module name
fffff880`1106a000 fffff880`11d52000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="Red"]Thu Aug 30 11:50:16 2012[/COLOR] (503F8BB8)
    CheckSum:         00CCA304
    ImageSize:        00CE8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please update it form here:Drivers - Download NVIDIA Drivers

 

[sharf224]

The driver's I have are specific to the card, as it is designed to work with the Asus software, I have the latest driver from the Asus website, but I suppose at this point it can't hurt to try it.

 

[sharf224]

Alright everything was fine for several days, and then all of a sudden this happened. I got a 1e error labeling tcpip.sys as the culprit. Here is the SFDT report.

 

[VistaKing]

sharf224

Try updating the LAN driver for your Asus .

Have you tried running SFC /scannow ?

 

[sharf224]

Updating the driver now - could have sworn that was up to date. SFC reported nothing wrong. I'll post back if anything goes wrong again. Thanks.

Edit: the driver listed on the website says it's from 10/31/12 but when I install it, device manager shows it as being 6/7/12...not sure what's up, but that's the same date I had before.

 

[Dsprague]

You may need to update the driver for your USB mouse it was being blamed for the problem in your last dump file:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

[COLOR="Red"]*** WARNING: Unable to verify timestamp for DB3G.sys
*** ERROR: Module load completed but symbols could not be loaded for DB3G.sys

Probably caused by : DB3G.sys[/COLOR] ( DB3G+1ba3 )

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

Driver Reference Table - DB3G.sys

Please update the driver from here: Razer Diamondback Driver v6.02

 

[sharf224]

Ok thanks, that's done. I would have thought when Windows update offered the drivers for it, they would be the latest. While I was at it I also tried updating my keyboard drivers (Saitek Cyborg V7) from their website, but it doesn't seem to change anything.

And about those lan drivers, I had to download the latest version from the realtek site, but now they're the newest.

 

[Dsprague]

Never had to deal with a Saitek driver before, so I cant really speak to how well they provide support and update for their drivers, but let us know if you have further problems with your computer and we would be glad to help.

 

[sharf224]

Well, this was it's longest streak without blue screening, and on the previous set up, I didn't install any drivers for the mouse I don't think. So I guess I'll just keep running it, and if I get another one, just try and fix them one at a time. Thanks!

 

[Dsprague]

Glad to be of help.

 

[sharf224]

Just had another one. This one is a 1E KMODE_EXCEPTION_NOT_HANDLED. Might have been caused by the alpha version of a game I was playing, but just to be sure, here's my files.