BSOD while computer is idle SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

[LordKane]

Sadly this happened while I was asleep, when I tried to resume my PC screen was blank so I had to reset, when I checked BSODView it turned out I had a BSOD while I was sleeping.



System Specs are as follows



Intel i5 3ghz

4 GB RAM

ATI 5770 HD (its sadly now out of support so I have latest available drivers, I am planning on upgrading in Feb/March as that is when I will have the money to do so)

Windows 7 Home X64

500GB WD HDD (Platter)



All my drivers are up to date as possible and windows is up to date as far as I know.



DM Log Collector zip file attached.



My guess is this was due to the fact that I am low on HDD space.



Hope you guys can help.



~LordKane

 

[wither 2]

Hi LordKane-

The problem seems to be in the Volume Shadow Copy driver.

Go to Accessories and find Command Prompt. Right click on it and select Run as Administrator.

Type in- sfc /scannow

and run it.

Does it find/fix any errors? If it does, reboot and run it again to see if there are any other issues.

 

[axe0]

Please run the DM Log Collector again and upload a new zip, the current uploaded one misses several logs.
You could check if there are

1. 18 .txt,
2. 1 .nfo,
3. 1 or more .dmp,

files present, if this is the case then all logs are present
If there are a few missing, no problem as we can get them manually if required

If there are more than a few missing, please do the following

• Open an admin command prompt
• Copy & paste the code below in the command prompt
• Go to your desktop
• Right click CollectedFiles folder and choose sent to and select compressed (zipped) folder
• Upload the zip.

Code:

md "%USERPROFILE%\Desktop\CollectedFiles"&wmic /output:"%USERPROFILE%\Desktop\CollectedFiles\hotfix.txt" qfe list full /format:table&copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\CollectedFiles"&dxdiag /t %temp%\dxdiag.txt&copy %temp%\dxdiag.txt "%USERPROFILE%\Desktop\CollectedFiles\dxdiag.txt"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\CollectedFiles\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\CollectedFiles\systeminfo.tmp"&findstr /v "Owner." "%USERPROFILE%\Desktop\CollectedFiles\systeminfo.tmp" > "%USERPROFILE%\Desktop\CollectedFiles\systeminfo.txt"&del "%USERPROFILE%\Desktop\CollectedFiles\systeminfo.tmp"&driverquery /v > "%USERPROFILE%\Desktop\CollectedFiles\drivers.txt"&msinfo32 /nfo "%USERPROFILE%\Desktop\CollectedFiles\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\CollectedFiles\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\CollectedFiles\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\CollectedFiles\installed.txt"

Also, please run driver verifier for 48 hours. Any configurations are in the link.

Warning: driver verifier could cause boot issues and/or performance issues.

• Make sure that you have recovery media, if needed you can create it.
• Configure a restore point prior enabling driver verifier.

Resetting driver verifier options (recommended in this order)

1. In normal mode open an administrator command prompt and enter the below command
2. In safe mode open an administrator command prompt and enter the below command
3. Press F8 to go to the recovery options,
   • Select Repair Your Computer and press enter,
   • Click Next
   • Enter your password and click ok
   • choose command prompt
   • enter the below command
4. Boot with the recovery media, follow the tutorial and then see above 4 steps in option 3.
5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier

verifier /reset

Crashed when running driver verifier

1. Reset driver verifier
2. Boot in normal mode if necessary
3. Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs

 

[LordKane]

Hi LordKane-

The problem seems to be in the Volume Shadow Copy driver.

Go to Accessories and find Command Prompt. Right click on it and select Run as Administrator.

Type in- sfc /scannow

and run it.

Does it find/fix any errors? If it does, reboot and run it again to see if there are any other issues.

SFC /scannow completed with no errors.

 

[LordKane]

Hi LordKane-

The problem seems to be in the Volume Shadow Copy driver.

