Supportnet / Forum / WindowsXP
PAGE_FAULT_IN_NONPAGED_AREA (laut Google oft in 0xbad0b154, wieso?)
Frage
Hallo,
ich habe mir heute das akoya mini von ALDI gekauft und während des Surfens einen Bluescreen erhalten.
Es handelt sich um einen STOP 0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA).
Seltsam finde ich jedoch, dass ich, als ich nach der Googlesuche nach der ersten Speicheradresse "bad0b154" jede Menge 0x00000050-STOP-Errors gefunden habe, die dem Muster
STOP 0x00000050 (0xbad0b154, 0x00000000, 0x805*****, 0x0000000*)
folgen.
Könnte mir hier jemand sagen, ob dies eventuell am Firefox 3, *Z* *Z*, BullGuard, Realtek etc. liegen könnte?
Bitte um Antwort.
Zur Analyse habe ich hier die Debuggerinfos angehängt. (Wegen der Größe in mehreren Posts.
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini072308-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Jul 23 23:17:27.734 2008 (GMT+2)
System Uptime: 0 days 4:38:37.452
Loading Kernel Symbols
...............................................................................................................
Loading User Symbols
Loading unloaded module list
..............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {bad0b154, 0, 805c4a47, 2}
Could not read faulting driver name
Probably caused by : ntkrpamp.exe ( nt!ObQueryNameString+9b )
Followup: MachineOwner
---------
0: 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: bad0b154, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 805c4a47, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: bad0b154
FAULTING_IP:
nt!ObQueryNameString+9b
805c4a47 8b88a4000000 mov ecx,dword ptr [eax+0A4h]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 8058205e to 805c4a47
STACK_TEXT:
f7a52cbc 8058205e 846ed030 f7a52d0c 00000062 nt!ObQueryNameString+0x9b
f7a52d7c 8053876d 00000000 00000000 863c28b8 nt!IopErrorLogThread+0x172
f7a52dac 805cff64 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
f7a52ddc 805460de 8053867e 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ObQueryNameString+9b
805c4a47 8b88a4000000 mov ecx,dword ptr [eax+0A4h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObQueryNameString+9b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a
FAILURE_BUCKET_ID: 0x50_BADMEMREF_nt!ObQueryNameString+9b
BUCKET_ID: 0x50_BADMEMREF_nt!ObQueryNameString+9b
Followup: MachineOwner
---------
Antwort 1 von steenvoortl
0: 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: bad0b154, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 805c4a47, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: bad0b154
FAULTING_IP:
nt!ObQueryNameString+9b
805c4a47 8b88a4000000 mov ecx,dword ptr [eax+0A4h]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 8058205e to 805c4a47
STACK_TEXT:
f7a52cbc 8058205e 846ed030 f7a52d0c 00000062 nt!ObQueryNameString+0x9b
f7a52d7c 8053876d 00000000 00000000 863c28b8 nt!IopErrorLogThread+0x172
f7a52dac 805cff64 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
f7a52ddc 805460de 8053867e 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ObQueryNameString+9b
805c4a47 8b88a4000000 mov ecx,dword ptr [eax+0A4h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObQueryNameString+9b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a
FAILURE_BUCKET_ID: 0x50_BADMEMREF_nt!ObQueryNameString+9b
BUCKET_ID: 0x50_BADMEMREF_nt!ObQueryNameString+9b
Followup: MachineOwner
---------
0: 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: bad0b154, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 805c4a47, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: bad0b154
FAULTING_IP:
nt!ObQueryNameString+9b
805c4a47 8b88a4000000 mov ecx,dword ptr [eax+0A4h]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 8058205e to 805c4a47
STACK_TEXT:
f7a52cbc 8058205e 846ed030 f7a52d0c 00000062 nt!ObQueryNameString+0x9b
f7a52d7c 8053876d 00000000 00000000 863c28b8 nt!IopErrorLogThread+0x172
f7a52dac 805cff64 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
f7a52ddc 805460de 8053867e 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ObQueryNameString+9b
805c4a47 8b88a4000000 mov ecx,dword ptr [eax+0A4h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObQueryNameString+9b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a
FAILURE_BUCKET_ID: 0x50_BADMEMREF_nt!ObQueryNameString+9b
BUCKET_ID: 0x50_BADMEMREF_nt!ObQueryNameString+9b
Followup: MachineOwner
---------
0: 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: bad0b154, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 805c4a47, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: bad0b154
FAULTING_IP:
nt!ObQueryNameString+9b
805c4a47 8b88a4000000 mov ecx,dword ptr [eax+0A4h]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 8058205e to 805c4a47
STACK_TEXT:
f7a52cbc 8058205e 846ed030 f7a52d0c 00000062 nt!ObQueryNameString+0x9b
f7a52d7c 8053876d 00000000 00000000 863c28b8 nt!IopErrorLogThread+0x172
f7a52dac 805cff64 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
f7a52ddc 805460de 8053867e 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ObQueryNameString+9b
805c4a47 8b88a4000000 mov ecx,dword ptr [eax+0A4h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObQueryNameString+9b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a
FAILURE_BUCKET_ID: 0x50_BADMEMREF_nt!ObQueryNameString+9b
BUCKET_ID: 0x50_BADMEMREF_nt!ObQueryNameString+9b
Followup: MachineOwner
---------
0: kd> lmvm nt
start end module name
804d7000 806e5000 nt # (pdb symbols) c:\symbols\ntkrpamp.pdb\7D6290E03E32455BB0E035E38816124F1\ntkrpamp.pdb
Loaded symbol image file: ntkrpamp.exe
Mapped memory image file: c:\symbols\ntkrpamp.exe\4802516A20e000\ntkrpamp.exe
Image path: ntkrpamp.exe
Image name: ntkrpamp.exe
Timestamp: Sun Apr 13 20:31:06 2008 (4802516A)
CheckSum: 001F8636
ImageSize: 0020E000
File version: 5.1.2600.5512
Product version: 5.1.2600.5512
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0816.04b0
CompanyName: Microsoft Corporation
ProductName: Sistema operativo Microsoft® Windows®
InternalName: ntkrpamp.exe
OriginalFilename: ntkrpamp.exe
ProductVersion: 5.1.2600.5512
FileVersion: 5.1.2600.5512 (xpsp.080413-2111)
FileDescription: Sistema & kernel NT Kernel
LegalCopyright: © Microsoft Corporation. Todos os direitos reservados.
*******************************************************************************
* *
* 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: bad0b154, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 805c4a47, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: bad0b154
FAULTING_IP:
nt!ObQueryNameString+9b
805c4a47 8b88a4000000 mov ecx,dword ptr [eax+0A4h]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 8058205e to 805c4a47
STACK_TEXT:
f7a52cbc 8058205e 846ed030 f7a52d0c 00000062 nt!ObQueryNameString+0x9b
f7a52d7c 8053876d 00000000 00000000 863c28b8 nt!IopErrorLogThread+0x172
f7a52dac 805cff64 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
f7a52ddc 805460de 8053867e 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ObQueryNameString+9b
805c4a47 8b88a4000000 mov ecx,dword ptr [eax+0A4h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObQueryNameString+9b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a
FAILURE_BUCKET_ID: 0x50_BADMEMREF_nt!ObQueryNameString+9b
BUCKET_ID: 0x50_BADMEMREF_nt!ObQueryNameString+9b
Followup: MachineOwner
---------
0: 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: bad0b154, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 805c4a47, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: bad0b154
FAULTING_IP:
nt!ObQueryNameString+9b
805c4a47 8b88a4000000 mov ecx,dword ptr [eax+0A4h]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 8058205e to 805c4a47
STACK_TEXT:
f7a52cbc 8058205e 846ed030 f7a52d0c 00000062 nt!ObQueryNameString+0x9b
f7a52d7c 8053876d 00000000 00000000 863c28b8 nt!IopErrorLogThread+0x172
f7a52dac 805cff64 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
f7a52ddc 805460de 8053867e 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ObQueryNameString+9b
805c4a47 8b88a4000000 mov ecx,dword ptr [eax+0A4h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObQueryNameString+9b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a
FAILURE_BUCKET_ID: 0x50_BADMEMREF_nt!ObQueryNameString+9b
BUCKET_ID: 0x50_BADMEMREF_nt!ObQueryNameString+9b
Followup: MachineOwner
---------
0: 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: bad0b154, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 805c4a47, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: bad0b154
FAULTING_IP:
nt!ObQueryNameString+9b
805c4a47 8b88a4000000 mov ecx,dword ptr [eax+0A4h]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 8058205e to 805c4a47
STACK_TEXT:
f7a52cbc 8058205e 846ed030 f7a52d0c 00000062 nt!ObQueryNameString+0x9b
f7a52d7c 8053876d 00000000 00000000 863c28b8 nt!IopErrorLogThread+0x172
f7a52dac 805cff64 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
f7a52ddc 805460de 8053867e 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ObQueryNameString+9b
805c4a47 8b88a4000000 mov ecx,dword ptr [eax+0A4h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObQueryNameString+9b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a
FAILURE_BUCKET_ID: 0x50_BADMEMREF_nt!ObQueryNameString+9b
BUCKET_ID: 0x50_BADMEMREF_nt!ObQueryNameString+9b
Followup: MachineOwner
---------
0: kd> lmvm nt
start end module name
804d7000 806e5000 nt # (pdb symbols) c:\symbols\ntkrpamp.pdb\7D6290E03E32455BB0E035E38816124F1\ntkrpamp.pdb
Loaded symbol image file: ntkrpamp.exe
Mapped memory image file: c:\symbols\ntkrpamp.exe\4802516A20e000\ntkrpamp.exe
Image path: ntkrpamp.exe
Image name: ntkrpamp.exe
Timestamp: Sun Apr 13 20:31:06 2008 (4802516A)
CheckSum: 001F8636
ImageSize: 0020E000
File version: 5.1.2600.5512
Product version: 5.1.2600.5512
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0816.04b0
CompanyName: Microsoft Corporation
ProductName: Sistema operativo Microsoft® Windows®
InternalName: ntkrpamp.exe
OriginalFilename: ntkrpamp.exe
ProductVersion: 5.1.2600.5512
FileVersion: 5.1.2600.5512 (xpsp.080413-2111)
FileDescription: Sistema & kernel NT Kernel
LegalCopyright: © Microsoft Corporation. Todos os direitos reservados.
Antwort 2 von steenvoortl
Ergänzung:
Könnte dies auch an XP SP3 liegen?
Warum wurde in meinem ersten Thread *Z* *Z* zu *Z* *Z* zensiert?
Könnte dies auch an XP SP3 liegen?
Warum wurde in meinem ersten Thread *Z* *Z* zu *Z* *Z* zensiert?
Antwort 3 von steenvoortl
Mit *Z* *Z* meine ich
A*l*c*o*h*o*l* *1*2*0*%!
Wieso wird dies hier zensiert?
A*l*c*o*h*o*l* *1*2*0*%!
Wieso wird dies hier zensiert?