For the past four months, I have been getting random freezes and reboots and have yet to see a BSOD, something must be going on because my minidump folder is packed with files. I downloaded WinDbg and the symbols, around 200MB worth to try reading several of files but I still don't know what's wrong. I know it's with the "win32k.sys" and "ntoskrnl.exe." I've googled several things and haven't recieved much information except RAM is likely an issue.
Here's my latest dump.
So can I fix this?
Here's my latest dump.
Loading Dump File [C:\WINDOWS\Minidump\Mini042007-02.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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Fri Apr 20 21:22:13.968 2007 (GMT-4)
System Uptime: 0 days 1:10:40.579
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
.........
**********************************************************
* *
* Bugcheck Analysis *
* *
**********************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {90f2f064, 0, 80589082, 0}
Could not read faulting driver name
Probably caused by : ntoskrnl.exe ( nt!ObQueryNameString+4da )
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: 90f2f064, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 80589082, 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: 90f2f064
FAULTING_IP:
nt!ObQueryNameString+4da
80589082 8b30 mov esi,dword ptr [eax]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: iexplore.exe
LAST_CONTROL_TRANSFER: from 80588707 to 80589082
STACK_TEXT:
b37c7c48 80588707 b37c7c70 01000000 00000000 nt!ObQueryNameString+0x4da
b37c7c88 80588583 e45d9000 00080000 82097938 nt!ObInheritDeviceMap+0x39
b37c7d04 80582c17 82097938 e3abb388 00000000 nt!ObpIncrementHandleDataBase+0x6c
b37c7d50 804f827a 00000000 7c810665 00000001 nt!NtNotifyChangeMultipleKeys+0x33c
b37c7d8c 00000000 00000000 00000023 00000023 nt!RtlInsertElementGenericTableFullAvl+0xd0
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ObQueryNameString+4da
80589082 8b30 mov esi,dword ptr [eax]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 45e54711
SYMBOL_NAME: nt!ObQueryNameString+4da
FAILURE_BUCKET_ID: 0x50_nt!ObQueryNameString+4da
BUCKET_ID: 0x50_nt!ObQueryNameString+4da
Followup: MachineOwner
---------
kd> lm
start end module name
804d7000 806eb500 nt M (pdb symbols) C:\WINDOWS\Symbols\exe\ntoskrnl.pdb
*All items that ended with "deferred" were taken out cause the post was too long.
Unloaded modules:
b3d4b000 b3d76000 kmixer.sys
b49ab000 b49ac000 drmkaud.sys
b4ac3000 b4ad0000 DMusic.sys
f6a9f000 f6aad000 swmidi.sys
b3d76000 b3d99000 aec.sys
b99ef000 b99f1000 splitter.sys
f00c2000 f00cb000 processr.sys
f0983000 f0988000 Cdaudio.SYS
f8251000 f8254000 Sfloppy.SYS
So can I fix this?
