RE: Bluescreen bei verschiedenen Spielen

Stimmt, thx für den Hinweis. Aber mit dem Bericht kann ich nicht besonders
viel anfangen vieleicht aber ein von euch. Habe mal weil ich memory
corruption gelesen habe :D nen check gemacht. Keine Fehler der Rammodule.
auch ein wechesl dieser hat ja vorher keine Verbesserung erbracht.

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

Loading Dump File [C:\WINDOWS\Minidump\Mini061505-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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Wed Jun 15 00:26:23.984 2005 (GMT+2)
System Uptime: 0 days 0:05:47.570
Loading Kernel Symbols
.........................................................................................................
Loading unloaded module list
..............
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {9ce82240, 2, 0, 8051ec1c}

Probably caused by : memory_corruption ( nt!MiDeletePte+198 )

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

kd> .reload
Loading Kernel Symbols
.........................................................................................................
Loading unloaded module list
..............
Loading User Symbols
kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 9ce82240, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8051ec1c, address which referenced memory

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


OVERLAPPED_MODULE: rdbss

READ_ADDRESS: 9ce82240

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiDeletePte+198
8051ec1c 8b420c mov eax,[edx+0xc]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 8051f090 to 8051ec1c

STACK_TEXT:
ee683b84 8051f090 c0021f70 043ee000 00000000 nt!MiDeletePte+0x198
ee683c48 805164b7 e199a4f0 0443cfff 00000000 nt!MiDeleteVirtualAddresses+0x164
ee683cf4 805a6cb9 821b0020 82220438 ee683d64 nt!MiRemoveMappedView+0x237
ee683d38 805a6da8 82336658 8219e640 00000000 nt!MiUnmapViewOfSection+0x12b
ee683d54 8053c808 ffffffff 821b0020 0012fb4c nt!NtUnmapViewOfSection+0x54
ee683d54 7c91eb94 ffffffff 821b0020 0012fb4c nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fb30 00000000 00000000 00000000 00000000 0x7c91eb94


FOLLOWUP_IP:
nt!MiDeletePte+198
8051ec1c 8b420c mov eax,[edx+0xc]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MiDeletePte+198

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1d

STACK_COMMAND: kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiDeletePte+198

BUCKET_ID: 0xA_nt!MiDeletePte+198

Followup: MachineOwner

"xemox" schrieb:

> Hallo zusammen.
>
> Ich habe das faszinierende Problem das ich jedes Spiel zwar spielen kann,
> aber das beim Beenden dieses zw. auch bei einem Mapwechsel des Spieles mein
> Kompletter PC einfriert. Inzwischen habe ich raus das es ein Gerätetreiber
> problem ist aber ich finde nicht heraus welcher. Habe mit dem Windbg programm
> rausgefunden das es immer der Gleiche Fehler ist.
>
> Leider habe ich aber keine Ahnung was den Fehler hervorruft. Trieber habe
> ich eigentlich alle auf dem neuestem Stand.
>
> Die Fehlermeldung bzw. was mir der debugger auswirft:
>
> Microsoft (R) Windows Debugger Version 6.4.0007.2
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Loading Dump File [C:\WINDOWS\Minidump\Mini061505-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
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
> Debug session time: Wed Jun 15 00:26:23.984 2005 (GMT+2)
> System Uptime: 0 days 0:05:47.570
> *********************************************************************
> * 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 unloaded module list
> .............
> Loading User Symbols
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 1000000A, {9ce82240, 2, 0, 8051ec1c}
>
> ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
>
>
> Followup: MachineOwner
> ---------
>
>
.

Relevant Pages

  • problems with PC crashing; help/insight requested
    ... Mini Kernel Dump File: Only registers and stack trace are available ... Win32 error 2 ... Loading Kernel Symbols ... Will force reload symbols with known size. ...
    (microsoft.public.windowsxp.general)
  • Windows 2003 crashes after successful VPN connection
    ... I have a windows 2003 server, which is also a VPN server. ... Kernel Summary Dump File: Only kernel address space is available ... Loading Kernel Symbols ... If kernel debugger is available get stack backtrace. ...
    (microsoft.public.windows.server.general)
  • Slow Soft-RAID 5 performance
    ... The Kernel boot log is attached as boot.msg ... MEM window: disabled. ... registered new interface driver usbfs ... Loading ide-core ...
    (Linux-Kernel)
  • [PATCH] kexec based hibernation: a prototype of kexec multi-stage load
    ... This patch implements a prototype of kexec multi-stage load. ... loading the hibernated disk image with sys_kexec_load. ... necessary for parameter passing from original kernel to kexeced kernel ... struct page *pages; ...
    (Linux-Kernel)
  • Bluescreen bei verschiedenen Spielen
    ... * Symbols can not be loaded because symbol path is not initialized. ... Unable to load image ntoskrnl.exe, Win32 error 2 ... Loading Kernel Symbols ...
    (microsoft.public.de.german.windowsxp.sonstiges)