Right,
I’ve been having a few issues with BSOD lately. I have a brand new Hard disk with 3 partitions which are as follows:
1. Win XP Pro x32 - Set up for any software I need that’s not x64 compatible
2. Win XP Pro x64 - Set up as standard OS for all other needs
3. Win XP Pro x64 - Set up for audio with no networking & OS is seriously tweaked
Most common errors are on the x64 OS giving me:
STOP 0x00000050
STOP 0x0000000A
Partition 3 seams to be fine so I'm thinking its not hardware related although I have recently bought a new Motherboard, processor, CD-WR, PSU & another 8G of RAM.
At first I just had the stop errors on the x64 OS & then I started to see stop errors on the x32 OS also. I reinstalled Windows on the X32 partition which bombed out half way through the install. I re-installed it again which seamed to work but since I’ve installed it I’ve started getting STOP 0x00000050
I grabbed a dump file & converted it to this with WinDBG. Can I have your thoughts on this:
====================================================================
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\Administrator\Desktop\Mini021609-01.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 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Feb 16 19:52:36.843 2009 (GMT+0)
System Uptime: 0 days 0:01:03.437
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** 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 50, {fff7ffff, 0, 0, 0}
Could not read faulting driver name
Probably caused by : ntoskrnl.exe ( nt!PspReaper+39 )
Followup: MachineOwner
---------
3: 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: fff7ffff, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 00000000, 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: fff7ffff
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: explorer.exe
LAST_CONTROL_TRANSFER: from 00000000 to 804f9c4b
STACK_TEXT:
b48e89c0 00000000 00000000 00000000 00000000 nt!PspReaper+0x39
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!PspReaper+39
804f9c4b 5d pop ebp
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!PspReaper+39
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4249fa54
FAILURE_BUCKET_ID: 0x50_nt!PspReaper+39
BUCKET_ID: 0x50_nt!PspReaper+39
Followup: MachineOwner
---------
I’ve been having a few issues with BSOD lately. I have a brand new Hard disk with 3 partitions which are as follows:
1. Win XP Pro x32 - Set up for any software I need that’s not x64 compatible
2. Win XP Pro x64 - Set up as standard OS for all other needs
3. Win XP Pro x64 - Set up for audio with no networking & OS is seriously tweaked
Most common errors are on the x64 OS giving me:
STOP 0x00000050
STOP 0x0000000A
Partition 3 seams to be fine so I'm thinking its not hardware related although I have recently bought a new Motherboard, processor, CD-WR, PSU & another 8G of RAM.
At first I just had the stop errors on the x64 OS & then I started to see stop errors on the x32 OS also. I reinstalled Windows on the X32 partition which bombed out half way through the install. I re-installed it again which seamed to work but since I’ve installed it I’ve started getting STOP 0x00000050
I grabbed a dump file & converted it to this with WinDBG. Can I have your thoughts on this:
====================================================================
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\Administrator\Desktop\Mini021609-01.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 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Feb 16 19:52:36.843 2009 (GMT+0)
System Uptime: 0 days 0:01:03.437
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** 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 50, {fff7ffff, 0, 0, 0}
Could not read faulting driver name
Probably caused by : ntoskrnl.exe ( nt!PspReaper+39 )
Followup: MachineOwner
---------
3: 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: fff7ffff, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 00000000, 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: fff7ffff
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: explorer.exe
LAST_CONTROL_TRANSFER: from 00000000 to 804f9c4b
STACK_TEXT:
b48e89c0 00000000 00000000 00000000 00000000 nt!PspReaper+0x39
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!PspReaper+39
804f9c4b 5d pop ebp
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!PspReaper+39
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4249fa54
FAILURE_BUCKET_ID: 0x50_nt!PspReaper+39
BUCKET_ID: 0x50_nt!PspReaper+39
Followup: MachineOwner
---------