BSOD after time of inactiveness/sleeping/hibernation

[Sour]

BSOD After Inactiveness - 0x000000F4 [Unsolved]

I have recently bought a new motherboard, processor, and memory. I get a BSOD every single time that the computer goes to sleep by itself. I do not actually see the BSOD, but whenever I go back to my computer after a little while of not using it I see an error message saying the computer restarted randomly. Then when I click 'More Info' it says it was a Blue Screen. Pretty much all it says.

It will never BSOD while I am on it. I was at a LAN party over the weekend and only when I went away from my computer for around 15-30 minutes I would come back and see an error message saying that my computer shutdown unexpectedly. I tried searching on how to fix the problem, I haven't gotten much help.

System Specs:
I am running Windows Professional x64 Purchased separately
The system ranges from about 1 year to 1 week old. The power supply and hd are about 1 year. The rest of it about 1 week old.
I recently just re-installed windows about 1 week ago.

I believe I have the most recent drivers. I installed the motherboard cd. Downloaded Graphics Drivers. Windows update pretty much did the rest.

EDIT:
I was watching my computer and about every 30 minutes after i got off of it I would get the BSOD. It was 0x000000F4, or something like that. The BSOD never happens while I am on the computer.

Whenever I go back onto my computer I get Windows has recovered from an unexpected shutdown. Here is the Problem Details.

Problem signature:
  Problem Event Name:	BlueScreen
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033

Additional information about the problem:
  BCCode:	f4
  BCP1:	0000000000000003
  BCP2:	FFFFFA800929EB30
  BCP3:	FFFFFA800929EE10
  BCP4:	FFFFF8000319D8B0
  OS Version:	6_1_7601
  Service Pack:	1_0
  Product:	256_1

Files that help describe the problem:
  C:\Windows\Minidump\101611-34429-01.dmp
  C:\Users\Dylan\AppData\Local\Temp\WER-51199-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

I will post a recent zip of the .dmp files. It will be named todays date. 10/16/2011

 

[Sour]

Any help? This only happens when sleep mode is put on automatically. If I manually put it into sleep mode it will not get a BSOD.

 

[Sour]

Does anyone know the answer? The computer gets a BSOD when the Hard drive goes to sleep, not the sleep setting in the Power Options.

 

[Sour]

I just changed the hard drive settings to never turn off for now. Should fix it for now. Still wan't someone to tell me what is wrong if possible. Still haven't figured it out.

 

[Sour]

I was watching my computer and about every 30 minutes after i got off of it I would get the BSOD. It was 0x000000F4, or something like that. The BSOD never happens while I am on the computer.

Whenever I go back onto my computer I get Windows has recovered from an unexpected shutdown. Here is the Problem Details.

Problem signature:
  Problem Event Name:	BlueScreen
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033

Additional information about the problem:
  BCCode:	f4
  BCP1:	0000000000000003
  BCP2:	FFFFFA800929EB30
  BCP3:	FFFFFA800929EE10
  BCP4:	FFFFF8000319D8B0
  OS Version:	6_1_7601
  Service Pack:	1_0
  Product:	256_1

Files that help describe the problem:
  C:\Windows\Minidump\101611-34429-01.dmp
  C:\Users\Dylan\AppData\Local\Temp\WER-51199-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

I will post a recent zip of the .dmp files. It will be named todays date. 10/16/2011

 

[zigzag3143]

I was watching my computer and about every 30 minutes after i got off of it I would get the BSOD. It was 0x000000F4, or something like that. The BSOD never happens while I am on the computer.

Whenever I go back onto my computer I get Windows has recovered from an unexpected shutdown. Here is the Problem Details.

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033

Additional information about the problem:
  BCCode:    f4
  BCP1:    0000000000000003
  BCP2:    FFFFFA800929EB30
  BCP3:    FFFFFA800929EE10
  BCP4:    FFFFF8000319D8B0
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    256_1

Files that help describe the problem:
  C:\Windows\Minidump\101611-34429-01.dmp
  C:\Users\Dylan\AppData\Local\Temp\WER-51199-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

I will post a recent zip of the .dmp files. It will be named todays date. 10/16/2011

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.


