Windows 10: Unpredictable and random BSODs - Frustration Factor: Chainsaw

A clean install is mostly the solution for software, but not for drivers, bugs in windows or hardware.

 

You still have Daemon tools installed?

Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

Is daemon tools still appearing? damn that programme...

Removing it was the first step of this process.

I cannot find anything about it on the machine - the SPTDinst says no version found.
I will install daemon and remove it again.

 

ah, ok - i found, inside C:\Windows\System32\drivers, a file called dtlitescsibus.dll.

I have renamed this file, and enabled driver verifier.

 

What are the results of driver verifier?

 

Hi axe0,

The driver verifier has not been noted in any BSOD's that have happened over the past few days.
Attached is an updated .zip. The BSOD's were reduced by about 50% after removing the old daemon and mij drivers. They came back, though

ntokernl.exe is most often named now.

 

scratch that last file - here is a new one, while I am here.

I've been playing some Total War: Atilla and Metal Gear Solid V in the past few days. The machine does not blue screen while I am playing - it blue screens when I take a break and leave it idle for a minute or so, it seems. The one just now was during Total War, where I had gone to make tea.

Small mercies - The machine does not BSOD using photoshop or illustrator at all lately. Only from desktop or, past few days, in a game. I have not had to use media encoder or after effects yet.

 

Please make sure you've updated the drivers of your network card via the site of Realtek.

Please do the following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow doesn't say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.


Please do the following:

• Open an admin command prompt
• Copy/paste "chkdsk C: /f" (without quotes) and press enter
• Reboot if asked

It may take a while to finish depending on the size of the partition, in your case not that much, please let it run even when it looks frozen as it will finish.

 

ok. I will do this now.

both sfc and chkdsk have been run in the last 24 hours - i will run them again for collection.
The realtek drivers are the latest available - i have reinstalled them using a new download.

---

the machine crashed just now, opening cmd - then did some update on restart...

 

If you already did sfc and chkdsk then there is no need to do them again.

 

those things have become part of the daily routine :/

 

Sfc just needs to be done when there are new updates installed.

Chkdsk is only necessary when you think there are problems with the hard drive.

 

While I am running these steps - the machine has crashed twice at different stages.

 

You don't need to run them daily.

A driver is probably not correct installed,
Code: BugCheck 50, {ffffe0017026da42, 2, fffff80083ea778d, 2} Could not read faulting driver name Unable to load image dump_iaStorA.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for dump_iaStorA.sys *** ERROR: Module load completed but symbols could not be loaded for dump_iaStorA.sys Probably caused by : memory_corruption Followup: memory_corruption[/quote] Seeing here it has probably something to do with Nividia.
Code: ffffd000`28b0b458 fffff803`cce13095 : 00000000`00000050 ffffe001`7026da42 00000000`00000002 ffffd000`28b0b6a0 : nt!KeBugCheckEx ffffd000`28b0b460 fffff803`ccc94536 : 00000000`00000002 00000000`00000000 ffffd000`28b0b6a0 ffffe001`00000000 : nt! ?? ::FNODOBFM::`string'+0x41295 ffffd000`28b0b550 fffff803`ccdcc2bd : ffffc001`00000000 00000000`00000000 ffffd000`28b0ba78 ffffe001`e73fa340 : nt!MmAccessFault+0x696 ffffd000`28b0b6a0 fffff800`83ea778d : 00007ffb`da268b30 00000000`00000000 fffff803`ccfcfd00 fffff800`83e5129b : nt!KiPageFault+0x13d (TrapFrame @ ffffd000`28b0b6a0) ffffd000`28b0b830 fffff800`83e90bdf : ffffe001`e2ded240 ffffd000`28b0ba28 00000000`00000000 00000000`00000000 : dxgkrnl!DXGSYNCOBJECT::Initialize+0x80e9 ffffd000`28b0b880 fffff800`83ea0339 : ffffd000`28b0b9a0 ffffd000`28b0ba80 ffffc001`4f682000 fffff800`00000001 : dxgkrnl!DXGGLOBAL::CreateSyncObject+0xcf ffffd000`28b0b910 fffff800`83e50a96 : ffffc001`00000000 ffffc001`4f682000 00000000`00000000 ffffd000`28b0bb80 : dxgkrnl!CreateSynchronizationObjectInternal+0xb9 ffffd000`28b0b9a0 fffff803`ccdcd863 : ffffe001`ebf19080 000000f9`00000000 ffffc001`4f682000 ffffc001`4f682000 : dxgkrnl!DxgkCreateSynchronizationObjectInternal+0x376 ffffd000`28b0bb00 00007ffb`ff70f0ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ ffffd000`28b0bb00) 000000f9`0f03c988 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`ff70f0ca[/quote] Please uninstall the nvidia drivers in Display Driver Uninstaller and install them again.

EDIT: Looking a little deeper it looks like a driver cannot be loaded from the Graphics card.

 

The drivers have been removed and reinstalled (again ).

If the machine keeps on crashing as today - I will remove the card and give it a good dust off and check around.