BSOD after time of inactiveness/sleeping/hibernation

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.

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.

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.

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.

Script:

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

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.

Script:

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.

RAM - Test with Memtest86+



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.

Driver Verifier - Enable and Disable

I got one error, Here it is-

Code:

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.

Sour said:

I got one error, Here it is-

Code:

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?

zigzag3143 said:

Sour said:

I got one error, Here it is-

Code:

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?

Sour said:

zigzag3143 said:

Sour said:

I got one error, Here it is-

Code:

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.