Cyntek

Alright, I already have memtest on cd so I will do a memtest on my sticks and see which are faulty, thanks.

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?

Thanks 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 X86 Copyright © 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 available Symbol search path is: C:Documents and SettingsCyntekMy DocumentsSymbols Executable search path is: Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 Debug session time: Thu Jun 12 01:54:09.625 2008 (GMT-7) System Uptime: 0 days 6:59:30.312 Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe Loading Kernel Symbols .................................................................................................... ................................. Loading User Symbols Loading 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 error Arguments: Arg1: 00000004 Arg2: 8054e5f0 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: Idle LAST_CONTROL_TRANSFER: from 806e9bfb to 804f9f33 STACK_TEXT: 8054e5c8 806e9bfb 0000009c 00000004 8054e5f0 nt!_woutput+0x404 8054e6f4 806e4c52 80042000 00000000 00000000 hal!_allshr+0xb 00000000 00000000 00000000 00000000 00000000 hal!HalpWriteCmosTime+0xce STACK_COMMAND: kb FOLLOWUP_IP: nt!_woutput+404 804f9f33 5d pop ebp SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!_woutput+404 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntoskrnl.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a FAILURE_BUCKET_ID: 0x9C_AuthenticAMD_nt!_woutput+404 BUCKET_ID: 0x9C_AuthenticAMD_nt!_woutput+404 Followup: MachineOwner ---------

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. Event Date: 6/12/2008 Source: System Error Time: 11:34:05 AM Catagory: (102) Type: Error Event ID: 1003 User: N/A Computer: AMDX24600 Description: Error code 0000009c, parameter1 00000004, parameter2 8054e5f0, parameter3 b2000000, parameter4 00070f0f. Data: Bytes: 0000: 53 79 73 74 65 6d 20 45 System E 0008: 72 72 6f 72 20 20 45 72 rror Er 0010: 72 6f 72 20 63 6f 64 65 ror code 0018: 20 30 30 30 30 30 30 39 0000009 0020: 63 20 20 50 61 72 61 6d c Param 0028: 65 74 65 72 73 20 30 30 eters 00 0030: 30 30 30 30 30 34 2c 20 000004, 0038: 38 30 35 34 65 35 66 30 8054e5f0 0040: 2c 20 62 32 30 30 30 30 , b20000 0048: 30 30 2c 20 30 30 30 37 00, 0007 0050: 30 66 30 66 0f0f Data: Words: 0000: 74737953 45206d65 726f7272 72452020 0010: 20726f72 65646f63 30303020 39303030 0020: 50202063 6d617261 72657465 30302073 0030: 30303030 202c3430 34353038 30663565 0040: 3262202c 30303030 202c3030 37303030 0050: 66306630 Woudl this be the cause of the random freezes and reboots ?

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.

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:0A AMD X2 4600 + Stock clock EVGA 7950 GT KO 512MB Stock clock Pci-e 1 Gb Generic Ram Dual Channel 1 Gb Kingston Hyper X Ram Lite On DVD +Rw 160 Gb Maxtor Sata HD 500 Gb Hitachi DeskStar Sata Hd 320 Gb Western Digital Pata Eide hd Audigy 2 value sound card Here's the memory dump log: Microsoft ® Windows Debugger Version 6.8.0004.0 X86 Copyright © 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 available Symbol 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.exe Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 Debug 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.exe Loading Kernel Symbols .................................................................................................... ................................. Loading User Symbols Loading 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> .reload Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe Loading Kernel Symbols .................................................................................................... ................................. Loading User Symbols Loading 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 error Arguments: Arg1: 00000004 Arg2: 8054e5f0 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: Idle LAST_CONTROL_TRANSFER: from 806e9bfb to 804f9f33 STACK_TEXT: 8054e5c8 806e9bfb 0000009c 00000004 8054e5f0 nt!_woutput+0x404 8054e6f4 806e4c52 80042000 00000000 00000000 hal!_allshr+0xb 00000000 00000000 00000000 00000000 00000000 hal!HalpWriteCmosTime+0xce STACK_COMMAND: kb FOLLOWUP_IP: nt!_woutput+404 804f9f33 5d pop ebp SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!_woutput+404 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntoskrnl.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a FAILURE_BUCKET_ID: 0x9C_AuthenticAMD_nt!_woutput+404 BUCKET_ID: 0x9C_AuthenticAMD_nt!_woutput+404 Followup: MachineOwner ---------

