BSoD Problems


  1. sconeseeker
    Posts : 5
    Windows 7 Ultimate x64
       New #1

    BSoD Problems


    Ive been having many bsods when playing games, I have attached file as requested here is the other relivent information:

    Windows 7 Ultimate
    x64
    Fully Updated
    Full Retail Version

    Age of Hardware: between 0 - 1 years (hard drive is around 2 or 3 year)

    Age of OS installation: 0 - 1 year (installed recently to try and counter bsods (didnt work ^^))

    Any help would be appriciated.
    Thanks, Jon.


    EDIT: PROBLEM HAS BEEN SOLVED THANKS!!!!
    Last edited by sconeseeker; 06 Mar 2011 at 13:52. Reason: problem solved.
      My Computer
    Quote Quote

  3. Maguscreed
    Posts : 6,668
    Windows 7 x64
       New #2

    Code:
    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: fffffa8004a4b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b66b4000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000145, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Crysis2Demo.ex

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02ddca88 fffff800`02c1b903 : 00000000`00000124 00000000`00000000 fffffa80`04a4b028 00000000`b66b4000 : nt!KeBugCheckEx
fffff880`02ddca90 fffff800`02dd85a3 : 00000000`00000001 fffffa80`04944a60 00000000`00000000 fffffa80`04944ab0 : hal!HalBugCheckSystem+0x1e3
fffff880`02ddcad0 fffff800`02c1b5c8 : 00000000`00000728 fffffa80`04944a60 fffff880`02ddce30 00000000`1a84b400 : nt!WheaReportHwError+0x263
fffff880`02ddcb30 fffff800`02c1af1a : fffffa80`04944a60 fffff880`02ddce30 fffffa80`04944a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02ddcc80 fffff800`02c0ee8f : 00000000`1d48ad68 00000000`00000001 fffff880`02ddceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02ddccc0 fffff800`02cc0fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02ddccf0 fffff800`02cc0e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02ddce30 00000000`20046d73 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`22bcfac8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x20046d73


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

Followup: MachineOwner
---------
    Definitely a hardware error, usually see this one when the machine is overclocked.
    Of course the crash was caused by a unpatched released ahead of schedule demo too.
      My Computer
    Quote Quote

  4. sconeseeker
    Posts : 5
    Windows 7 Ultimate x64
    Thread Starter
       New #3

    Maguscreed said:
    Code:
    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: fffffa8004a4b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b66b4000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000145, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Crysis2Demo.ex

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02ddca88 fffff800`02c1b903 : 00000000`00000124 00000000`00000000 fffffa80`04a4b028 00000000`b66b4000 : nt!KeBugCheckEx
fffff880`02ddca90 fffff800`02dd85a3 : 00000000`00000001 fffffa80`04944a60 00000000`00000000 fffffa80`04944ab0 : hal!HalBugCheckSystem+0x1e3
fffff880`02ddcad0 fffff800`02c1b5c8 : 00000000`00000728 fffffa80`04944a60 fffff880`02ddce30 00000000`1a84b400 : nt!WheaReportHwError+0x263
fffff880`02ddcb30 fffff800`02c1af1a : fffffa80`04944a60 fffff880`02ddce30 fffffa80`04944a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02ddcc80 fffff800`02c0ee8f : 00000000`1d48ad68 00000000`00000001 fffff880`02ddceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02ddccc0 fffff800`02cc0fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02ddccf0 fffff800`02cc0e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02ddce30 00000000`20046d73 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`22bcfac8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x20046d73


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

