Repeated crashes-at my wit's end-desperate for help!

Disable and disconnect your wireless stuff.

Thanks CCT-I uninstalled the WUSB monitor and loaded the Linksys driver only after uninstalling the adapter. It still crashes! Any help appreciated. Here's the latest dump file:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini050407-09.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri May 4 15:46:35.437 2007 (GMT-5)
System Uptime: 0 days 5:06:04.028
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.........................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {d04ffffc, 0, 805bf39d, 0}


Could not read faulting driver name
Probably caused by : ntoskrnl.exe ( nt!HalpGetFullGeometry+44 )

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

0: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* 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: d04ffffc, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 805bf39d, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: d04ffffc

FAULTING_IP:
nt!HalpGetFullGeometry+44
805bf39d 8b8cb5a8fdffff mov ecx,dword ptr [ebp+esi*4-258h]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 9

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: GoldfishMD.scr

LAST_CONTROL_TRANSFER: from 565308ec to 805bf39d

STACK_TEXT:
80538d00 565308ec 8bfc5557 458b0c5d 0440f708 nt!HalpGetFullGeometry+0x44
WARNING: Frame IP not in any known module. Following frames may be wrong.
80538d10 00000000 00ab850f 45890000 10458bf8 0x565308ec


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!HalpGetFullGeometry+44
805bf39d 8b8cb5a8fdffff mov ecx,dword ptr [ebp+esi*4-258h]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9d

SYMBOL_NAME: nt!HalpGetFullGeometry+44

FAILURE_BUCKET_ID: 0x50_nt!HalpGetFullGeometry+44

BUCKET_ID: 0x50_nt!HalpGetFullGeometry+44

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

Another dump file-as you can see the BSODs are random! It is agravating!

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


Loading Dump File [C:\WINDOWS\Minidump\Mini050407-08.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri May 4 10:39:50.031 2007 (GMT-5)
System Uptime: 0 days 1:49:31.742
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...........................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 0, b9804c64, b9804960}

Unable to load image IntelC52.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for IntelC52.sys
*** ERROR: Module load completed but symbols could not be loaded for IntelC52.sys
Probably caused by : IntelC52.sys ( IntelC52+7b818 )

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

1: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: b9804c64, Exception Record Address
Arg4: b9804960, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
+0
00000000 ?? ???

EXCEPTION_RECORD: b9804c64 -- (.exr ffffffffb9804c64)
ExceptionAddress: 00000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000008
Parameter[1]: 00000000
Attempt to execute non-executable address 00000000

CONTEXT: b9804960 -- (.cxr ffffffffb9804960)
eax=00000001 ebx=00000000 ecx=b8f26b60 edx=00000000 esi=804fa034 edi=804fa0ec
eip=00000000 esp=b9804d2c ebp=b9804dac iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210246
00000000 ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 8

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

WRITE_ADDRESS: 00000000

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 00000000 to 00000000

SYMBOL_ON_RAW_STACK: 1

STACK_ADDR_RAW_STACK_SYMBOL: 17002000010004

STACK_COMMAND: dds B9804D40-0x20 ; kb

STACK_TEXT:
b9804d20 00000000
b9804d24 00000008
b9804d28 00210246
b9804d2c 00000000
b9804d30 00000000
b9804d34 8912d6d8
b9804d38 00000000
b9804d3c b8f1a818 IntelC52+0x7b818
b9804d40 b8f1a818 IntelC52+0x7b818
b9804d44 8912d6d8
b9804d48 b8f1a810 IntelC52+0x7b810
b9804d4c b9804d54
b9804d50 00010000
b9804d54 b8f1a808 IntelC52+0x7b808
b9804d58 b8f1a808 IntelC52+0x7b808
b9804d5c 8912d6d8
b9804d60 b8f1a800 IntelC52+0x7b800
b9804d64 b9804d6c
b9804d68 00010001
b9804d6c b8f1a7f8 IntelC52+0x7b7f8
b9804d70 b8f1a7f8 IntelC52+0x7b7f8
b9804d74 8912d6d8
b9804d78 b8f1a7f0 IntelC52+0x7b7f0
b9804d7c b9804d84
b9804d80 00010002
b9804d84 b8f03428 IntelC52+0x64428
b9804d88 b8f03428 IntelC52+0x64428
b9804d8c 8912d6d8
b9804d90 b8f03420 IntelC52+0x64420
b9804d94 b9804d3c
b9804d98 00010003
b9804d9c b8f1a810 IntelC52+0x7b810


FOLLOWUP_IP:
IntelC52+7b818
b8f1a818 ?? ???

SYMBOL_NAME: IntelC52+7b818

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: IntelC52

IMAGE_NAME: IntelC52.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4406209b

FAILURE_BUCKET_ID: 0x7E_IntelC52+7b818

BUCKET_ID: 0x7E_IntelC52+7b818

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

Only thing I can say is pull the Sound Blaster and anything else you absolutely don't need and reinstall.

Just get the OS and chipset and Video going if you can.

(In)voluntary euthanasia!

I appreciate your input CCT-I have analyzed the minidumps under Vista as well and no guesses allowed! same problems persist under Vista-almost the same processes with random crashes-which to me points to a hardware issue-but which one? I am going to do a heart transplant-I have ordered a replacement mobo from Centrix international (Dell OEM for 9100-it was not too costly-$49-so it should be the exact same replacement)-I will use this opportunity to learn to strip my computer and put it together and if it breaks the machine-so be it-at least it will be (in)voluntary euthanasia! I will report on my success (or lack of it) soon-as you can see-I will put an end to this BSOD problem one way or another!!:giddy:

It was the Prescott heating up (I think)-problem looks solved!

Hello guys:
I think the problem I had of random BSODs looks like it has been solved. The new thermal paste helped-and that got me thinking-after I did some research, I realized that my Prescott 3 Ghz HT processor may be the one heating up and crashing the machine-because the same problems happened under Vista as well. Even though I had bought a new mobo, instead of swapping the old one out, I bought an OEM Pentium D 940 (Presler-Dual core 3.2 Ghz) from Tiger Direct for $109 and installed it with the paste yesterday and would you believe it?-No crashes -system running heavy loads for over 6 hours now -no BSODs at all! Vista and XP running great-with the old mobo itself! Hope this helps someone-I will keep the post alive-I still want to see how the machine does after a week...:hotbounce

Update-after more than 10 hours with multitasking-not even one crash-the fans are running a lot cooler as well (just by tactile sensation on the case side)-I would stay away from the Prescotts unless you can leave the case open I think-the Presler Penium D is great and the Dell A03 BIOS recognized it w/out any problem and XP and Vista did not ask for reactivation also! Thanks to all who volunteered thier help for me...

Final Post-success at last! 5 days after change in processors and not a single crash!!! Final verdict-guilty of heat related injury-Prescott 630 HT processor-condemned to sit in solitary confinement!!
Cheers! over and out!

June 9, 2007-Fellows! The machine is running fantastic-yup-not a single crash since the processor change. I'm lovin' it!!!