Hi, I am having problem such as Bule Screen with sound from cpu otherwise automatic restart.....i checked by memtest..it wont produce errror.. Recently i checked Event Viewer --> application...there are so many error automatically generated exactly after 1 mintute...all the errors are same.. check temperature exception hr =0x86999999 Sensor Type Winbond W83647HF (ISA 290h) Motherboard 56 °C (133 °F) CPU 86 °C (187 °F) Aux 49 °C (120 °F) CPU coolng fan 3497 RPM MY MINIDUMP info Microsoft (R) Windows Debugger Version 6.10.0003.233 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini121208-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: %systemroot%/minidump Executable search path is: 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 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0 Debug session time: Fri Dec 12 07:39:55.953 2008 (GMT+5) System Uptime: 0 days 11:16:16.637 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 Unable to load image afd.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for afd.sys *** ERROR: Module load completed but symbols could not be loaded for afd.sys ************************************************************ ******************* * * * Bugcheck Analysis * * * ************************************************************ ******************* Use !analyze -v to get detailed debugging information. BugCheck 1000000A, {e8, 2, 1, 80701a16} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** WARNING: Unable to verify timestamp for avgtdix.sys *** ERROR: Module load completed but symbols could not be loaded for avgtdix.sys *** WARNING: Unable to verify timestamp for tcpip.sys *** ERROR: Module load completed but symbols could not be loaded for tcpip.sys ************************************************************ ************* *** *** *** *** *** 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 *** *** *** ************************************************************ ************* ************************************************************ ************* *** *** *** *** *** 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 *** *** *** ************************************************************ ************* ************************************************************ ************* *** *** *** *** *** 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 *** *** *** ************************************************************ ************* ************************************************************ ************* *** *** *** *** *** 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 : avgtdix.sys ( avgtdix+1c84 ) Followup: MachineOwner Please help me

Did you confirm those temps in the BIOS? Both the motherboard temp & CPU temp are extremely high...your system's on the verge of a meltdown. Describe your case cooling configuration.

Thank for your reply.... i dont know how to find case cooling configuration....my fan speed is 3479 RPM Sensor Type Winbond W83647HF (ISA 290h) but my senor didnt alert me..what is going on

Have you cleaned it? Before posting try google. Backup. Use anti virus software.

Also, your other post is still on the site: http://www.computing.net/answers/wi... You may want to PM Justin Weber and ask him to remove it. "So won’t you give this man his wings What a shame To have to beg you to see We’re not all the same What a shame" - Shinedown

Your cpu temp as reported is more than high enough to permanently damage it and eventually fry it. You should stop using your computer at all (or at the very least for not any more than a short time after it has cooled down to room temp) until you have cured your overheating problem. The cpu heatsink/fan on your computer may be clogged with mung (dust, lint, etc.), or the cpu fan may have stopped spinning, which could account for the high cpu temp, but I think it's likely, if you have a desktop computer, that your power supply is failing. If you have a desktop (or tower) computer, if the fan fails on the power supply, the power supply will overheat in a short time, and because the fan isn't working, much of the heat generated by the PS is dumped inside the case rather than being removed, which would account for your high mboard and aux temps as well as, at least contributing to, your high cpu temp. If you have a desktop computer... Failing power supplies are common and can cause your symptoms. Check your PS. See response 4 in this: http://www.computing.net/hardware/w... ...... It appears you have a software problem as well. That may still be there after you have corrected whatever is causing your overheating problem.

See the sister post in WinXP forum. http://www.computing.net/answers/wi... Temps are extreme.