Random Reboots and Freezes

[Baounit]

So I've been getting this message after a clean reformat. Now this computer will randomly reboot or shut down. I've never recieved the BSODs because the computer either reboots or freezes before the BSOD would show up.

Can anyone help? Here's my newest mini dump.

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini022707-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 Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Tue Feb 27 18:16:20.828 2007 (GMT-5)
System Uptime: 0 days 10:57:54.434
************************************************** *******************
* 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 User Symbols
Loading unloaded module list
..................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e47418a4, 0, 80594fbe, 1}

ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,213F80,42250FF9
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Probably caused by : ntoskrnl.exe ( nt+bdfbe )

Followup: MachineOwner
---------

kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e47418a4, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 80594fbe, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)

Debugging Details:
------------------

ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,213F80,42250FF9
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.


MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
e47418a4

FAULTING_IP:
nt+bdfbe
80594fbe 8b30 mov esi,dword ptr [eax]

MM_INTERNAL_CODE: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 80594643 to 80594fbe

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
ebd57c48 80594643 ebd57c70 00000000 00000000 nt+0xbdfbe
ebd57c88 805944bf e472f000 00080000 8202b328 nt+0xbd643
ebd57d04 805811af 8202b328 e3681148 00000000 nt+0xbd4bf
ebd57d50 804fa4da 00000000 7c810665 00000001 nt+0xaa1af
00000000 00000000 00000000 00000000 00000000 nt+0x234da


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+bdfbe
80594fbe 8b30 mov esi,dword ptr [eax]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

SYMBOL_NAME: nt+bdfbe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

[FordPrefect]

I cannot really interpret the Minidump output but afaik the " PAGE_FAULT_IN_NONPAGED_AREA" is especially caused by faulty hardware. I had this problem when my RAM was defective.
I would try no narrow down the problem by booting up with minimum hardware built in and then by and by add more hardware components.
Also, if you have not done so, don't use quickformat when installing Windows as defective sectors are not tagged.

Hm, just read your problem again. Do you mean that your computer also just shuts down or reboots without any BSOD? Did you install any new hardware components? Then I would guess your Power Supply doesn't deliver enough power.

Edit: Also update Windows and all your drivers.

Good Luck

[Jito463]

The fault is shown to lie with ntoskrnl.exe. However, as this is a critical Windows file, then I would assume hardware failure as well. As FordPrefect pointed out, it's likely RAM given the error message. Go to www.memtest.org and download the latest version of MemTest 86+ in ISO format (or the floppy version if you like). Write it to a disc and then boot from it and let it run a minimum of 5 passes unless it finds errors before then.

If it does find errors, and you're running more than one stick of RAM, you'll need to test them individually. If they work individually but not together, then it's likely that either the board or the CPU is bad. It takes time to hunt this stuff down (trust me, I do it for a living), but if you're patient you should be able to find the faulty part.