Followup: MachineOwner
---------
    Definitely a hardware error, usually see this one when the machine is overclocked.
    Of course the crash was caused by a unpatched released ahead of schedule demo too.
    thanks for confirming i dont remember overclocking my system but my friend believes it to be my processor so ill look into it
      My Computer
    Quote Quote

  6. DeanP
    Posts : 2,566
    Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
       New #4

    Stop 0x124 - what it means and what to try
      My Computer
    Quote Quote

  7. sconeseeker
    Posts : 5
    Windows 7 Ultimate x64
    Thread Starter
       New #5

    Maguscreed said:
    Code:
    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: fffffa8004a4b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b66b4000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000145, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Crysis2Demo.ex

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02ddca88 fffff800`02c1b903 : 00000000`00000124 00000000`00000000 fffffa80`04a4b028 00000000`b66b4000 : nt!KeBugCheckEx
fffff880`02ddca90 fffff800`02dd85a3 : 00000000`00000001 fffffa80`04944a60 00000000`00000000 fffffa80`04944ab0 : hal!HalBugCheckSystem+0x1e3
fffff880`02ddcad0 fffff800`02c1b5c8 : 00000000`00000728 fffffa80`04944a60 fffff880`02ddce30 00000000`1a84b400 : nt!WheaReportHwError+0x263
fffff880`02ddcb30 fffff800`02c1af1a : fffffa80`04944a60 fffff880`02ddce30 fffffa80`04944a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02ddcc80 fffff800`02c0ee8f : 00000000`1d48ad68 00000000`00000001 fffff880`02ddceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02ddccc0 fffff800`02cc0fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02ddccf0 fffff800`02cc0e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02ddce30 00000000`20046d73 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`22bcfac8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x20046d73


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

Followup: MachineOwner
---------
    Definitely a hardware error, usually see this one when the machine is overclocked.
    Of course the crash was caused by a unpatched released ahead of schedule demo too.
    Me and my friend have just discovered that when I bought my processor from overclockers they had overclocked it is there any way to 'underclock' it back down to a 3.2 GHz because my processor is at 3.6 GHz
      My Computer
    Quote Quote

  8. DeanP
    Posts : 2,566
    Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
       New #6

    Reset the settings in the BIOS.
      My Computer
    Quote Quote

  10. sconeseeker
    Posts : 5
    Windows 7 Ultimate x64
    Thread Starter
       New #7

    im rather new to BIOS and I wouldn't like to ruin my computer if I make a mistake any way I can get a guide?
      My Computer
    Quote Quote

  11. sconeseeker
    Posts : 5
    Windows 7 Ultimate x64
    Thread Starter
       New #8

    I have reset my bios and processor has been underclocked back to a 3.2 GHz no further BSoDs thanks guys!
      My Computer
    Quote Quote

  12. Maguscreed
    Posts : 6,668
    Windows 7 x64
       New #9

    Good deal, doubt you were getting any real performance boost out of such a small overclock anyhow.
      My Computer
    Quote Quote

  13. DeanP
    Posts : 2,566
    Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
       New #10

    sconeseeker said:
    I have reset my bios and processor has been underclocked back to a 3.2 GHz no further BSoDs thanks guys!
    Glad we could help. Sounds like if overclocking was the culprit.
    Let us know if you need anything else.

    Regards...
    Dean
      My Computer
    Quote Quote

 

  Related Discussions
After BSOD problems (0x00000050), I took my two month old Dell desktop back to Geek Squad under warranty. Said problem wasn't hardware, but software, and would charge to fix. I took it home and reinstalled Win 7. BSOD (0x0000007b) with a Dell installation CD, but otherwise fine except it keeps...
Howdy all, new user here looking to isolate a blue screen problem that makes me quite sad as it's becoming rather annoying. A friend a while back (2 years-ish) solved a bsod problem with you guy's help and I thought I would do the same. I read and followed the "Blue Screen of Death (BSOD)...
Hi I hope I'm placing this in the right section, if not, then could someone tell me where to put it and I'll post it again. I've got a Samsung RV510 laptop with Windows 7 HP 64 bit. About 2 weeks ago, I was watching a Youtube video, had Spotify and Facebook open too, and my computer...
BSOD Different problems Help!!
in BSOD Help and Support

Hello All See attached mini dump files Computer was at Idle.turned monitor back on and greeted with a BSOD 60190 60191
hi guys i dunno why i have many problems with win7 since installation and so far btw i wrote many topics before about my installation and eventually i didn't found any solution so i took my pc to computer shop and they solve the problem after that i installed win7 without any problems...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 15:10.
Find Us