Go to Accessories and find Command Prompt. Right click on it and select Run as Administrator.

Type in- sfc /scannow

and run it.

Does it find/fix any errors? If it does, reboot and run it again to see if there are any other issues.

Please run the DM Log Collector again and upload a new zip, the current uploaded one misses several logs.
You could check if there are

1. 18 .txt,
2. 1 .nfo,
3. 1 or more .dmp,

files present, if this is the case then all logs are present
If there are a few missing, no problem as we can get them manually if required

If there are more than a few missing, please do the following

• Open an admin command prompt
• Copy & paste the code below in the command prompt
• Go to your desktop
• Right click CollectedFiles folder and choose sent to and select compressed (zipped) folder
• Upload the zip.

Code:



Also, please run driver verifier for 48 hours. Any configurations are in the link.

Warning: driver verifier could cause boot issues and/or performance issues.

• Make sure that you have recovery media, if needed you can create it.
• Configure a restore point prior enabling driver verifier.

Resetting driver verifier options (recommended in this order)

1. In normal mode open an administrator command prompt and enter the below command
2. In safe mode open an administrator command prompt and enter the below command
3. Press F8 to go to the recovery options,
   • Select Repair Your Computer and press enter,
   • Click Next
   • Enter your password and click ok
   • choose command prompt
   • enter the below command
4. Boot with the recovery media, follow the tutorial and then see above 4 steps in option 3.
5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier

verifier /reset

Crashed when running driver verifier

1. Reset driver verifier
2. Boot in normal mode if necessary
3. Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs

I think this zip should meet your requirements. I do really have to do driver verifer cant I just turn volume shadow copy off and be done with it?

 

[axe0]

I do not recommend turning off volume shadow copy because it's sort of a backup that could be used to restore files to a previous version. I also doubt a Windows file is causing the crash, rather something else interacting with it.

 

[LordKane]

I do not recommend turning off volume shadow copy because it's sort of a backup that could be used to restore files to a previous version. I also doubt a Windows file is causing the crash, rather something else interacting with it.

well I will let you get back to your analysis. I wont wont run verifier for now, since i lack any recovery media atm, I might just leave this as it has happened before but only every 30 or 32 days, since i am going to be now appearantly building a new system.

 

[axe0]

The eventlog is most interesting, it shows lots of bad blocks on cdrom1 which is the cd/dvd player.
This is going back a couple of months, either the player is going bad and damaging your media or the media is damaged.

2019-01-05T11:11:05.593		The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:58.289		The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:50.985		The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:43.681		The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:36.353		The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:28.992		The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:21.685		The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:14.381		The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:07.077		The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:59.771		The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:52.117		The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:44.812		The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:37.328		The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:30.024		The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:22.697		The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:15.377		The device, \Device\CdRom1, has a bad block.

I already had a look at the dump, which is why I suggested to run driver verifier.

I find these a bit worrying in regards to the amount that's present in the eventlog.

2019-01-05T02:18:44.000		The dump file at location: C:\Windows\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.
2019-01-04T02:46:40.734		The driver detected a controller error on \Device\Harddisk5\DR25.
2019-01-04T02:46:40.234		The driver detected a controller error on \Device\Harddisk5\DR25.
2019-01-04T02:46:39.233		The driver detected a controller error on \Device\Harddisk5\DR25.
2018-12-28T02:48:14.629		The driver detected a controller error on \Device\Harddisk5\DR9.
2018-12-28T02:48:14.129		The driver detected a controller error on \Device\Harddisk5\DR9.
2018-12-28T02:48:13.629		The driver detected a controller error on \Device\Harddisk5\DR9.
2018-12-28T02:48:12.629		The driver detected a controller error on \Device\Harddisk5\DR9.
2018-12-19T23:37:48.927		The driver detected a controller error on \Device\Harddisk5\DR26.
2018-12-19T23:37:48.427		The driver detected a controller error on \Device\Harddisk5\DR26.
2018-12-19T23:37:47.927		The driver detected a controller error on \Device\Harddisk5\DR26.
2018-12-19T23:37:46.927		The driver detected a controller error on \Device\Harddisk5\DR26.
2018-12-18T19:36:22.579		An error was detected on device \Device\Harddisk5\DR13 during a paging operation.
2018-12-18T19:36:22.579		An error was detected on device \Device\Harddisk5\DR13 during a paging operation.
2018-12-18T19:36:22.579		An error was detected on device \Device\Harddisk5\DR13 during a paging operation.
2018-11-14T06:01:05.156		Crash dump initialization failed!
2018-11-14T06:01:05.156		Crash dump initialization failed!
2018-11-05T20:49:37.953		Crash dump initialization failed!
2018-11-05T20:49:37.953		Crash dump initialization failed!

