random BSOD that happens occasionally / not reproducible

[k0ala2k]

had to skip the steps 3-5 due to lack of C:\NVIDIA but did the rest as the tutorial said...
lets hope it will work tho - gonna game a bit to test it right away

 

[k0ala2k]

seems like that wasn't the solution.. now the BSOD said "IRQL NOT LESS OR EQUAL"

 

[Golden]

Im not having much luck with this one - I'll ask for a 2nd opinion

 

[Arc]

Hi k0ala2k.

Let us have another way.

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.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus. All means all. Dont be choosy here.
5. Apply > OK
6. Accept then restart.

Then 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.

 

[k0ala2k]

Hello Arc, thanks for helping out, I really appreciate your help!

Right after having set up the driver verifier I got BSODs on windows startup - everytime the same one.

Edit:
when I think this over. sometimes when I browse a volume on hdd it takes long time and I hear a sound. after this sound I can access the hdd. it feels like the hdd is starting with that sound. it also makes that sound when theres a BSOD and it says "init hdd for crash dump" maybe this is related somehow?

 

[Arc]

Driver verifier caught two things at a single go. Intel Rapid Storage and Daemon Tools. And Daemon Tools can cause any sort of issue, from hardware to software.

Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall the program at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Now run the computer normally. If it BSODs again in the normal mode, report us. We may need to go for Driver Verifier again, depending on the situation.

* EDIT: 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. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.
________________________________________

BugCheck C9, {23e, fffff880046f3360, fffff98002a1ce10, 0}

[COLOR=Red]*** WARNING: Unable to verify timestamp for iaStorF.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for iaStorF.sys
Unable to load image \SystemRoot\system32\DRIVERS\dtsoftbus01.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for dtsoftbus01.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
[COLOR=Red]Probably caused by : dtsoftbus01.sys[/COLOR] ( dtsoftbus01+1360 )

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

 

[k0ala2k]

ok, done everything. FurMark Benchmark went good. Nothing exceptional.

will play a few games to try to cause BSODs

 

[Arc]

will play a few games to try to cause BSODs

Yes, do it. That will be needed.

 

[k0ala2k]

Well, its been a few days now.. and I haven't had a BSOD yet.
Reliabiltyhistory-Report looks good too (sry its in german )

Do you think the problem is solved with this?

 

[Arc]

Yes, we may consider it as solved for now, as it is running BSOD for a reasonably long time.

 

[k0ala2k]

I'm afraid this wasn't it yet...
had a BSOD again today

 

[Arc]

BugCheck 50, {ffffe8a002edcc80, 0, fffff88004360193, 7}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b )

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

fffff880`048f2708  fffff880`04371980 dxgmms1!VIDMM_SEGMENT::FlushPendingCPUAccess+0x4
fffff880`048f2b98  fffff880`04376f00 dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+0x68

fffff880`048f26e0  fffff880`04cca586Unable 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+0x61586

I havent noticed a number of issues with 347.88 WHQL installed, but as you are having issues with it, try two earlier drivers one by one .....

• NVIDIA DRIVERS GeForce Game Ready Driver WHQL
• NVIDIA DRIVERS GeForce Game Ready Driver WHQL

Uninstall the installed version of the display driver using DDU, then apply any of the above two, see how it goes. If it problems, try the other one in the same way.

As teh graphics card is free from errors, either of these two driver version should work stable for you.