jediagh

Thank you for the info! I did some more googling & found this: http://www.motherboardpoint.com/asus-a8n-sli-deluxe-chip-fan-fail-speed-too-low-t191237.html In which indeed the mobo fan has gone bad. On that other post they advise on getting an after-market fan/heatsink combo that is better for my mobo. I just ordered the part so it looks like I will doing some "operating" next week when the part gets here. =) $40 was the cost for the fan/heatsink. Hopefully that will give me another 2 to 3 years before I finally get a new rig. =)

Here is a bot of more info: I went into my BIOS to enable all the warnings possible on the hardware. It gave me the option of CPU and CHIP fans. So when I reboot I am now getting this error at the BIOS. WARNING: CHIP FAN SPEED 0 RPM Press F1 to continue or DEL to enter SETUP to disable warning. I do believe that CHIP FAN is the small fan on the MB as I don't see any other fans apart from the AC 64 Silencer on the CPU but that one is CPU FAN per the BIOS. I did a good cleaning right now of the mobo and checked each capacitor and they are all fine. Blew out any dust it had (very little) as I blow dust once a month from the machine. I did disconnect the mobo small fan and reconnected it. The fan is still not running right now. So is that the issue? My small mobo fan? What is that fan for? What is overheating that is causing the lockups? How come it only does it once in a while as oppose to all the time? Is the fact that the case can "handle" the heat for a while and then an't the issue? Is it possible to replace that fan? Or is it a mobo replacement only? This rig was bought in 2005 and I'm not ready (can't afford) a new one. =(

Hello all, I'm hoping someone here more knowledgeable than me can help me out. I think I'm getting the same type of error as the one in this post: The reason for that is that when I google for this: Error code 0000009c, parameter1 00000004, parameter2 8054e5f0, parameter3 b2000000, parameter4 00070f0f. Which I am getting from my event properties description the above topic comes up. I read the sticky on how to do a memory dump and when the blue screen occurred today I was able to get this dump. Note that I don't think the DUMP is working right since it says there are errors with it not finding some symbols. Not sure??? --- Microsoft ® Windows Debugger Version 6.12.0002.633 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\MEMORY.DMP] Kernel Complete Dump File: Full address space is available ************************************************************ WARNING: Dump file has been truncated. Data may be missing. ************************************************************ 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+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe - Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 2600.xpsp_sp3_gdr.101209-1647 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 Debug session time: Sat Feb 12 05:15:34.609 2011 (UTC - 6:00) System Uptime: 0 days 0:15:11.186 WARNING: Process directory table base 0074F000 doesn't match CR3 0AD30020 WARNING: Process directory table base 0074F000 doesn't match CR3 0AD30020 ********************************************************************* * 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+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe - Loading Kernel Symbols ............................................................... ................................................................ ............ Loading User Symbols Loading unloaded module list .......... *** ERROR: Symbol file could not be found. Defaulted to export symbols for halmacpi.dll - ERROR: FindPlugIns 8007007b ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9C, {4, 8054e5f0, b2000000, 70f0f} *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys ***** 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 *** *** *** ************************************************************************* Probably caused by : ntkrpamp.exe Followup: MachineOwner --------- ---- END OF DUMP My systems info: CPU: AMD Atholn 64 3800+ MB: Asus A8N SLI Video: 256MB NVIDA GeForce 7800GT RAM: 2GB Total via 4 x 512 MB Mushkin Memory HD1: (OS on this one) 250GB WD HD2: 250GB WD HD3: 200GB WD As I re-read the other post with the memory dump issue and look at my MB I just noticed that my small fan on the MB next to where the SLI chip is at is **NOT** spinning. I don't know if it did spin before for not as I have never noticed it. From what I can see (I have opened the case will do it again in a bit after I finsih this post) all the capacitors on the board are ok and dust free. BTW this is what the event viewer has: Event Type: Error Event Source: System Error Event Category: (102) Event ID: 1003 Date: 2/12/2011 Time: 10:10:52 AM User: N/A Computer: T1300 Description: Error code 0000009c, parameter1 00000004, parameter2 8054e5f0, parameter3 b2000000, parameter4 00070f0f. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 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 Could any one please help me? Thanks!