Overall I think there's an underlying issue, but if you may want to build a new system and if you want to re-use some parts I suggest that you make sure they're in good condition before using them in the new system.

 

[LordKane]

The eventlog is most interesting, it shows lots of bad blocks on cdrom1 which is the cd/dvd player.
This is going back a couple of months, either the player is going bad and damaging your media or the media is damaged.

2019-01-05T11:11:05.593        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:58.289        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:50.985        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:43.681        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:36.353        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:28.992        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:21.685        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:14.381        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:07.077        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:59.771        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:52.117        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:44.812        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:37.328        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:30.024        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:22.697        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:15.377        The device, \Device\CdRom1, has a bad block.

I already had a look at the dump, which is why I suggested to run driver verifier.

I find these a bit worrying in regards to the amount that's present in the eventlog.

2019-01-05T02:18:44.000        The dump file at location: C:\Windows\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.
2019-01-04T02:46:40.734        The driver detected a controller error on \Device\Harddisk5\DR25.
2019-01-04T02:46:40.234        The driver detected a controller error on \Device\Harddisk5\DR25.
2019-01-04T02:46:39.233        The driver detected a controller error on \Device\Harddisk5\DR25.
2018-12-28T02:48:14.629        The driver detected a controller error on \Device\Harddisk5\DR9.
2018-12-28T02:48:14.129        The driver detected a controller error on \Device\Harddisk5\DR9.
2018-12-28T02:48:13.629        The driver detected a controller error on \Device\Harddisk5\DR9.
2018-12-28T02:48:12.629        The driver detected a controller error on \Device\Harddisk5\DR9.
2018-12-19T23:37:48.927        The driver detected a controller error on \Device\Harddisk5\DR26.
2018-12-19T23:37:48.427        The driver detected a controller error on \Device\Harddisk5\DR26.
2018-12-19T23:37:47.927        The driver detected a controller error on \Device\Harddisk5\DR26.
2018-12-19T23:37:46.927        The driver detected a controller error on \Device\Harddisk5\DR26.
2018-12-18T19:36:22.579        An error was detected on device \Device\Harddisk5\DR13 during a paging operation.
2018-12-18T19:36:22.579        An error was detected on device \Device\Harddisk5\DR13 during a paging operation.
2018-12-18T19:36:22.579        An error was detected on device \Device\Harddisk5\DR13 during a paging operation.
2018-11-14T06:01:05.156        Crash dump initialization failed!
2018-11-14T06:01:05.156        Crash dump initialization failed!
2018-11-05T20:49:37.953        Crash dump initialization failed!
2018-11-05T20:49:37.953        Crash dump initialization failed!

Overall I think there's an underlying issue, but if you may want to build a new system and if you want to re-use some parts I suggest that you make sure they're in good condition before using them in the new system.

Yeah my DVDROM is old, I rarely use it now a days and the DEVICE/HARDDISKX issues are being generated by my USB flashdrives, I have a front port thats slightly damaged. and from some initial discussions it looks like i am a building a totally new system only retaining my HD which is just for data, as I will be migrating to Win10/SSD in March/April.

 

