 | |
| |
| 20 Apr 2011 | #1 |
| | Problems with machine BSOD during idle time So I have been trolling around for a few days attempting to solve this issue on my own, but to no avail. I have run the BSOD Dump & System File Collection app as well as the System Health Report (both zipped and included). I have never "seen" the BSOD happen on this machine, I just come back to it and it has happened, so I am guessing it is happening during an idle time and isn't heat related so much as RAM/SLEEP/ETC. This morning I ran the "powercfg -h on" command that some have recommended, but I don't have a whole lot of faith in it. This seems to be happening about once or twice a day now, everyday. and I can't seem to find a reason why. This is a Gateway machine that is a bout a year old running OEM WIN HOME x64 with the original install. Everything was peachy until about a week ago. Not sure if this is relevant or not, but recently while watching youtube or listening to MP3s, I was getting a very annoying stutter sound in the audio. I disabled one of the two audio drivers to see if that would help (did that yesterday), but I am not sure if that is related to this issue. Also, you will see in the report it saying I don't have an antivirus installed, that isn't true. I do run Symantec Corporate. I also ran MDSCHED and rebooted to see how the memory did and it reported no errors. Any thoughts? Thanks in advance!!!! |
My System Specs | |
| 20 Apr 2011 | #2 |
| | 
Quote: Originally Posted by toozie21  So I have been trolling around for a few days attempting to solve this issue on my own, but to no avail. I have run the BSOD Dump & System File Collection app as well as the System Health Report (both zipped and included). I have never "seen" the BSOD happen on this machine, I just come back to it and it has happened, so I am guessing it is happening during an idle time and isn't heat related so much as RAM/SLEEP/ETC. This morning I ran the "powercfg -h on" command that some have recommended, but I don't have a whole lot of faith in it. This seems to be happening about once or twice a day now, everyday. and I can't seem to find a reason why. This is a Gateway machine that is a bout a year old running OEM WIN HOME x64 with the original install. Everything was peachy until about a week ago. Not sure if this is relevant or not, but recently while watching youtube or listening to MP3s, I was getting a very annoying stutter sound in the audio. I disabled one of the two audio drivers to see if that would help (did that yesterday), but I am not sure if that is related to this issue. Also, you will see in the report it saying I don't have an antivirus installed, that isn't true. I do run Symantec Corporate. I also ran MDSCHED and rebooted to see how the memory did and it reported no errors. Any thoughts? Thanks in advance!!!! Your .dmp file shows a stop error of 0x124 which is a general hardware error . A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try I would also remove Symantec if possible as it is frequently the cause of BSOD's Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\042011-40326-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`03056e50
Debug session time: Wed Apr 20 00:40:00.389 2011 (GMT-4)
System Uptime: 0 days 6:43:04.005
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8007957028, be000000, 800400}
Probably caused by : hardware
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007957028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: firefox.exe
CURRENT_IRQL: f
STACK_TEXT:
fffff800`00ba8a98 fffff800`03408903 : 00000000`00000124 00000000`00000000 fffffa80`07957028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`02f9f5a3 : 00000000`00000001 fffffa80`064c9ea0 00000000`00000000 fffffa80`064c9ef0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`034085c8 : 00000000`00000728 fffffa80`064c9ea0 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`03407f1a : fffffa80`064c9ea0 fffff800`00ba8e70 fffffa80`064c9ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`03407dd5 : 00000000`00000004 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`033fbe88 : 00000000`00000000 00000000`ffffffff 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`02e87fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`02e87e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 fffff880`0485ff02 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00ba2df8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : usbehci!EHCI_Get32BitFrameNumber+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007957028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: firefox.exe
CURRENT_IRQL: f
STACK_TEXT:
fffff800`00ba8a98 fffff800`03408903 : 00000000`00000124 00000000`00000000 fffffa80`07957028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`02f9f5a3 : 00000000`00000001 fffffa80`064c9ea0 00000000`00000000 fffffa80`064c9ef0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`034085c8 : 00000000`00000728 fffffa80`064c9ea0 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`03407f1a : fffffa80`064c9ea0 fffff800`00ba8e70 fffffa80`064c9ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`03407dd5 : 00000000`00000004 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`033fbe88 : 00000000`00000000 00000000`ffffffff 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`02e87fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`02e87e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 fffff880`0485ff02 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00ba2df8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : usbehci!EHCI_Get32BitFrameNumber+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
Followup: MachineOwner
--------- Might also want to run memtest to check you memory. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86.com - Memory Diagnostic 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. |
| My System Specs |
| 20 Apr 2011 | #3 |
| | OK, thank you for the help. Is there something you recommend that plays nice (antivirus-wise) with Windows 7? I will check out the 0x124 page and report back. Also, I ran the built in memory test, but I realize that the Memtest86 is probably better, so I will give that a shot. Lastly, so the firefox.exe listed in the bugcheck analysis is more of a red herring I guess? |
| My System Specs |
| . |
| |
 |
Problems with machine BSOD during idle time problems?
| Thread Tools | |
| Similar help and support threads for: Problems with machine BSOD during idle time | ||||
| Thread | Forum | |||
 BSOD after leaving computer idle after some time | BSOD Help and Support | |||
| BSOD When machine goes idle | BSOD Help and Support | |||
| BSOD 2nd time while computer was idle | BSOD Help and Support | |||
| BSOD when idle for a long period of time. | BSOD Help and Support | |||
| BSOD almost every time I boot my machine | BSOD Help and Support | |||
All times are GMT -5. The time now is 05:30 PM.
