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

help with hardware caused BSODs


  • Please log in to reply
13 replies to this topic

#1 timmybadshoes

timmybadshoes

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:07:22 AM

Posted 15 January 2010 - 11:49 AM

Hello, thought I'd come here over to hardware for some help. I built a system about 3 months ago and about 2 weeks on started getting these BSOD errors. Since then I've literally replaced everything besides cpu, heat sink and hard drive and still getting BSODs. In the event viewer here is what i see. If anyone could offer any advice on what may be causing this would be greatly appreciated. I'm running Windows 7 64bit but have tried XP and it dint stop.

System Specs:

Asus M4A78 Plus
Phenom II x3 710
XFX Radeon 4770 HD
2gb Kingston 800

Event log

A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor ID: 2

A fatal hardware error has occurred.

Component: AMD Northbridge
Error Source: Machine Check Exception
Error Type: Sync Error
Processor ID: 0

And this is the bug check:


BugCheck 124, {0, fffffa8002bdd8f8, 0, 0}

Probably caused by : hardware

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

1: 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: fffffa8002bdd8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,415 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:22 AM

Posted 15 January 2010 - 12:21 PM

Summary info at 9C, left column, http://www.aumha.org/a/stop.htm.

You could also try finding .dmp files on your system and then followoing Help Diagnosing BSODs And Crashes (BC) - http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/.

Is the heatsink/fan secure and operating properly?

Louis

#3 timmybadshoes

timmybadshoes
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:07:22 AM

Posted 15 January 2010 - 01:05 PM

I've reseated the heatsink and cpu and just sprayed it out with air can. I watch the temps and nothing unusual but is there a a way that could still be the problem because was considering changing it.

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,415 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:22 AM

Posted 15 January 2010 - 04:48 PM

Did you look for those .dmp files?

Louis

#5 timmybadshoes

timmybadshoes
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:07:22 AM

Posted 15 January 2010 - 07:02 PM

Yes I did. The .dmp file is always the same. here what the latest one was.


Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\011510-17768-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
Executable search path is:
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02e45e50
Debug session time: Fri Jan 15 16:30:28.568 2010 (GMT-6)
System Uptime: 0 days 0:00:07.347
Loading Kernel Symbols
................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8002c018f8, 0, 0}

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: fffffa8002c018f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`02f396f0 fffff800`02ec2a89 : fffffa80`02c018d0 fffffa80`0195e040 00000000`00000007 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02f39c10 fffff800`02da4547 : fffffa80`02c018d0 fffff800`02e1d5f8 fffffa80`0195e040 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02f39c40 fffff800`02d0cb95 : fffff800`02e7f360 fffffa80`0284ca58 fffffa80`0284ca50 fffffa80`0195e040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02f39c80 fffff800`02c87161 : fffff880`00e3be00 fffff800`02d0cb70 fffffa80`0195e040 02020003`03010303 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02f39cb0 fffff800`02f1d166 : 00000100`00010000 fffffa80`0195e040 00000000`00000080 fffffa80`0184fb30 : nt!ExpWorkerThread+0x111
fffff880`02f39d40 fffff800`02c58486 : fffff880`02d63180 fffffa80`0195e040 fffff880`02d6df80 33031b2f`03182a03 : nt!PspSystemThreadStartup+0x5a
fffff880`02f39d80 00000000`00000000 : fffff880`02f3a000 fffff880`02f34000 fffff880`03b29540 00000000`00000000 : nt!KxStartSystemThread+0x16


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_PRV

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

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

#6 hamluis

hamluis

    Moderator


  • Moderator
  • 56,415 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:22 AM

Posted 15 January 2010 - 08:05 PM

http://msdn.microsoft.com/en-us/library/bb725851.aspx

Not even an XP error, a typical Vista error from what I looked at on the Web.

Don't know if you've been overclocking the system...but I take any Windows error message about hardware at face value and prepare for the worst, while working to verify what the message is about.

Windows seems to think you have a bum CPU, IMO.

Louis

#7 timmybadshoes

timmybadshoes
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:07:22 AM

Posted 15 January 2010 - 08:59 PM

I haven't been over clocking and ran test on memory and hard drive and graphics card with 3dmark 06. Don't really know anything to test cpu but I've been thinking that may just be it also.

#8 timmybadshoes

timmybadshoes
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:07:22 AM

Posted 16 January 2010 - 11:13 PM

is it right its saying i have 2 graphic's cards when i only have one nad could that be causing this...dont know why it showing that.

Attached Files



#9 hamluis

hamluis

    Moderator


  • Moderator
  • 56,415 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:22 AM

Posted 17 January 2010 - 12:29 PM

Two display adapters in Device Manager...just indicates dual-monitor support for the video card/chip.

Louis

#10 timmybadshoes

timmybadshoes
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:07:22 AM

Posted 17 January 2010 - 07:35 PM

ok so after a BSOD filed day I noticed something. There seems to be no rhyme or reason to them. I got stop errors 0x050, 0x07e, 0x07f, 0x04e, 0x0124, 0x01e, 0x01, 0x09c and then some about ci.dll.