These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[Sour]

I got one error, Here it is-

Tst   | Pass  | Failing Address |                Good  |      Bad  |         Err-Bits|     Count    |Chan
6      |    5   | 0014824d82c - 5250.3MB |  00020000|  00028000 |  00008000 |   1   |

They don't quite align correctly, but the | separates the parts.

Is this something to be concerned about?
I will do the Driver Verifier thing sometime soon.

 

[zigzag3143]

I got one error, Here it is-

Tst   | Pass  | Failing Address |                Good  |      Bad  |         Err-Bits|     Count    |Chan
6      |    5   | 0014824d82c - 5250.3MB |  00020000|  00028000 |  00008000 |   1   |

They don't quite align correctly, but the | separates the parts.

Is this something to be concerned about?
I will do the Driver Verifier thing sometime soon.

IF that is from memtest and it is saying you have errors what you do with them is up to you. Can you deal with the crashes?

 

[Sour]

I got one error, Here it is-

Tst   | Pass  | Failing Address |                Good  |      Bad  |         Err-Bits|     Count    |Chan
6      |    5   | 0014824d82c - 5250.3MB |  00020000|  00028000 |  00008000 |   1   |

They don't quite align correctly, but the | separates the parts.

Is this something to be concerned about?
I will do the Driver Verifier thing sometime soon.

IF that is from memtest and it is saying you have errors what you do with them is up to you. Can you deal with the crashes?

Is this what is causing the BSODs? If so, then I will be replacing my memory. What does this error mean exactly? What stick/motherboard is causing the error?

Should I still run the Driver Verifier to see what it does?

 

[zigzag3143]

I got one error, Here it is-

Tst   | Pass  | Failing Address |                Good  |      Bad  |         Err-Bits|     Count    |Chan
6      |    5   | 0014824d82c - 5250.3MB |  00020000|  00028000 |  00008000 |   1   |

They don't quite align correctly, but the | separates the parts.

Is this something to be concerned about?
I will do the Driver Verifier thing sometime soon.

IF that is from memtest and it is saying you have errors what you do with them is up to you. Can you deal with the crashes?

Is this what is causing the BSODs? If so, then I will be replacing my memory. What does this error mean exactly? What stick/motherboard is causing the error?

Your crashes are being caused by bad information being passed into or out of memory. It can be caused by bad ram, OR A DRIVER, (AS LISTED IN PREVIOUS POSTS) Read memtest. It says test each stick in each slot to determine which.

Should I still run the Driver Verifier to see what it does?

YES, the other possible cause of BSOD memory exceptions can be a corrupt, or poorly written driver.

 

[Sour]

Driver Verifier Just got done - Couldn't log in to my computer because of the dang Driver Verifier.
Thats the DMP File.

I uninstalled Daemon Tools - Since I read the dmp, and it looked like one of the files was from that.
But, I also know I had the BSOD's before I installed Daemon tools. Anyways I will add a complete list of all my dmps + System Health thing soon.

 

[zigzag3143]

Driver Verifier Just got done - Couldn't log in to my computer because of the dang Driver Verifier.
Thats the DMP File.

I uninstalled Daemon Tools - Since I read the dmp, and it looked like one of the files was from that.
But, I also know I had the BSOD's before I installed Daemon tools. Anyways I will add a complete list of all my dmps + System Health thing soon.

When uninstalling Daemon tools you missed one . This latest crash was driver verified and Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd.

Did you use the tool to remove daemon tools?

If so you will have to find and delte the above manually.

 

[Sour]

Driver Verifier Just got done - Couldn't log in to my computer because of the dang Driver Verifier.
Thats the DMP File.

I uninstalled Daemon Tools - Since I read the dmp, and it looked like one of the files was from that.
But, I also know I had the BSOD's before I installed Daemon tools. Anyways I will add a complete list of all my dmps + System Health thing soon.

When uninstalling Daemon tools you missed one . This latest crash was driver verified and Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd.

Did you use the tool to remove daemon tools?

If so you will have to find and delte the above manually.

What do you mean "Did you use the tool to remove daemon tools?"?
I just uninstalled it through the Uninstall Program/Files thing.
How exactly do I go about manually removing it?

