BSOD at random times

[CaioF]

It's been 3 months since last BSOD. I will upload a log

 

[Arc]

Multiple bugcheck codes, but pointing to the display driver 337.88 WHQL.

[COLOR=Red]BugCheck 116[/COLOR], {fffffa8006b2f4e0, fffff8800fa1ed1c, ffffffffc000009a, 4}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
[COLOR=Red]Probably caused by : nvlddmkm.sys[/COLOR] ( nvlddmkm+98bd1c )

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

[COLOR=Red]BugCheck D1[/COLOR], {10, 2, 0, fffff8800f0c6fdc}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
[COLOR=Red]Probably caused by : nvlddmkm.sys[/COLOR] ( nvlddmkm+dfdc )

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

Try to roll it back to the earlier version that worked good for you.
Device Manager - Roll Back Driver

Also, update the driver to DW1525 WiFi card from Dell: Product Selection | Dell US
Update the onboard Realtek network: Realtek

Let us know the results.

 

[CaioF]

Forgot to say that the BSOD started after I unninstalled CS GO, yes it's original from steam

 

[CaioF]

I updated the two network drivers, I'm going to send another log just to make sure it's the video driver that is causing the problems. BTW, today from about 8 am to 14 pm the computer worked just fine, it started giving BSOD now

 

[Arc]

This time the BSOD crash dump is not very informative.

BugCheck A, {fffffa80908be9c0, 2, 0, fffff8000331001c}

Probably caused by : ntkrnlmp.exe ( nt!CcLazyWriteScan+188 )

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

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

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

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Also, as teh computer was long time in use before throwing the bugcheck, the question of heat becomes uppermost. Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

 

[CaioF]

Should I idle the pc while DV is running ?

 

[CaioF]

Memtest showed 37 errors, Driver Verification ran for about 2 hours before BSOD. I'm guessing I will have to buy new RAM right ?

 

[Arc]

I suggested you to run driver verifier if memtest does not show any error. When memtest shows at least one error, no more troubleshooting is required. Now it is the time to search for the source of the RAM issue.

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

If the RAM is bad, change/replace the RAM stick with one having the exact same specs of the existing ones. But it is best to get a new kit.

For a bad slot, it is a motherboard failure. You may use the computer with that particular slot not occupied by a RAM stick.

 

[CaioF]

I'll do this. Thursday my father will take the computer to support, i'll reply here if anything happens. Thank you very much for your help

 

[CaioF]

So the computer is back, we changed the thermal paste and the cooler, turns out the computer was overheating just like you said. Here are some prints. I'll mark as solved.

 

[Arc]

Good job!

Let us know for any further issue.