Edited by timmybadshoes, 17 January 2010 - 07:37 PM.


#11 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,378 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:07:22 AM

Posted 17 January 2010 - 08:26 PM

I'm wondering if you might have installed a driver by mistake that was meant to be used on windows Vista.
I'm also curious what would happen if, before the system crashes again you can re-install all your drivers, making sure they are the correct ones.

I know I've installed the wrong drivers in the past and had issues like yours.

Make sure the disks are not from another computer you own, Because that's what I did once years ago, I installed the ATI video drivers from the disk for another computer I owned. The card was an ATI card, but required a different set of drivers.

Just a thought.

Edited by MrBruce1959, 17 January 2010 - 08:28 PM.

Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 45 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:


#12 hamluis

hamluis

    Moderator


  • Moderator
  • 56,415 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:22 AM

Posted 18 January 2010 - 09:51 AM

If you want to discuss STOP errors...you need to post the entire first line of such.

Anytime that a file is specifically mentioned in an error message...that's important data for troubleshooting purposes.

Louis

#13 timmybadshoes

timmybadshoes
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:07:22 AM

Posted 20 January 2010 - 02:14 AM

Well I installed XP today and have come to the conclusion it must be the cpu. I've been getting blue screens, just much less frequently and they are 0x0000009c which according to Microsoft seems to mainly have to do with cpu defects. Last one produced this minidump.


Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini011910-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
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (3 procs) Free x86 compatible
Product: WinNt
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Jan 19 06:02:08.843 2010 (GMT-6)
System Uptime: 0 days 0:42:33.660
Loading Kernel Symbols
...............................................................
...............................................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, ba344050, f6002000, 6000136}

Probably caused by : Msfs.SYS ( Msfs!MsCommonCreate+34 )

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

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000000
Arg2: ba344050
Arg3: f6002000
Arg4: 06000136

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


BUGCHECK_STR: 0x9C_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 806e9bfb to 804f9f33

SYMBOL_ON_RAW_STACK: 1

STACK_ADDR_RAW_STACK_SYMBOL: ffffffffba344298

STACK_COMMAND: dds BA344298-0x20 ; kb

STACK_TEXT:
ba344278 0000ffff
ba34427c 00009200
ba344280 bfd003b7
ba344284 8000984f
ba344288 0000ffff
ba34428c 00009200
ba344290 8000ffff
ba344294 ba409310 Msfs!MsCommonCreate+0x34
ba344298 8000ffff
ba34429c ba409310 Msfs!MsCommonCreate+0x34
ba3442a0 8000ffff
ba3442a4 ba409310 Msfs!MsCommonCreate+0x34
ba3442a8 8003f120
ba3442ac 00000000
ba3442b0 8003f128
ba3442b4 00000000
ba3442b8 8003f130
ba3442bc 00000000
ba3442c0 8003f138
ba3442c4 00000000
ba3442c8 8003f140
ba3442cc 00000000
ba3442d0 8003f148
ba3442d4 00000000
ba3442d8 8003f150
ba3442dc 00000000
ba3442e0 8003f158
ba3442e4 00000000
ba3442e8 8003f160
ba3442ec 00000000
ba3442f0 8003f168
ba3442f4 00000000


FOLLOWUP_IP:
Msfs!MsCommonCreate+34
ba409310 668945dc mov word ptr [ebp-24h],ax

SYMBOL_NAME: Msfs!MsCommonCreate+34

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Msfs

IMAGE_NAME: Msfs.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 480251c6

FAILURE_BUCKET_ID: 0x9C_AuthenticAMD_Msfs!MsCommonCreate+34

BUCKET_ID: 0x9C_AuthenticAMD_Msfs!MsCommonCreate+34

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

2: kd> lmvm Msfs
start end module name
ba408000 ba40ca80 Msfs (pdb symbols) c:\symbols\msfs.pdb\CCBCBE0659AD4F778F44D4A38ADBF7F71\msfs.pdb
Loaded symbol image file: Msfs.SYS
Mapped memory image file: c:\symbols\Msfs.SYS\480251C64a80\Msfs.SYS
Image path: \SystemRoot\System32\Drivers\Msfs.SYS
Image name: Msfs.SYS
Timestamp: Sun Apr 13 13:32:38 2008 (480251C6)
CheckSum: 00005BB8
ImageSize: 00004A80
File version: 5.1.2600.5512
Product version: 5.1.2600.5512
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: MSFS.SYS
OriginalFilename: MSFS.SYS
ProductVersion: 5.1.2600.5512
FileVersion: 5.1.2600.5512 (xpsp.080413-2111)
FileDescription: Mailslot driver
LegalCopyright: © Microsoft Corporation. All rights reserved.

#14 hamluis

hamluis

    Moderator


  • Moderator
  • 56,415 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:05:22 AM

Posted 20 January 2010 - 11:10 AM

http://www.thewindowsclub.com/windows-7-st...e-screens-guide

http://support.microsoft.com/kb/925810

You might also post in BC Win 7 forum, http://www.bleepingcomputer.com/forums/f/167/windows-7/.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users