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

Computer crash


  • Please log in to reply
7 replies to this topic

#1 ashete

ashete

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:03:48 AM

Posted 14 September 2011 - 01:25 AM

Hi,

I have a problem with my Gateway GM5072 with the following specs:
AMD Athlon™ 64 X2 dual-core processor 4200+
http://support.gateway.com/s/PC/R/1008848/1008848sp2.shtml

The computer crashes or hangs every few minutes. This has been going on since the time I got the computer. I had shipped it to Gateway for fixing but the problem never got completely fixed. I had given up on it but then I found this forum and thought that I would give a try to see if someone can help me. I am pasting a dmp log of the latest crash.

Thanks a lot in advance.

Ashish



Loading Dump File [C:\Users\LENOVO USER\Documents\Personal\Mini091311-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 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Sep 13 20:20:50.187 2011 (UTC - 7:00)
System Uptime: 0 days 0:06:11.875
Loading Kernel Symbols
...............................................................
...............................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {4, 8054d5f0, b2000000, 70f0f}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: 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: 00000004
Arg2: 8054d5f0
Arg3: b2000000
Arg4: 00070f0f

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

NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.

This error is documented in the following publication:

- Bios and Kernel Developers Guid for AMD Athlon® 64 and AMD Opteron® Processors
Bit Mask:

MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1011001000000000000000000000000000000000000001110000111100001111


VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.

UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.

EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.

PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.

BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
These errors match the format 0000 1PPT RRRR IILL



Concatenated Error Code:
--------------------------
_VAL_UC_EN_PCC_BUSCONNERR_30F

This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.

BUGCHECK_STR: 0x9C_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 806e7bff to 804f9c37

STACK_TEXT:
8054d5c8 806e7bff 0000009c 00000004 8054d5f0 nt!KeBugCheckEx+0x1b
8054d6f4 806e2c52 80042000 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd
8054d6f4 00000000 80042000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x4a


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x9C_AuthenticAMD_ANALYSIS_INCONCLUSIVE

BUCKET_ID: 0x9C_AuthenticAMD_ANALYSIS_INCONCLUSIVE

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

BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,582 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:48 AM

Posted 14 September 2011 - 06:53 AM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#3 hamluis

hamluis

    Moderator


  • Moderator
  • 55,545 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:48 AM

Posted 14 September 2011 - 06:56 AM

<<All questions regarding STOP 0x9C should be directed to the hardware manufacturer.>>

I think that I would do as suggested. In your case, that would be Gateway.

FWIW: See 9C at http://www.aumha.org/a/stop.htm for generic data available on this error.

Louis

Edited by hamluis, 14 September 2011 - 06:57 AM.


#4 ashete

ashete
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:03:48 AM

Posted 14 September 2011 - 01:53 PM

Hi Allan,

I am attaching the crash logs as you suggested.

Thanks a lot for looking into this.

Regards,

Ashish

Attached Files



#5 Allan

Allan

  • BC Advisor
  • 8,582 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:48 AM

Posted 14 September 2011 - 02:04 PM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply



#6 ashete

ashete
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:03:48 AM

Posted 14 September 2011 - 07:05 PM

ops, didn't read your response correctly. Here is the correct information:


==================================================
Dump File : Mini091311-02.dmp
Crash Time : 9/13/2011 10:55:28 PM
Bug Check String : BUGCODE_USB_DRIVER
Bug Check Code : 0x000000fe
Parameter 1 : 0x00000005
Parameter 2 : 0x89b200e0
Parameter 3 : 0x10de026d
Parameter 4 : 0x88a35958
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+ecc3
File Description : USB 1.1 & 2.0 Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Processor : 32-bit
Crash Address : ntoskrnl.exe+22c37
Stack Address 1 : USBPORT.SYS+ecc3
Stack Address 2 : USBPORT.SYS+1b516
Stack Address 3 : usbohci.sys+18f3
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini091311-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini091311-01.dmp
Crash Time : 9/13/2011 8:22:55 PM
Bug Check String : MACHINE_CHECK_EXCEPTION
Bug Check Code : 0x0000009c
Parameter 1 : 0x00000004
Parameter 2 : 0x8054d5f0
Parameter 3 : 0xb2000000
Parameter 4 : 0x00070f0f
Caused By Driver : hal.dll
Caused By Address : hal.dll+5bff
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Processor : 32-bit
Crash Address : ntoskrnl.exe+22c37
Stack Address 1 : hal.dll+5bff
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini091311-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini090609-01.dmp
Crash Time : 9/6/2009 5:14:40 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x80acea08
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0xf7934737
Caused By Driver : usbohci.sys
Caused By Address : usbohci.sys+1737
File Description : OHCI USB Miniport Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Processor : 32-bit
Crash Address : ntoskrnl.exe+47ee6
Stack Address 1 : ntoskrnl.exe+2d12e
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini090609-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 65,536
==================================================

#7 ashete

ashete
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:03:48 AM

Posted 14 September 2011 - 07:07 PM

One more bit of information - the computer hangs/freezes much more frequently than it crashes. I don't have any logs of the hangs/freezes. I have looked into the event viewer but there doesn't seem to be any information captured at the time of the hang.

Thanks

Ashish

#8 Allan

Allan

  • BC Advisor
  • 8,582 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:48 AM

Posted 15 September 2011 - 07:03 AM

First, if this has been going on since you got the system and if Gateway can't fix it - and if it's still under warranty - I'd ask them to replace it. If that is not an options:

1) Look in device manager - any errors?

2) Go to the Gateway website and check for an updated chipset driver and bios version. If they exist, install the driver and flash the bios.

3) Other than the bsod's, does everything work as expected (usb ports in particular)?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users