BSOD 2 times each day

Jakle001 · 22 Jun 2015

Hello,

As the title says, a BSOD occurs two times each day, always after the computer has been shut off for a few hours (so it happens after I've gone to bed). This has happened before but then it happened after around 10 min after starting the computer; now it takes around a half hour before BSOD occurs.

I failed to tell you that the BSOD occurs regardless of what I am doing. I can play games, be on internet or just do nothing and BSOD still happen.

A zip file is added as required.

Boozad · 22 Jun 2015

Welcome to 7F, I'll see if I can help you solve your issues. There are two immediate issues standing out in your dumps which I've outlined below, follow the instructions below and then monitor the system's performance and report back.

NVIDIA DRIVER

Your nVidia driver has been flagged. Download an earlier version from here and follow NVIDIA Drivers - Avoid Problems for the cleanest possible install.

Code:

fffff880`0be9ea58  fffff880`04a602b4Unable 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+0x22d2b4

1: kd> lmvm nvlddmkm
start             end                 module name
fffff880`04833000 fffff880`052ee000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue May 12 02:59:00 2015 (55515E64)
    CheckSum:         00A86612
    ImageSize:        00ABB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

REALTEK

Your Realtek ethernet driver has also been flagged. It's very old and needs updating, check your motherboard vendor's support page for you board for an updated version.

Code:

fffff880`0be9e608  fffff880`04216f12Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
 Rt64win7+0x16f12

1: kd> lmvm Rt64win7
start             end                 module name
fffff880`04200000 fffff880`04232000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Thu Feb 26 09:04:13 2009 (49A65B0D)
    CheckSum:         0002EB30
    ImageSize:        00032000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

There are also a couple of nods towards memory corruption, and while this may be down to the drivers listed above it will be best to rule out your physical RAM. Read all of the information below and then test your RAM.

Download and run MemTest86+ to test your RAM. RAM - Test with Memtest86+

Note

Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

Jakle001 · 22 Jun 2015

So now I have reinstalled the Nvidia drivers according to the safe installation guide that you provided. After that do I update the drivers to the latest?

For the Realtek Ethernet, I could not find the drivers on their website. Is it okey if I use follow this one instead? RT64win7.sys BSOD crashes when PC idle

For MemTest, it says that I should run it for at least 8 passes; does that mean 8 days over the night?

Boozad · 22 Jun 2015

Jakle001 said:

So now I have reinstalled the Nvidia drivers according to the safe installation guide that you provided. After that do I update the drivers to the latest?

Use the system with the driver you have installed at the moment and see how it goes.

Jakle001 said:

For the Realtek Ethernet, I could not find the drivers on their website. Is it okey if I use follow this one instead? RT64win7.sys BSOD crashes when PC idle

I'd need to know exactly which motherboard you have.

Jakle001 said:

For MemTest, it says that I should run it for at least 8 passes; does that mean 8 days over the night?

The passes are shown on screen as highlighted below, let it run overnight and don't stop it until eight full passes have completed, unless any errors show first.

Jakle001 · 22 Jun 2015

My motherboard is this one ASRock Socket AM3/AMD 770/SATA3&USB3.0/A&GbE/ATX Motherboard 770 EXTREME3

Boozad · 22 Jun 2015

The driver for your LAN is linked below, download it and install to give it a try. It's dated 2010 so while it's not recent it's still newer than the one you have installed.

Download

Jakle001 · 24 Jun 2015

I've now finished the Memtest and found no errors. But yesterday, before I started the Memtest but I had changed the Nvidia drivers and updated the LAN drivers, my computer crashed again. Could you take a look at this new zip file and see if you can spot the problem?

Boozad · 24 Jun 2015

There were no drivers named in the latest dump but memory corruption seems to be the issue.

Code:

BugCheck 3B, {c0000005, fffff88001029391, fffff8800289ec30, 0}

Probably caused by : fltmgr.sys ( fltmgr!FltpAllocateIrpCtrl+61 )

Followup: MachineOwner

An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88001029391, Address of the instruction which caused the bugcheck
Arg3: fffff8800289ec30, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

Now MemTest86+ has ruled out your RAM already so given that 0x3Bs are often down to user mode graphics drivers passing bad data to the kernel code I checked the date of the driver you replaced your last one with. It's pretty old so we'll go for the latest one.

Code:

1: kd> lmvm nvlddmkm
start             end                 module name
fffff880`130f1000 fffff880`13d28000   nvlddmkm   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Oct 23 07:21:50 2013 (52676AFE)
    CheckSum:         00C0CF0F
    ImageSize:        00C37000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Download version 353.30 linked below and follow NVIDIA Drivers - Avoid Problems for the cleanest possible install.

Download

Jakle001 · 26 Jun 2015

It seems like updating the drivers hasn't fixed the problem because it still exist. I created another DM Collector and hope that you have time to take a look at this one as well.

Boozad · 26 Jun 2015

The dumps are blaming the the nVidia driver again.

Code:

fffff880`0b3b15c8  fffff880`04a9597c
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x23397c

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`04862000 fffff880`0532b000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Jun 17 06:36:26 2015 (5581075A)
    CheckSum:         00A850BE
    ImageSize:        00AC9000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It looks as if there may be a problem with your card, please follow the instructions below.

Run Furmark to stress test your GPU. Video Card - Stress Test with Furmark

Note

Run Furmark for around 30 minutes.

Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them, if the temperature continues to rise steadily once it has reached 80°C be prepared to stop the test so as to not damage your GPU.

Monitor your temperatures at idle and under load and report them back.

Refresh your WEI Windows Experience Index - Update or Refresh Score