Windows 7 Crashes Every Morning

[ndfan1993]

It seems like every morning around 30 minutes after I start up my machine I get a BSOD and a reboot, this has started occurring since I installed Windows 7 Ultimate on my machine. After it reboots it is fine, and if I leave it running all night it won't crash the next morning. Is there any reason why this is happening?

Here is what the error report looks like:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{CFC18EC0-96B1-4EBA-961B-622CAEE05B0A}" />

<EventID>100</EventID>

<Version>2</Version>

<Level>1</Level>

<Task>4002</Task>

<Opcode>34</Opcode>

<Keywords>0x8000000000010000</Keywords>

<TimeCreated SystemTime="2009-10-16T13:59:25.365358900Z" />

<EventRecordID>682</EventRecordID>

<Correlation ActivityID="{00000100-0000-0006-E856-5046684ECA01}" />

<Execution ProcessID="1700" ThreadID="5668" />

<Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel>

<Computer>Ryan-PC</Computer>

<Security UserID="S-1-5-19" />

</System>


- <EventData>
<Data Name="BootTsVersion">2</Data>

<Data Name="BootStartTime">2009-10-16T13:55:09.671600300Z</Data>

<Data Name="BootEndTime">2009-10-16T13:59:21.072113300Z</Data>

<Data Name="SystemBootInstance">39</Data>

<Data Name="UserBootInstance">37</Data>

<Data Name="BootTime">243446</Data>

<Data Name="MainPathBootTime">52974</Data>

<Data Name="BootKernelInitTime">23</Data>

<Data Name="BootDriverInitTime">8755</Data>

<Data Name="BootDevicesInitTime">1811</Data>

<Data Name="BootPrefetchInitTime">0</Data>

<Data Name="BootPrefetchBytes">0</Data>

<Data Name="BootAutoChkTime">0</Data>

<Data Name="BootSmssInitTime">33821</Data>

<Data Name="BootCriticalServicesInitTime">818</Data>

<Data Name="BootUserProfileProcessingTime">1476</Data>

<Data Name="BootMachineProfileProcessingTime">309</Data>

<Data Name="BootExplorerInitTime">2067</Data>

<Data Name="BootNumStartupApps">21</Data>

<Data Name="BootPostBootTime">190472</Data>

<Data Name="BootIsRebootAfterInstall">false</Data>

<Data Name="BootRootCauseStepImprovementBits">4194304</Data>

<Data Name="BootRootCauseGradualImprovementBits">4194304</Data>

<Data Name="BootRootCauseStepDegradationBits">0</Data>

<Data Name="BootRootCauseGradualDegradationBits">0</Data>

<Data Name="BootIsDegradation">false</Data>

<Data Name="BootIsStepDegradation">false</Data>

<Data Name="BootIsGradualDegradation">false</Data>

<Data Name="BootImprovementDelta">0</Data>

<Data Name="BootDegradationDelta">0</Data>

<Data Name="BootIsRootCauseIdentified">true</Data>

<Data Name="OSLoaderDuration">1862</Data>

<Data Name="BootPNPInitStartTimeMS">23</Data>

<Data Name="BootPNPInitDuration">3278</Data>

<Data Name="OtherKernelInitDuration">3849</Data>

<Data Name="SystemPNPInitStartTimeMS">5708</Data>

<Data Name="SystemPNPInitDuration">7289</Data>

<Data Name="SessionInitStartTimeMS">14416</Data>

<Data Name="Session0InitDuration">1455</Data>

<Data Name="Session1InitDuration">318</Data>

<Data Name="SessionInitOtherDuration">32046</Data>

<Data Name="WinLogonStartTimeMS">48238</Data>

<Data Name="OtherLogonInitActivityDuration">883</Data>

<Data Name="UserLogonWaitDuration">7954</Data>

</EventData>


</Event>

 

[H2SO4]

If you update some minidumps, it may be possible to explain why the machine is BSODing. Virtually every thread in this section has an explanation of what "minidumps" are and where to locate them on your machine.

 