[LordKane]

The eventlog is most interesting, it shows lots of bad blocks on cdrom1 which is the cd/dvd player.
This is going back a couple of months, either the player is going bad and damaging your media or the media is damaged.

2019-01-05T11:11:05.593        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:58.289        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:50.985        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:43.681        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:36.353        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:28.992        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:21.685        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:14.381        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:10:07.077        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:59.771        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:52.117        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:44.812        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:37.328        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:30.024        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:22.697        The device, \Device\CdRom1, has a bad block.
2019-01-05T11:09:15.377        The device, \Device\CdRom1, has a bad block.

I already had a look at the dump, which is why I suggested to run driver verifier.

I find these a bit worrying in regards to the amount that's present in the eventlog.

2019-01-05T02:18:44.000        The dump file at location: C:\Windows\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.
2019-01-04T02:46:40.734        The driver detected a controller error on \Device\Harddisk5\DR25.
2019-01-04T02:46:40.234        The driver detected a controller error on \Device\Harddisk5\DR25.
2019-01-04T02:46:39.233        The driver detected a controller error on \Device\Harddisk5\DR25.
2018-12-28T02:48:14.629        The driver detected a controller error on \Device\Harddisk5\DR9.
2018-12-28T02:48:14.129        The driver detected a controller error on \Device\Harddisk5\DR9.
2018-12-28T02:48:13.629        The driver detected a controller error on \Device\Harddisk5\DR9.
2018-12-28T02:48:12.629        The driver detected a controller error on \Device\Harddisk5\DR9.
2018-12-19T23:37:48.927        The driver detected a controller error on \Device\Harddisk5\DR26.
2018-12-19T23:37:48.427        The driver detected a controller error on \Device\Harddisk5\DR26.
2018-12-19T23:37:47.927        The driver detected a controller error on \Device\Harddisk5\DR26.
2018-12-19T23:37:46.927        The driver detected a controller error on \Device\Harddisk5\DR26.
2018-12-18T19:36:22.579        An error was detected on device \Device\Harddisk5\DR13 during a paging operation.
2018-12-18T19:36:22.579        An error was detected on device \Device\Harddisk5\DR13 during a paging operation.
2018-12-18T19:36:22.579        An error was detected on device \Device\Harddisk5\DR13 during a paging operation.
2018-11-14T06:01:05.156        Crash dump initialization failed!
2018-11-14T06:01:05.156        Crash dump initialization failed!
2018-11-05T20:49:37.953        Crash dump initialization failed!
2018-11-05T20:49:37.953        Crash dump initialization failed!

Overall I think there's an underlying issue, but if you may want to build a new system and if you want to re-use some parts I suggest that you make sure they're in good condition before using them in the new system.

So I did try running Driver Verifier and well, it caused some kind of crash as windows was loading and would not allow me to proceed, so i think this might be some kind of interaction with the video drivers I am using as these were the last latest video drivers ATI provided for my card so I think they are responsible, but seeing as I am soon going to be building a new system I wont really attempt to fix it as the past BSODS all occured 30 days apart.



What do you reccommend I am still open to suggestions.

 

[wither 2]

I agree with axe0 about the CDRom drive problem but it doesn't seem to cause the boot problem. In regards to that do you have Daemon Tools or Alcohol 120 installed?

The .dmp still shows the Volume Shadow Copy as the culprit.

You mentioned that your hard drive is getting low on space. How much free space do you have?

 

[LordKane]

I agree with axe0 about the CDRom drive problem but it doesn't seem to cause the boot problem. In regards to that do you have Daemon Tools or Alcohol 120 installed?

The .dmp still shows the Volume Shadow Copy as the culprit.

You mentioned that your hard drive is getting low on space. How much free space do you have?

1. the new .dmp is still from the first mentioned BSOD I havent had a new bsod since then


