New
#11
Here is what mine currently looks like:
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.
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.
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
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....
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