[ndfan1993]

The minidump file on my machine is 824 MB....

 

[H2SO4]

The minidump file on my machine is 824 MB....

The ones in \Windows\Minidump, not "memory.dmp".

 

[ndfan1993]

The minidump file on my machine is 824 MB....

The ones in \Windows\Minidump, not "memory.dmp".

This folder is empty....

 

[H2SO4]

The minidump file on my machine is 824 MB....

The ones in \Windows\Minidump, not "memory.dmp".

This folder is empty....

You've got no minidumps and yet a new memory.dmp is created with every BSOD? Are you quite sure (about the new memory.dmp being created each time)?

 

[ndfan1993]

The ones in \Windows\Minidump, not "memory.dmp".

This folder is empty....

You've got no minidumps and yet a new memory.dmp is created with every BSOD? Are you quite sure (about the new memory.dmp being created each time)?

Yup, the new memory.dmp was created on Friday morning the last time I turned my machine on in the morning.

 

[H2SO4]

Yup, the new memory.dmp was created on Friday morning the last time I turned my machine on in the morning.

Minidumps are technically a summary of a full dump. In other words, the ability to correctly generate an intact full dump is a prerequisite for a minidump.

In situations where you're seeing a memory.dmp being created but not a corresponding minidump, the cause is almost always corruption or truncation of the full dump.

Make sure you're not rebooting the machine prematurely during the BSOD - let it finish when it says it's "dumping physical memory to disk".

 

[ndfan1993]

Yup, the new memory.dmp was created on Friday morning the last time I turned my machine on in the morning.

Minidumps are technically a summary of a full dump. In other words, the ability to correctly generate an intact full dump is a prerequisite for a minidump.

In situations where you're seeing a memory.dmp being created but not a corresponding minidump, the cause is almost always corruption or truncation of the full dump.

Make sure you're not rebooting the machine prematurely during the BSOD - let it finish when it says it's "dumping physical memory to disk".

Ok, I am not the one most of the times who forces the restart, it will start the dump get to around 30% and then restart, I have unchecked the auto restart when I get the BSOD but other times when I get there it says it is starting dumping but I could let it sit for 30 minutes and it doesn't even get to 1%....

 

[TGSoldier]

Right click on My Computer, go to properties, advanced, startup and recovery..

Make sure your settings correspond...

Note, that's an xp screen shot, just the lower boxes you're looking at.

Edit, untick the "Automatically Restart" button, this way, you can read what the BSOD says.

 

[ndfan1993]

Here is what mine currently looks like:

 

[H2SO4]

Ok, I am not the one most of the times who forces the restart, it will start the dump get to around 30% and then restart, I have unchecked the auto restart when I get the BSOD but other times when I get there it says it is starting dumping but I could let it sit for 30 minutes and it doesn't even get to 1%....

OK, that's why you never get a minidump. Since the minidump is essentially a summary of a full dump, the fact that there's something wrong during the creation of the full dump becomes a problem.

Some crash types end up mangling the OS components which are responsible for writing the dump. For example, if the disk I/O subsystem goes ga-ga, then it becomes difficult or impossible to dump the memory to disk. Other times the very same hardware problem which caused the BSOD also prevents memory dumping.

If unchecking the "auto restart" option doesn't work for you, try reviewing the contents of the system event log (run EVENTVWR). Sometimes the BSOD bugcheck code and parameters are recorded there just after the following reboot.

 

[ndfan1993]

Ok, I am not the one most of the times who forces the restart, it will start the dump get to around 30% and then restart, I have unchecked the auto restart when I get the BSOD but other times when I get there it says it is starting dumping but I could let it sit for 30 minutes and it doesn't even get to 1%....

OK, that's why you never get a minidump. Since the minidump is essentially a summary of a full dump, the fact that there's something wrong during the creation of the full dump becomes a problem.