2. Yes I do have Daemon Tools installed currently. The boot problem only occured when I tried to make use of Driver Verifier after loading into windows it would show my desktop for about 10 seconds, then it would corrupt the display, freeze and just sit there, I just simply reset, booted into safe mode and turned verifier off.



3. I did a massive cleaning as after the OP BSOD (which remains the only one) but at the time I think I had under 15 gigs of space left, after cleaning I have 64gb of space now.



Apologies for the late reply, when I got the email notification to your response, I was out of town for most of the day, didnt get back home till about 3:30am MST.

 

[wither 2]

No problem with the late reply. I never know if I'm going to respond to someone the same day or the next day. Depends on what I have on my plate.

The reason I asked about Daemon Tools is because the CDROM problem is coming from SPTD and that's installed by Daemon Tools and Alcohol 120. I don't think it's installed as a part of Windows. You might try uninstalling/reinstalling the former with the latest version.

Doing the cleanup will probably eliminate the VSC problem if the problem was that there wasn't enough space for it. I periodically go to Accessories, System Tools and run Disk Cleanup on the C:. When it says how much space it can recover, I check the boxes to include Temporary Files and Recycle Bin (Temporary Internet Files is checked by default). Then I run it and reboot. I don't have to check the boxes every time because Windows remembers it after the first time. It won't tell you how much additional space it recovered but it is substantial if you work with Video editing/transcoding and other programs that generate a huge amount of temporary files.

 

[axe0]

So I did try running Driver Verifier and well, it caused some kind of crash as windows was loading and would not allow me to proceed, so i think this might be some kind of interaction with the video drivers I am using as these were the last latest video drivers ATI provided for my card so I think they are responsible, but seeing as I am soon going to be building a new system I wont really attempt to fix it as the past BSODS all occured 30 days apart.



What do you reccommend I am still open to suggestions.

What kind of crash do you mean? What happened?

 

[LordKane]

What kind of crash do you mean? What happened?

After enabling Driver Verifier according to the instructions on the page you linked, I rebooted, and while windows began loading normally about...10 seconds the loading process corrupted the display (the background became corrupted I really cannot describe it adequately and my phone was dead the time so no pictures) and froze (the mouse cursor was unaffected but it was frozen in place) I left it for about 10 minutes and as nothing happened. I rebooted into safe mode and shut verifier off.

 

[axe0]

It's unfortunate to hear you won't attempt to fix the issue you experienced with driver verifier, but I do understand it.
However, if driver verifier doesn't produce a dump, I'm afraid we won't be of much help. Without additional dumps we can't provide the support needed to resolve BSOD crashes, nobody can.

 

[LordKane]

It's unfortunate to hear you won't attempt to fix the issue you experienced with driver verifier, but I do understand it.
However, if driver verifier doesn't produce a dump, I'm afraid we won't be of much help. Without additional dumps we can't provide the support needed to resolve BSOD crashes, nobody can.

huh what are you talking about, I told you what happened when I tried it on the post above me.

 

[axe0]

I wrote it a little poor, but in post 10, you say you're not going to fix it.

With "It's unfortunate to hear you won't attempt to fix the issue you experienced with driver verifier" I meant the issue (system freeze and graphics problems) is likely caused by driver verifier as in it validated the actions taken by some drivers which resulted in a delay in performance and display.

 

[LordKane]

I wrote it a little poor, but in post 10, you say you're not going to fix it.

With "It's unfortunate to hear you won't attempt to fix the issue you experienced with driver verifier" I meant the issue (system freeze and graphics problems) is likely caused by driver verifier as in it validated the actions taken by some drivers which resulted in a delay in performance and display.

ah yes, thats right I did, we apparently misconnected I dont even know what would cause that problem with verifier so I dont even know where to start honestly.

 

[wither 2]

In regards to the graphics driver, are you using the beta Crimson 16.2.1 or the Radeon 15.7.1?