Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD while computer is idle SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

1 Week Ago   #1
LordKane

Windows 7 Home Premium 64
 
 
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




Attached Files
File Type: zip LORD_KANE-PC-Sat_01_05_2019__25401_83.zip (49.3 KB, 4 views)
My System SpecsSystem Spec
.
1 Week Ago   #2
wither 2

Windows 7 Pro SP1 64 bit
 
 

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.
My System SpecsSystem Spec
1 Week Ago   #3
axe0

Windows 10 Pro
 
 

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:
Quote:
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.

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
My System SpecsSystem Spec
.

1 Week Ago   #4
LordKane

Windows 7 Home Premium 64
 
 

Quote   Quote: Originally Posted by wither 2 View Post
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.
My System SpecsSystem Spec
1 Week Ago   #5
LordKane

Windows 7 Home Premium 64
 
 

Quote   Quote: Originally Posted by wither 2 View Post
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.
Quote   Quote: Originally Posted by axe0 View Post
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.

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?


Attached Files
File Type: zip LORD_KANE-PC-Sun_01_06_2019_115209_40.zip (1.79 MB, 3 views)
My System SpecsSystem Spec
1 Week Ago   #6
axe0

Windows 10 Pro
 
 

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.
My System SpecsSystem Spec
1 Week Ago   #7
LordKane

Windows 7 Home Premium 64
 
 

Quote   Quote: Originally Posted by axe0 View Post
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.
My System SpecsSystem Spec
1 Week Ago   #8
axe0

Windows 10 Pro
 
 

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.
My System SpecsSystem Spec
1 Week Ago   #9
LordKane

Windows 7 Home Premium 64
 
 

Quote   Quote: Originally Posted by axe0 View Post
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.
My System SpecsSystem Spec
1 Week Ago   #10
LordKane

Windows 7 Home Premium 64
 
 

Quote   Quote: Originally Posted by axe0 View Post
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.
My System SpecsSystem Spec
Reply

 BSOD while computer is idle SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.




Thread Tools




Similar help and support threads
Thread Forum
System_thread_exception_not_handled bsod
I am receiving several BSOD a day. I have udpated drivers and ran chkdsk /r still cant figure out why it blue screens. I have attached the file dumps and other info. Any help would be greatly appreciated! Marc
BSOD Help and Support
bsod SYSTEM_THREAD_EXCEPTION_NOT_HANDLED HELP!
So after a very long time of no longer receiving any BSODs, I purchased a new graphics card (gtx680). The computer was running just fine until today when I got the bsod SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check code 0x1000007e parameter 1 ffffffff`c0000005 parameter 2 fffff880`0f983ca3 ...
BSOD Help and Support
BSOD - Crashes while computer idle/not idle (Unpredictable)
Windows 7 Enterprise 64bit Clean installation to windows 7 from Windows XP professional Hardware 18 months old OS installed 2 weeks ago I am currently facing the lovely BSOD error. The computer was recently upgraded from windows XP to Windows 7 enterprise 64bit , this was a fresh...
BSOD Help and Support
BSOD,system_thread_exception_not_handled + M
Hello again! I'm using Windows 7 home premium 64 bit 8gb. It's my brothers old pc. While mine is away for some tweaks. Anyways I keep getting these Error's SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED I Included a zip with files and picture. From...
BSOD Help and Support
Bsod system_thread_exception_not_handled
(while i was writing here another BSOD appeared) computer is "old" (2009), after many BSOD at windows xp and windows 7 ultimate x64 I installed windows 7 ultimate x86 a week ago. I was prepared for BSOD and after my personal research I uninstalled the display driver, windows installed and...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 07:57.
Twitter Facebook Google+