Tech Support Forum banner
Status
Not open for further replies.
1 - 9 of 9 Posts

·
Registered
Joined
·
5 Posts
Discussion Starter · #1 ·
syste: windows XP 64



*******************************************************************************
* *
* 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: 0000000000000000
Arg2: fffff80000085bc0
Arg3: 00000000b6794000
Arg4: 0000000000000135
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

BUGCHECK_STR: 0x9C_AuthenticAMD
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8000080ef4c to fffff8000102e890
STACK_TEXT:
fffff800`00085b88 fffff800`0080ef4c : 00000000`0000009c 00000000`00000000 fffff800`00085bc0 00000000`b6794000 : 0xfffff800`0102e890
fffff800`00085b90 00000000`0000009c : 00000000`00000000 fffff800`00085bc0 00000000`b6794000 00000000`00000135 : 0xfffff800`0080ef4c
fffff800`00085b98 00000000`00000000 : fffff800`00085bc0 00000000`b6794000 00000000`00000135 00000000`00000000 : 0x9c

STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: CORRUPT_MODULELIST
Followup: MachineOwner
 

·
Registered
Joined
·
3,036 Posts
Minidump Collection:
Please collect your .dmps by doing the following:
  1. Go to C:\Windows and find the Minidump folder.
  2. Right click the folder.
  3. Click Copy.
  4. Go to C:\<username>\My Documents.
  5. Right click in an empty area of My Documents.
  6. Paste the file there (that link is for Windows 7, but the steps are the same).
  7. Compress (zip) the Minidump folder.
  8. Upload the .zip file to your next post.

MSINFO32 upload:
  1. Click Start.
  2. Click Run,
  3. type msinfo32.exe in the Open box,
  4. and then click OK.
  5. When it opens, go to File,
  6. Save -> Save as msinfo32.nfo and save in a place you will remember
  7. Let it finish the process of gathering and saving the system info
  8. Compress (zip) the .nfo file.
  9. Upload the .zip file to your next post.
 

·
Registered
Joined
·
3,036 Posts
I would recommend checking hardware and seeing what temperatures you get under stress and during idle. Please post back with both your idle and stress temperatures.

Prime95 Hardware Stress Testing Steps:
  1. Download Prime95.

  2. Navigate to where you saved the Prime95 files and unzip the files.

  3. Open Prime95 from the list, and then click Run in the dialog box if it opens.

  4. Click Just Stress Testing



  5. Run Small FFTs, In-place large FFTs, and Blend for a few hours each. Report back if CPU temperatures reach dangerous levels, if the system crashes, or if hardware errors are discovered by the diagnostics.



    Use the following programs to monitor the temperatures.

 

·
Registered
Joined
·
5 Posts
Discussion Starter · #6 ·
maximum heat case:
cpu 77 deg; motherboard 78deg;
other test:
both about 60deg;
computer did note crash during test. Actually it has not crashed for the last couple of days.
 

·
Registered
Joined
·
3,036 Posts
Temperatures are way too high. When was the last time you cleaned the dust out of the system?

Dust Removal:
To remove dust, follow the subsequent general procedure. If you have a desktop bought from Dell, HP, Sony, Lenovo, etc. make sure removing the desktop casing will not void your warranty first. Call the company if you are still under warranty and ask if it is okay to remove the casing and blow dust out. The procedure described is fine for laptops; just make sure no stickers are on panels saying if you remove the panel it will void the warranty.
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Remove the casing for a desktop, or remove any screwed on panels and disc drives for laptops.
  5. Blow out the dust inside by using a can of compressed air or a low pressure compressor. You will want to put the computer on a desk or table so you can maintain the can in an upright position if using a can of air. Blow into all crevices on the motherboard, heat sinks, cards, modules, etc. for a desktop. Blow into vents, opened panels, disc drive areas, USB ports, and the keyboard if it is a laptop. You may also want to blow inside the disc drive by replacing the drive to the laptop, starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step. For a desktop, you may also want to blow inside the disc drive by starting the computer, opening the drive, and then turning off the computer and removing all power as described above including the 30 second power button step.
  6. Replace casing for the desktop. Replace panels and disc drive (if you have not already done so) for the laptop.
  7. Plug power supplies in. AC adapter for the desktop. Battery and then AC Adapter for the laptop.
  8. Start the computer and see if performance is better.



Easier Laptop steps:

  1. Get a can of compressed air...
  2. Shut down and turn off your system...
  3. Unplug the system from any docking stations...
  4. Remove the AC Adapter and then remove the battery...
  5. Hold down the power button for 30 seconds to ensure all power is drained from the components. This closes the circuit and allows any remaining power to dissipate; it also clears the temporary memory of corruption and resets hardware/software connections. No permanent changes are made to the system doing this step...
  6. Use the can of compressed air to blow into every vent, crevice, keyboard key, USB port, VGA/monitor port, etc...
  7. Replace the battery and then plug in the AC Adapter...
  8. Replace the docking station...
  9. See how the system runs after doing all these steps...

WARNING:
  • Never use a vacuum cleaner or hair drier to clean dust out of your system!!
 

·
Registered
Joined
·
5 Posts
Discussion Starter · #8 ·
Thanks for the advice I will clean the dust out.
I still feel some other bugs may be there because some times the BSOD happened at fair low load right after the boot up.
 

·
Registered
Joined
·
3,036 Posts
Follow the steps to Test RAM with Memtest86+. You should run for at least 7-10 passes and may need up to 22 to find errors.

I would also recommend running Memtest86+ both after the system has been running for a while and after the system has been completely shut down for a while. Sometimes memory errors occur when the RAM is cold and not warm, or vice versa.
 
1 - 9 of 9 Posts
Status
Not open for further replies.
Top