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.


BSOD during windows booting up

  • Please log in to reply
3 replies to this topic

#1 TimMY.Net


  • Members
  • 2 posts
  • Local time:08:02 AM

Posted 11 March 2009 - 10:20 AM

[[sorry for my english not well...]]

Hi there...this is my first time to post new topic here.

My computer is not working while windows booting up and then it show BSOD. Sometime mainboard can't POST when I power on my PC.

I test ram, PSU, harddisk is working normal and flash new BIOS version the problem not fixed. I doube problem may cause from mainboard? I use Debugging tool to track dumpfile but I can't understand them.

Everybody please kindly verify memory dump from my computer. T T

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

Loading Dump File [C:\Documents and Settings\tim\Desktop\Minidump\Mini030709-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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Mar 7 01:17:32.781 2009 (GMT+7)
System Uptime: 0 days 4:49:26.500
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* *
* Bugcheck Analysis *
* *

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, 8054e5f0, b2000000, 1080080f}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner

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

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
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
FW reported a fatal MCA.
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.
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
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
Arg1: 00000000
Arg2: 8054e5f0
Arg3: b2000000
Arg4: 1080080f

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:

- IA-32 Intel® Architecture Software Developer's Manual
Volume 3: System Programming Guide

Bit Mask:

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

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:

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_GenuineIntel




LAST_CONTROL_TRANSFER: from 806e9bfb to 804f9f43

8054e5c8 806e9bfb 0000009c 00000000 8054e5f0 nt!KeBugCheckEx+0x1b
8054e6f4 806e4c52 80042000 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd
8054e6f4 00000000 80042000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x4a




MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image




Followup: MachineOwner

Followup: MachineOwner

0: kd> lmvm Unknown_Module
start end module name


Thank you everyone for advised...

BC AdBot (Login to Remove)


#2 hamluis



  • Moderator
  • 56,302 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:02 PM

Posted 11 March 2009 - 10:37 AM

Hi :thumbsup:.

Don't worry about your English :flowers:, there are more important things to consider.

Do you have this program installed on your system, http://www.freewarefiles.com/AIMP_program_28231.html ?

If so, I suggest uninstalling and then reinstalling it anew...it may be damaged.

The comment about the board not POSTing...that's something that concerns me. A corrupt/damaged program should have no impact on POST.

System manufacturer and model...or motherboard manufacturer and model?

What sort of RAM testing did you do?


#3 TimMY.Net

  • Topic Starter

  • Members
  • 2 posts
  • Local time:08:02 AM

Posted 11 March 2009 - 11:08 AM

็Hello hamluis,

I test memory four time each time insert only one memory to my PC the problem still found on each memory sometime it working normal :thumbsup:. I doubeful very much.

You can view my PC information in attachment file.

Thank for your help. :flowers:

#4 hamluis



  • Moderator
  • 56,302 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:02 PM

Posted 11 March 2009 - 11:28 AM

The problem with testing RAM...it could be one of the memory slots on the motherboard, it could be more than one...it could be one of the modules, it could be more than one...and it could be any combination of such.

What I do...if I have a motherboard with 4 RAM slots, I do a full run using Memtest (takes about 2.5 hours on this system). If I have an error, I look to see which module it is...then I remove the RAM from that module (label it) and put it aside.

I then move a module which showed no errors...to the same motherboard slot...and run Memtest again. That's how I find out if it's the motherboard slot or the RAM module itself.

I do this until I find that I have no errors, running at least two modules in 2 slots. Once I know those slots and those two RAM modules are good...I go back to modules I've removed and try them in known good slots. If I still have problems, I try adjusting the BIOS bus speed...to see if the modules will work at a slower speed or a faster speed.

I do this sort of thing until I think I understand how to overcome what I view as "the problem."


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users