Some crash types end up mangling the OS components which are responsible for writing the dump. For example, if the disk I/O subsystem goes ga-ga, then it becomes difficult or impossible to dump the memory to disk. Other times the very same hardware problem which caused the BSOD also prevents memory dumping.

If unchecking the "auto restart" option doesn't work for you, try reviewing the contents of the system event log (run EVENTVWR). Sometimes the BSOD bugcheck code and parameters are recorded there just after the following reboot.

Will do, shutting down the computer tonight and rebooting tomorrow morning should trigger it.

 

[ndfan1993]

Booted up this morning and 45 minutes in I did not get the BSOD but instead the computer just locked up and became totally unresponsive in which I had to hard reboot.

 

[ndfan1993]

This morning it restarted itself without any freezing or BSOD, or so I thought. Shortly after the reboot a windows message box popped up with the following information:

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

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800C024038
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\102109-38641-01.dmp
\AppData\Local\Temp\WER-410407-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Highlights - Microsoft Windows

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

 

[H2SO4]

This morning it restarted itself without any freezing or BSOD, or so I thought. Shortly after the reboot a windows message box popped up with the following information:

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

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800C024038
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
...

A stop 0x124 is a hardware error report being passed along by Windows. It's architecturally different to other "normal" bluescreen types.

If you're confident that the BIOS and hardware drivers are up-to-date, the machine is adequately cooled, and nothing is over-clocked, a stop 0x124 is reason enough to take it back to the shop, especially if it's under warranty.

 

[ndfan1993]

This morning it restarted itself without any freezing or BSOD, or so I thought. Shortly after the reboot a windows message box popped up with the following information:

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

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800C024038
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
...

A stop 0x124 is a hardware error report being passed along by Windows. It's architecturally different to other "normal" bluescreen types.

If you're confident that the BIOS and hardware drivers are up-to-date, the machine is adequately cooled, and nothing is over-clocked, a stop 0x124 is reason enough to take it back to the shop, especially if it's under warranty.

Bought it custom made from HP back in August....any reason why it would only occur if it was freshly rebooted in the morning 45 min. in and never again? The other thing that troubles me is that this only started occurring the day I installed Windows 7 Ultimate - running Vista Home Premium I never had this problem. Just curious questions....

 

[H2SO4]

Bought it custom made from HP back in August....any reason why it would only occur if it was freshly rebooted in the morning 45 min. in and never again? The other thing that troubles me is that this only started occurring the day I installed Windows 7 Ultimate - running Vista Home Premium I never had this problem. Just curious questions....

All valid questions which are impossible to answer at this level. It is possible that different drivers are exposing hardware flaws which were previously undetected, or that the machine has actually broken down in some way after it was purchased. Personally, I would not live with newly-purchased hardware logging machine check exceptions, but would instead expect the hardware vendor to do further troubleshooting on their own time - after giving me a replacement machine.

If you're interested, I wrote up a bit more info regarding 0x124 crashes on the Vista sister forum:

Please help with BSOD STOP 0x00000124 - Vista Forums

 

[ndfan1993]

Bought it custom made from HP back in August....any reason why it would only occur if it was freshly rebooted in the morning 45 min. in and never again? The other thing that troubles me is that this only started occurring the day I installed Windows 7 Ultimate - running Vista Home Premium I never had this problem. Just curious questions....

All valid questions which are impossible to answer at this level. It is possible that different drivers are exposing hardware flaws which were previously undetected, or that the machine has actually broken down in some way after it was purchased. Personally, I would not live with newly-purchased hardware logging machine check exceptions, but would instead expect the hardware vendor to do further troubleshooting on their own time - after giving me a replacement machine.

If you're interested, I wrote up a bit more info regarding 0x124 crashes on the Vista sister forum:

Please help with BSOD STOP 0x00000124 - Vista Forums

Thank you for your help, I will contact HP and see what can be done.

 

[ndfan1993]

Twist #2

I received this BSOD this morning: