Cyntek Posted June 12, 2008 Share Posted June 12, 2008 (edited) Hello, I have been experiencing some random freezing issues and reboots. I'm running windows xp with all the latest updates and hotfixes available for windows xp. I have installed the sp3 for winxp pro and have successfully ran individual tests and all my hardware and memory and they all seem to okay. However, I still get these random reboots. Just the other day I experienced the bsod and windows did a memory.dump and I was not able to view it without a debugger program so I downloaded the program and installed it, but I am not comprehending what this crash means. So I am here to find out what my crash dump mean if any one of you guys can help me out I would really appreciate it. If you need any further info please let me know.My rig:ECS KN1 Sli Lite Rev:0AAMD X2 4600 + Stock clockEVGA 7950 GT KO 512MB Stock clock Pci-e1 Gb Generic Ram Dual Channel1 Gb Kingston Hyper X RamLite On DVD +Rw 160 Gb Maxtor Sata HD500 Gb Hitachi DeskStar Sata Hd320 Gb Western Digital Pata Eide hdAudigy 2 value sound cardHere's the memory dump log:Microsoft ® Windows Debugger Version 6.8.0004.0 X86Copyright © Microsoft Corporation. All rights reserved.Loading Dump File [C:\Documents and Settings\Cyntek\My Documents\Memory dump\Mini061208-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: *** Invalid ******************************************************************************** Symbol loading may be unreliable without a symbol search path. ** Use .symfix to have the debugger choose a symbol path. ** After setting your symbol path, use .reload to refresh symbol locations. *****************************************************************************Executable search path is: ********************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************Unable to load image ntoskrnl.exe, Win32 error 0n2*** WARNING: Unable to verify timestamp for ntoskrnl.exe*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeWindows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatibleProduct: WinNt, suite: TerminalServer SingleUserTSKernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720Debug session time: Thu Jun 12 01:54:09.625 2008 (GMT-7)System Uptime: 0 days 6:59:30.312********************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************Unable to load image ntoskrnl.exe, Win32 error 0n2*** WARNING: Unable to verify timestamp for ntoskrnl.exe*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeLoading Kernel Symbols.....................................................................................................................................Loading User SymbolsLoading unloaded module list...............*** WARNING: Unable to verify timestamp for hal.dll*** ERROR: Module load completed but symbols could not be loaded for hal.dll******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 9C, {4, 8054e5f0, b2000000, 70f0f}***** Kernel symbols are WRONG. Please fix symbols to do analysis.**************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ************************************************************************************************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ ******************************************************************************************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************Probably caused by : ntoskrnl.exe ( nt+22f33 )Followup: MachineOwner---------0: kd> .reloadUnable to load image ntoskrnl.exe, Win32 error 0n2*** WARNING: Unable to verify timestamp for ntoskrnl.exeLoading Kernel Symbols.....................................................................................................................................Loading User SymbolsLoading unloaded module list...............0: kd> !analyze -v*** WARNING: Unable to verify timestamp for hal.dll******************************************************************************** ** 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 errorArguments:Arg1: 00000004Arg2: 8054e5f0Arg3: b2000000Arg4: 00070f0fDebugging 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 ---------------------------------------------------------------- 1011001000000000000000000000000000000000000001110000111100001111VAL - 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_AuthenticAMDCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: DRIVER_FAULTPROCESS_NAME: IdleLAST_CONTROL_TRANSFER: from 806e9bfb to 804f9f33STACK_TEXT: 8054e5c8 806e9bfb 0000009c 00000004 8054e5f0 nt!_woutput+0x4048054e6f4 806e4c52 80042000 00000000 00000000 hal!_allshr+0xb00000000 00000000 00000000 00000000 00000000 hal!HalpWriteCmosTime+0xceSTACK_COMMAND: kbFOLLOWUP_IP: nt!_woutput+404804f9f33 5d pop ebpSYMBOL_STACK_INDEX: 0SYMBOL_NAME: nt!_woutput+404FOLLOWUP_NAME: MachineOwnerMODULE_NAME: ntIMAGE_NAME: ntoskrnl.exeDEBUG_FLR_IMAGE_TIMESTAMP: 4802516aFAILURE_BUCKET_ID: 0x9C_AuthenticAMD_nt!_woutput+404BUCKET_ID: 0x9C_AuthenticAMD_nt!_woutput+404Followup: MachineOwner--------- Edited June 13, 2008 by Tarun I like the codebox BBCode, don't you? :) Link to comment Share on other sites More sharing options...
Guest elarifr Posted June 12, 2008 Share Posted June 12, 2008 hithis dump only say this seems to be an hardware issue !as i can see ecs kn1 board are from mid 2005those board use chimical capacitor and a small fan on the chipset you can check 1/ if small fan is ok. (i have got one board with a fan like this with the retain clip desoldered from board so that it had bad thermal contact on th chipset)2/ check capacitor around the cpu, the top (& bottom) must be clean / plate and not curvedhope you'll better understand my english than in french elarifrhttp://accedinfo.com Link to comment Share on other sites More sharing options...
Cyntek Posted June 12, 2008 Author Share Posted June 12, 2008 hithis dump only say this seems to be an hardware issue !as i can see ecs kn1 board are from mid 2005those board use chimical capacitor and a small fan on the chipset you can check 1/ if small fan is ok. (i have got one board with a fan like this with the retain clip desoldered from board so that it had bad thermal contact on th chipset)2/ check capacitor around the cpu, the top (& bottom) must be clean / plate and not curvedhope you'll better understand my english than in french elarifrhttp://accedinfo.comThanks for the reply, but I don't understand how it can be a hardware failure when the computer runs fine with another OS for example "ubuntu" I have no issues when running Linux. This issue is only on windows. Link to comment Share on other sites More sharing options...
Cyntek Posted June 12, 2008 Author Share Posted June 12, 2008 I also was looking into the " Event Viewer " and looked in the " System log " and found an system error with a red cirlce and an white X running through it. Here is what the Properties says about.EventDate: 6/12/2008 Source: System ErrorTime: 11:34:05 AM Catagory: (102)Type: Error Event ID: 1003User: N/AComputer: AMDX24600Description:Error code 0000009c, parameter1 00000004, parameter2 8054e5f0, parameter3 b2000000, parameter4 00070f0f.Data: Bytes: 0000: 53 79 73 74 65 6d 20 45 System E0008: 72 72 6f 72 20 20 45 72 rror Er0010: 72 6f 72 20 63 6f 64 65 ror code0018: 20 30 30 30 30 30 30 39 00000090020: 63 20 20 50 61 72 61 6d c Param0028: 65 74 65 72 73 20 30 30 eters 000030: 30 30 30 30 30 34 2c 20 000004, 0038: 38 30 35 34 65 35 66 30 8054e5f00040: 2c 20 62 32 30 30 30 30 , b200000048: 30 30 2c 20 30 30 30 37 00, 00070050: 30 66 30 66 0f0f Data: Words:0000: 74737953 45206d65 726f7272 724520200010: 20726f72 65646f63 30303020 393030300020: 50202063 6d617261 72657465 303020730030: 30303030 202c3430 34353038 306635650040: 3262202c 30303030 202c3030 373030300050: 66306630 Woudl this be the cause of the random freezes and reboots ? Link to comment Share on other sites More sharing options...
PsiMoon314 Posted June 12, 2008 Share Posted June 12, 2008 Hi,http://support.microsoft.com/kb/329284Kind RegardsSimon Link to comment Share on other sites More sharing options...
Cyntek Posted June 12, 2008 Author Share Posted June 12, 2008 Hi,http://support.microsoft.com/kb/329284Kind RegardsSimonThanks for the link, but it was not very helpful.However, here is what the windbg has on it?Microsoft ® Windows Debugger Version 6.8.0004.0 X86Copyright © Microsoft Corporation. All rights reserved.Loading Dump File [C:Documents and SettingsCyntekMy DocumentsMemory dumpMini061208-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: C:Documents and SettingsCyntekMy DocumentsSymbolsExecutable search path is: Unable to load image ntoskrnl.exe, Win32 error 0n2*** WARNING: Unable to verify timestamp for ntoskrnl.exeWindows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatibleProduct: WinNt, suite: TerminalServer SingleUserTSKernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720Debug session time: Thu Jun 12 01:54:09.625 2008 (GMT-7)System Uptime: 0 days 6:59:30.312Unable to load image ntoskrnl.exe, Win32 error 0n2*** WARNING: Unable to verify timestamp for ntoskrnl.exeLoading Kernel Symbols.....................................................................................................................................Loading User SymbolsLoading unloaded module list...............*** WARNING: Unable to verify timestamp for hal.dll******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 9C, {4, 8054e5f0, b2000000, 70f0f}Probably caused by : ntoskrnl.exe ( nt!_woutput+404 )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 errorArguments:Arg1: 00000004Arg2: 8054e5f0Arg3: b2000000Arg4: 00070f0fDebugging 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 ---------------------------------------------------------------- 1011001000000000000000000000000000000000000001110000111100001111VAL - 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_AuthenticAMDCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: DRIVER_FAULTPROCESS_NAME: IdleLAST_CONTROL_TRANSFER: from 806e9bfb to 804f9f33STACK_TEXT: 8054e5c8 806e9bfb 0000009c 00000004 8054e5f0 nt!_woutput+0x4048054e6f4 806e4c52 80042000 00000000 00000000 hal!_allshr+0xb00000000 00000000 00000000 00000000 00000000 hal!HalpWriteCmosTime+0xceSTACK_COMMAND: kbFOLLOWUP_IP: nt!_woutput+404804f9f33 5d pop ebpSYMBOL_STACK_INDEX: 0SYMBOL_NAME: nt!_woutput+404FOLLOWUP_NAME: MachineOwnerMODULE_NAME: ntIMAGE_NAME: ntoskrnl.exeDEBUG_FLR_IMAGE_TIMESTAMP: 4802516aFAILURE_BUCKET_ID: 0x9C_AuthenticAMD_nt!_woutput+404BUCKET_ID: 0x9C_AuthenticAMD_nt!_woutput+404Followup: MachineOwner--------- Link to comment Share on other sites More sharing options...
cluberti Posted June 13, 2008 Share Posted June 13, 2008 I understand that you claim to have no errors in Ubuntu, but is it possible that Ubuntu is simply not kernel panic'ing when the INT18 is sent from the processor, thus you don't see the error (again, it's not an error that will cause your box to spontaneously reboot or anything, but it IS a hardware error you should take care of before something else breaks - that's why Windows is bugchecking)?According to the bugcheck code and the parameters, your problem appears to be thus:Bug Check 0x9C: MACHINE_CHECK_EXCEPTIONThe MACHINE_CHECK_EXCEPTION bug check has a value of 0x0000009C. This bug check indicates that a fatal machine check exception has occurred.ParametersThe four parameters that are listed in the message have different meanings, depending on the processor type.If the processor is based on a newer x86-based architecture and has the MCA feature and the MCE feature (for example, any Intel Processor of family 6 or higher, such as Pentium Pro, Pentium IV, or Xeon), or if the processor is an x64-based processor, the parameters have the following meaning.Parameter Description 1 The bank number 2 The address of the MCA_EXCEPTION structure 3 The high 32 bits of MCi_STATUS MSR for the MCA bank that had the error 4 The low 32 bits of MCi_STATUS MSR for the MCA bank that had the errorIn looking at the document "BIOS and Kernel Developer's Guide for AMD Athlon 64 and AMD Opteron Processors" from AMD which discusses the Machine Check architecture and codes, it appears your processor told the OS quite a bit. Lert's see what it said...Looking at the error codes for the actual BUS error:Wdog error 0111 BUS GEN 1 GEN GEN LGI can tell you that the CPU reported the BUS error as a "GENeric error", the requested operation timed out (1), it was a GENeric memory error, and it was a GENeric cache level error (meaning it was probably DRAM, not a CPU cache issue)Digging deeper into the Machine Check bits, the following is displayed:MA Model Specific MCAO ID Other Information Error Code Error CodeVV SDP ___________|____________ _______|_______ _______|______AEUECRC| | | |LRCNVVC| | | |^^^^^^^| | | |6 5 4 3 2 13210987654321098765432109876543210987654321098765432109876543210----------------------------------------------------------------1011001000000000000000000000000000000000000001110000111100001111The above chart means thus:VAL (bit 63) is set to 1, meaning a VALID ERROR was detectedUC (bit 61) is set to 1, meaning the error is NOT correctable by hardware (so the machine should STOP whatever it's doing)EN (bit 60) is set to 1, meaning that error reporting is enabled for this error in the actual MCA control register, so we should report thisPCC (bit 57) is set to 1, meaning the actual state of the CPU may actually be corrupted because of the error condition, and as such whatever was executing should stop to avoid potential data loss (hence why Windows actually bugchecks - this is serious)Bits 18, 17, and 16 are set to 1, meaning the extended error code came from the northbridge on the motherboard, and it reads 0111 (19 -> 16), which means the error was a BUS error, indicating an error in the HyperTransport or actual DRAM errorsBits 11, 10, and 09 are reserved, and are ignoredBit 08 is set to 1, meaning that an error was found by the DRAM scrubber (indicating potential memory problems)Bits 03 and 02 are reserved, and are ignoredBit 01 indicates there was an error associated with the CPU 01 coreBit 00 indicates there was an error associated with the CPU 00 coreSo, honestly knowing that it was a generic processor cache hit error reported by the northbridge, and it was a DRAM scrubber watchdog error, I'd say it's probably bad RAM or a bad memory controller on the motherboard (the read or write timed out, so it's one or the other). Link to comment Share on other sites More sharing options...
Cyntek Posted June 13, 2008 Author Share Posted June 13, 2008 (edited) Thank you, for the very " intensive" review of my memory dump. I really appreciate the effort you put into it, now that these random occurrences have been diagnosed properly, It seems that I would have to do a more intensive memory test to find what stick of memory is bad? Edited June 13, 2008 by cluberti shortening the post for those with slow connections Link to comment Share on other sites More sharing options...
Zxian Posted June 13, 2008 Share Posted June 13, 2008 Download Memtest 86+ and burn it to a CD. Remove all RAM sticks except for one. Let Memtest run a complete pass on the stick. Swap out that stick for another one. Repeat for each stick of RAM you use. Link to comment Share on other sites More sharing options...
Cyntek Posted June 13, 2008 Author Share Posted June 13, 2008 Download Memtest 86+ and burn it to a CD. Remove all RAM sticks except for one. Let Memtest run a complete pass on the stick. Swap out that stick for another one. Repeat for each stick of RAM you use. Alright, I already have memtest on cd so I will do a memtest on my sticks and see which are faulty, thanks. Link to comment Share on other sites More sharing options...
Guest elarifr Posted June 13, 2008 Share Posted June 13, 2008 Thanks for the reply, but I don't understand how it can be a hardware failure when the computer runs fine with another OS for example "ubuntu" I have no issues when running Linux. This issue is only on windows.Linux & Windows does not use hardware the same way. linux use mostly generic driver and does not use some specific hardware feature.However error 9c are HARDWARE failure as so well explained by cluberti. Since you have an AMD cpu, the DRAM controller is inside the cpu. so it can be Dram (Memory chips) or Dram Controller (inside CPU). So please give a look at your motherboard.here is a picture of some bad capacitor to see if what it should look like....good luck Link to comment Share on other sites More sharing options...
PC_LOAD_LETTER Posted June 13, 2008 Share Posted June 13, 2008 here is a picture of some bad capacitor to see if what it should look like....if the picture doesnt help just look at just about any Dell GX260 motherboard ever made. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now