BSOD while computer is idle SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

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

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.

wither 2 said:

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.

wither 2 said:

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 said:

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

Code:

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 said:

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 said:

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.

Code:

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.

Code:

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.

axe0 said:

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.

Code:

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.

Code:

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.