Solved BSOD playing Civ5 and opening SpeedFan

[Macy]

Hello, I have been getting the BSOD while playing Civilization5 and at that time did not know it was the BSOD, it would just restart the computer. I assumed it may be a heating issue I installed a program called SpeedFan, and when I try to run it, a BSOD will be induced.

So far no BSOD appears other than playing Civ5 or trying to run SpeedFan, I tried going through and updating the drivers (very well could have missed one). I ran MemTest86+ overnight and got 5 passes with no errors. Ran a disk check (though this may not have been a through check). I also switch the RAM in the motherboard into the next compatible slot combination.

I did try verifier but I am not sure what it does, but attached is the diagnostic tool folder .zip

The system is newly built and tested by the makers, so I was wondering maybe there is a conflicting driver issue of some sort.

Thank you for your time.

 

[Dsprague]

It looks like your BSOD is being caused by faulty speedfan drivers:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80803a44728, 0, fffff800038b0442, 5}

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

Could not read faulting driver name
[COLOR="Red"]Probably caused by : speedfan.sys [/COLOR]( speedfan+1fc3 )

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

you may want to try uninstalling and then re-installing the program, if it persists beyond that you may want to look into another program for temperature monitoring program.

 

[Macy]

Okay, I removed it and reinstalled it, same effect so I will try a different temp gauge.

There still is the problem with Civ5, I have the first dump file available if you could take a look? (Id try to read the .dmp if I could).

Edit:
Or would you want a BSOD to happen when I am playing Civ5 and post another SF diagnostics?

 

[Dsprague]

This is a 0x116 error indicating possible GPU failure:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800cc6f4e0, fffff880063c8ed0, ffffffffc000009a, 4}

Unable 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
Probably caused by : nvlddmkm.sys ( nvlddmkm+8e9ed0 )

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

Firstly start by cleaning out your computers case and trying to get rid of any dust that may have accumulated, next run some stress tests on your GPU:

FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature" (BurnIn test in newer versions).
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Run test 2 in this to stress test your video memory, and post the graphs that the program generates when it finishes assuming it doesn't cause a crash:

http://www.sevenforums.com/tutorials/160729-nvidia-amd-video-card-test-occt.html

 

[Macy]

The FurMark test reached Max GPU Temp without a crash.

The Nvidia test completed without a crash, attached are the graphs in a zip folder.

 

[Macy]

I ran the OCCT test with 15loops. I did notice that the Vcore dropped below 1v on occasion, I attached the graph, would this cause a problem?

 

[Dsprague]

OK good news, I dont think it is a GPU problem its looking more like a PSU issue the graph below is one that you provided from the OCCT test it shows your Vcore voltage and as you can see it is fluctuating wildly that is not normal, what we are looking at here are power fluctuations of + or - more than thirty percent, so either your PSU is failing or is simply not powerful enough to handle the hardware you have installed.

 

[Macy]

Okay, I went into Power Options, and it was set on 'High Performance' so I put it on 'Balanced' and reran the test and this is what I got. Does that look better?

 

[Dsprague]

Your still getting the fluctuations though I am not a hard ware expert, let me see if I can get one to have a look at this.

 

[Macy]

Okay, Thank you very much for all of your help! I was ready to format or send this back to the place I bought it from.

Edit:
This is my powersupply
https://www.computerlx.com/product_view.aspx?product_ID=1067

Also Updated System Specs

 

[essenbe]

The PSU is a quality brand and I would be surprised if that is causing the fluctuations, but stranger things have happened. Even quality one go bad occasionally. I'm not overly familar with Occult test and how it runs. But, first things first. If you are overclocking anything, please set things back to default values. also, that is the GPU test, and is showing gpu voltage.

 

[Macy]

Had another crash during a different game. Attached is the diagnostics.

Edit:
I will do a power supply check with Occult.

 

[Layback Bear]

I tried Speed Fan about a month ago, again and it gave me all kinds of problems. I had to remove it and that wasn't easy because it's in all kinds of places one wouldn't think it would be in.

 

[essenbe]

I ran the test, and apparently I have a different version so couldn't get the same graph. But if you look at CPU usage it may explain the fluctuations in vcore (assuming the vcore is CPU vcore) The test does not appear to be very stressful, to me. It appears to be about the same as playing a game. My GPU temps were the same if playing a game. But, the way it uses the CPU may very well explain the vcore fluctuations.

View attachment 272563

 

[Dsprague]

I ran the test, and apparently I have a different version so couldn't get the same graph. But if you look at CPU usage it may explain the fluctuations in vcore (assuming the vcore is CPU vcore) The test does not appear to be very stressful, to me. It appears to be about the same as playing a game. My GPU temps were the same if playing a game. But, the way it uses the CPU may very well explain the vcore fluctuations.

View attachment 272563

Thank you essenbe, I do believe the Vcore is for the CPU is my memory serves me properly, so that still does not seem to dea lwith your Video TDR error aka 0x116 bugcheck (the one you get when your games crash). so moving along here are a few things to try:

Reset your page file:

Use this technique to "reset" your pagefile:
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step b ). Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.

Run the system file checker to clear up any file system corruption:

SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
If the program ends with anything other than "no integrity violations found" run the command two more times.
If after three runs there are still problems run the command at boot: http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

Re-install directx: Download DirectX End-User Runtime Web Installer from Official Microsoft Download Center

Stop any over clocking that you may be doing (if none then skip this step)

See essenbe's post and my post below

 

[essenbe]

I ran the test, and apparently I have a different version so couldn't get the same graph. But if you look at CPU usage it may explain the fluctuations in vcore (assuming the vcore is CPU vcore) The test does not appear to be very stressful, to me. It appears to be about the same as playing a game. My GPU temps were the same if playing a game. But, the way it uses the CPU may very well explain the vcore fluctuations.

View attachment 272563

Thank you essenbe, I do believe the Vcore is for the CPU is my memory serves me properly, so that still does not seem to dea lwith your Video TDR error aka 0x116 bugcheck (the one you get when your games crash). so moving along here are a few things to try:

Reset your page file:

Use this technique to "reset" your pagefile:
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step b ). Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.

Run the system file checker to clear up any file system corruption:

SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
If the program ends with anything other than "no integrity violations found" run the command two more times.
If after three runs there are still problems run the command at boot: http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

Re-install directx: Download DirectX End-User Runtime Web Installer from Official Microsoft Download Center

Stop any over clocking that you may be doing (if none then skip this step)

Dsprague, I think you are correct. I just ran it again and my CPU Vcore was pretty much a straight line.

 

[Dsprague]

Well that does change things a bit, in which case its best to ignore my above post and look into getting your PSU replaced it is likely having problems.

 

[essenbe]

For the record, here is my vcore graph

View attachment 272568

How about check bios > hardware monitor and tell us the values of the +12V, +3.3V and +5V. That could show a problem but still won't show what those values are under stress.

 

[Macy]

I ran those tests that you suggested Essenbe, came back clean. I am going to do one final try of reinstalling windows 7 and all the drivers. After that the PSU will have to be replace. Thank you all for helping!

Edit:
My Vcore still has spikes in it.

 

[Dsprague]

For the record, here is my vcore graph

View attachment 272568

How about check bios > hardware monitor and tell us the values of the +12V, +3.3V and +5V. That could show a problem but still won't show what those values are under stress.

Here The occt also provides the graphs for those rails here are the results from the occt test the OP did earlier