okay, well I slipped streamed only the nvidia 6.86 software and nothing else. I did not install the sp3 rc2 refresh. Now, the install was successfully installed and windows xp was updated via windows update. Then I started streaming online TV and after few minutes into the show, windows started to freeze and then reboots without any warning. What is causing this issue???. MY video card is update with with latest drivers as well. what is it????

hey everyone, just here to see if there is an issue with Nvidia Software 6.86 and Sp3 RC2 (Refreshed)?. The reason I am asking is to do several Freezes and Crashes with out any warning. Now, this has been happening to me and I would like to know if any one is having this issue. I have an ecs kn1 sli lite with the latest bios rev. 1.1E. And all my hard drives has been tested with spinrite6 and they are all healthy as a human being. Here is what Everest has to say: Everest Report

I just received another Freez and crash. man this beginning to be a pain. Where can i find the log to show what's causing it ?

It is not easy to understand the sense of your post and the consequences for users, who will get such an error message in the next future.As far as I understand you wanted to recommend the following: If you have updated a running Windows XP with SP3 and get an endless reboot at the end with an error message like Stop: c0000139 { Entry Point Not Found} The procedure entry point GdiGetBitmapBitssize could not be located in the dynamic link library Gdi32.dll, it is not useful to replace the broken file by any file of the same name. You have to take the file, which has been updated by SP3. You can find it within the WINDOWS\SERVICEPACKFILES\i386 directory of your OS partition. Is that correct? Who knows if that would have been the solution to fixing my problem, I have already did the clean install with sp3, nvraid intergrated into new cd. However, I really appreciate the help Fernando.

Thanks for the link and for the quick reply.

No problem thanks for the help, eveyone.

LOL

Hey, everyone. Well, I am here to find out what is happening to cause these crashes every so often?. I just did a clean installation with nLite and I slipstreamed pretty much all of the hotfixes and the latest nvraid (6.86) successfully. But, everyone so often the computer crashes whenever I view online resources or when ever i do something heavily tasked. The symptoms are: Freeze and crash and reboots. I have install sp3 successfully as well and as of right now I only have a few applications installed. Such as Antivirus "Eset NOD32, Office 2007, Quicktime, Realplayer, Winrar, Firefox, MoveOnBot" and that's it for now. It just crashes when ever it wants to crash and it's getting to be a really annoyance for it to happend, when ever I start on a project. All my hard drives are healthy and checked for consistency. "Thinking it migh have something to do with Nvraid" Here are the specs: ECS KN1 Sli lite Rev 1.0A AMD X2 4600 Evga 7950GT KO 512MB Audigy 2 Sound Card 1GB Kingston HyperX Dual channel 1GB Generic Ram Dual channel LiteON DVD-RW 160GB Maxtor SATA-I 500GB Hitachi Deskstar Sata-I 320GB Western Digital Caviar IDE 300GB Seagate ATA- IDE

Well, I have pretty much had to do clean install on my rig. Due to the fact that when I first installed SP3 after I have slipped stream my nvraid (6.86) software into windows xp/sp2, which by the way is now a successful install including all the hot fixes. However, there seems to be a downside to it, where uxthemepatch.dll is not supported on sp3. Well, I guess i can live without for a few months until there's an update for uxthempatch.dll. Or, is there another way of installing Themes in windows xp with sp3 already installed?