Hi, I wasn't sure whether to post this as a hardware problem or Windows XP. My suspicions are hardware but I'm not 100% certain.
--------------------------------------------------------------------------
PC Specs:
AMD Athlon XP 2200+
768Mb RAM
40Gb Maxtor 7200rpm
Jetway V266B Motherboard
ATI Radeon 64Mb 7500
--------------------------------------------------------------------------
Windows XP
Sophos Anti Virus (up to date)
Zone Alarm (up to date)
Microsoft Beta Spyware, AdAware & Spybot (all up to date)
--------------------------------------------------------------------------
My computer is approximately 2 years old, and as of the weekend, it has developed the habit of shutting itself down or freezing. This normally occurs within a couple of minutes after booting up. It doesn't seem to matter what programs I run if any at all. When the pc boots back up, there are no errors in event viewer nor any minidump logs. Therefore, I don't really know where to start on diagnosing the fault.
I originally had Windows XP Home, and have since performed a clean install of Windows XP Pro as I thought this would solve my problem. Unfortunately it hasn't. I have also ran chkdsk and it reported no errors on the disk.
I have re-seated all of my cards & memory, checked all power connectors & IDE cables & the problem is still occuring.
Any help would be appreciated.
Last edited by Preki's Left Foot; 03-08-2005 at 05:33 PM.
OOOokkkaaaayyy....Those are normal to great temps. I was looking for an overheating problem you obviously dont have. They way the system is acting is if it isnt heat then you have a loose component. That can be the Graphics card to the processor to the power connector. You said it even froze in Bios, that is definitely hardware. Open the case and make sure all components are seated tightly (if you havent already)
I have double and triple checked all of the components and cannot find any loose connections.
After a couple of restarts & lock ups yesterday, I was able to work on my computer for well over 4 hours, without any probs.
Same thing today, it's been on for about an hour now. One lock up, 2 restarts and then my first BSOD Whether it's a one off, or related to my other probs I don't know.
Here are the results from WinDbg:
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini080405-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 2
*** 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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Thu Aug 4 18:29:21.219 2005 (GMT+1)
System Uptime: 0 days 0:04:16.779
************************************************** *******************
* 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 2
*** 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 unloaded module list
...
Loading User Symbols
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Unable to load image USBPORT.SYS, Win32 error 2
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
Probably caused by : hardware ( USBPORT+94ac )
As previously mentioned that error is indicating a hardware failure most likely due to a connection problem or perhaps a driver.
It does point out a USB driver issue. Plus: Probably caused by : hardware ( USBPORT+94ac )
To translate your .dmp log further follow these steps:
Go to start | search (type in) .dmp
Note the location of your latest .dmp file.
Then:
1) Download and install the Debugging Tools from Microsoft
2) Download and install this debugwiz
3) Open the Wiz & Browse to, or paste in the path to, your latest .dmp file.
4) After the Wiz creates a Text document attach it back to this thread.
I've got a feeling that the BSOD was just a one off caused by the original problem. Same thing is now happening every night. Couple of reboots and freezes, then no problems until the next day.
Newbie
Whether it's a one off, or related to my other probs I don't know.
