Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Random Win7 Freezes


  • Please log in to reply
7 replies to this topic

#1 DarnedComps

DarnedComps

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:04:43 AM

Posted 22 September 2010 - 10:13 PM

Hi All:
I just had a new system built and I'm afraid it's been slightly buggy from the get-go so I'm trying to track down the cause of the problem and would appreciate any help. If you need any other information please let me know. I'm semi-computer savvy, but am definitely not a programmer.

My system is:

- Windows 7 Pro (x64) Dual Boot with Win XP Pro (x32)
- Gigabyte GA-880GA-UD3H AM3
- Mushkin 996652B DDR3 PC3-10666 4GB Kit
- Kingston V 64GB SATAII SSD
- Western Digital 1TB SATAII 32MB
- Samsung SH-S243D 24X DVDRW Black SATA
- XFX Radeon HD5830 1GB GDDR5 PCI-E
- Arctic Cooling Fusion 550W Silent PSU

I normally run Win7 and the crashes usually consist of the entire system just freezing, nothing can be done to restore the system except to physically reset it. Recently I got my first BSOD, so I'm hoping that some of the information from it can help:

From BlueScreenView:
==================================================
Dump File : 092210-19702-01.dmp
Crash Time : 22-Sep-10 9:27:41 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04b5f028
Parameter 3 : 00000000`b269c000
Parameter 4 : 00000000`00000175
Caused By Driver : hal.dll
Caused By Address : hal.dll+12903
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\092210-19702-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

From WindDBg:

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004b5f028, b269c000, 175}

Probably caused by : hardware

Followup: MachineOwner
---------

3: 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: fffffa8004b5f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b269c000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000175, 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: iquana_1.14_wi

CURRENT_IRQL: f

STACK_TEXT:
fffff880`02fdda88 fffff800`033f9903 : 00000000`00000124 00000000`00000000 fffffa80`04b5f028 00000000`b269c000 : nt!KeBugCheckEx
fffff880`02fdda90 fffff800`02f91593 : 00000000`00000001 fffffa80`04b60d30 00000000`00000000 fffffa80`04b60d80 : hal!HalBugCheckSystem+0x1e3
fffff880`02fddad0 fffff800`033f95c8 : 00000000`00000728 fffffa80`04b60d30 fffff880`02fdde30 00000000`03272d00 : nt!WheaReportHwError+0x263
fffff880`02fddb30 fffff800`033f8f1a : fffffa80`04b60d30 fffff880`02fdde30 fffffa80`04b60d30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02fddc80 fffff800`033ece8f : 00000000`00000033 00000000`00000001 fffff880`02fddeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02fddcc0 fffff800`02e79fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02fddcf0 fffff800`02e79e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fdde30 00000001`40011569 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`03fcfca0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1`40011569


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

BC AdBot (Login to Remove)

 


#2 Zuhl3156

Zuhl3156

  • Members
  • 309 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Bensalem, Pa.
  • Local time:04:43 AM

Posted 22 September 2010 - 10:31 PM

Here is a utility that will let you read the dmp file and locate the faulting module:
http://www.nirsoft.net/utils/blue_screen_view.html

For some reason I can't help thinking that mixing a 32-bit OS and a 64-bit OS on the same system has 'Driver failure and conflict' written all over it.

#3 DarnedComps

DarnedComps
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:04:43 AM

Posted 22 September 2010 - 10:55 PM

Part of the text from above was generated using that utility, but from my understanding an error in hal.dll usually means a piece of hardware is actually crapping out. Also, I have to say that running different OS's definitely is not a recipe for failure. Obviously each OS has it's own partition so all drivers etc. are segregated.

Thanks for the reply.

Edited by DarnedComps, 22 September 2010 - 10:57 PM.


#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,266 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:43 AM

Posted 23 September 2010 - 08:40 AM

Well...you are right, it does seem to be hardware...but other reported errors of this type all seem to revolve around different hardware situations.

I would start with looking at Event Viewer errors for indications of hardware problems.

Louis

#5 Zuhl3156

Zuhl3156

  • Members
  • 309 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Bensalem, Pa.
  • Local time:04:43 AM

Posted 23 September 2010 - 09:58 AM

Here's something that might be relevant:
http://www.vistax64.com/vista-hardware-dev...0x00000124.html

#6 DarnedComps

DarnedComps
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:04:43 AM

Posted 25 September 2010 - 08:58 PM

Thanks Zuhl for the post but I don't think it applies in my case. Does anybody know how to properly read the mini-dump? Does the string referring to the AMD processor indicate that there might be a problem with my CPU?

Here's another dump from a different crash which again refers to the AMD processor cache:


*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004b7b028, b66cc000, 135}

Probably caused by : hardware

Followup: MachineOwner
---------

2: 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: fffffa8004b7b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b66cc000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000135, 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: fokker_planck_

CURRENT_IRQL: f

STACK_TEXT:
fffff880`02f6ba88 fffff800`02e1b903 : 00000000`00000124 00000000`00000000 fffffa80`04b7b028 00000000`b66cc000 : nt!KeBugCheckEx
fffff880`02f6ba90 fffff800`02fd8593 : 00000000`00000001 fffffa80`04b7cea0 00000000`00000000 fffffa80`04b7cef0 : hal!HalBugCheckSystem+0x1e3
fffff880`02f6bad0 fffff800`02e1b5c8 : 00000000`00000728 fffffa80`04b7cea0 fffff880`02f6be30 00000000`00000000 : nt!WheaReportHwError+0x263
fffff880`02f6bb30 fffff800`02e1af1a : fffffa80`04b7cea0 fffff880`02f6be30 fffffa80`04b7cea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02f6bc80 fffff800`02e0ee8f : 00000000`00000087 00000000`00000001 fffff880`02f6beb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02f6bcc0 fffff800`02ec0fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02f6bcf0 fffff800`02ec0e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02f6be30 fffff880`01647086 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`02f926a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!RtlAcquireScalableWriteLockAtDpcLevel+0x6


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

#7 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:08:43 AM

Posted 25 September 2010 - 10:18 PM

Have a read here: WHEA_UNCORRECTABLE_ERROR

#8 DarnedComps

DarnedComps
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:04:43 AM

Posted 29 September 2010 - 06:16 PM

Hey all;
So apparently the problem was caused because my Mushkin RAM doesn't like my motherboard. Upping the voltage appears to have solved the issue.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users