If you mean Driver Verifier, no. I had to do restore to a system restore point. I had a BSOD on startup.

EDIT: It still gets BSODs

 

[zigzag3143]

Driver Verifier Just got done - Couldn't log in to my computer because of the dang Driver Verifier.
Thats the DMP File.

I uninstalled Daemon Tools - Since I read the dmp, and it looked like one of the files was from that.
But, I also know I had the BSOD's before I installed Daemon tools. Anyways I will add a complete list of all my dmps + System Health thing soon.

When uninstalling Daemon tools you missed one . This latest crash was driver verified and Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd.

Did you use the tool to remove daemon tools?

If so you will have to find and delte the above manually.

What do you mean "Did you use the tool to remove daemon tools?"?
I just uninstalled it through the Uninstall Program/Files thing.
How exactly do I go about manually removing it?

If you mean Driver Verifier, no. I had to do restore to a system restore point. I had a BSOD on startup.

EDIT: It still gets BSODs

When removing daemon tools you need to run a special tool

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.

If you didnt you can rename the driver to *.bak and it wont load or delete it

 

[Sour]

When uninstalling Daemon tools you missed one . This latest crash was driver verified and Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd.

Did you use the tool to remove daemon tools?

If so you will have to find and delte the above manually.

What do you mean "Did you use the tool to remove daemon tools?"?
I just uninstalled it through the Uninstall Program/Files thing.
How exactly do I go about manually removing it?

If you mean Driver Verifier, no. I had to do restore to a system restore point. I had a BSOD on startup.

EDIT: It still gets BSODs

When removing daemon tools you need to run a special tool

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.

If you didnt you can rename the driver to *.bak and it wont load or delete it

It says No SPTD version was detected. I also just did a recent Driver Verifier, and I didn't get that BSOD anymore. Now it has to do with HIDCLASS.SYS

Here is a recent compilation of the files(DMP/Performance Monitor)

 

[zigzag3143]

What do you mean "Did you use the tool to remove daemon tools?"?
I just uninstalled it through the Uninstall Program/Files thing.
How exactly do I go about manually removing it?

If you mean Driver Verifier, no. I had to do restore to a system restore point. I had a BSOD on startup.

EDIT: It still gets BSODs

When removing daemon tools you need to run a special tool

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.

If you didnt you can rename the driver to *.bak and it wont load or delete it

It says No SPTD version was detected. I also just did a recent Driver Verifier, and I didn't get that BSOD anymore. Now it has to do with HIDCLASS.SYS

Here is a recent compilation of the files(DMP/Performance Monitor)

Only one of the most recent crashes was related to HIDCLASS.SYS. HID (Human Interface Device) is an external device like a keyboard, mouse, etc. Since the process that was running at the time of the crash was Teamspeak I would start looking there.


If you have not run a system file check please do so.

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Let us know the results from the report at the end.


Of note:This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

 

[Sour]

As far as I can tell, nothing wrong.

 

[zigzag3143]

As far as I can tell, nothing wrong.

That is not the whole log. At the end of the test it could say one of three things. Did not find any violations, found violations and repaired them, or could not repair them.

Which was it?

 

[Sour]

'Did not find any violations'
I actually just reformatted in hopes of it disappearing, nope.
Anyways, I got a new compilation and I believe this could help.
The earlier dmps are most likely the Driver Verifier ones.
I recreated the average BSOD, so those should be them.
I just let my computer go to sleep, and it BSOD. Those are the DMPs.

 

[zigzag3143]

THe three most recent point to Disk hardware

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk

Please run a chkdsk first and download the mfr's HD test utility and run it

A- CHKDSK /R /F:

Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.

Do this for each hard drive on your system.

When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

Then reboot and let the test run.

It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.

See "CHKDSK LogFile" below in order to check the results of the test.


B- Elevated Command Prompt:

Go to Start and type in "cmd.exe" (without the quotes)

At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"


C-CHKDSK LogFile:

Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter

Expand the Windows logs heading, then select the Application log file entry.

Double click on the Source column header.

Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).

Copy/paste the results into your next post.