BSOD Help
Hello everyone, I am Seraph.
I am going to begin by showing you thatI have a Compaq Presario Cq60z
Windows 7 32-bit Ultimate
If needed, I will post more information.
I am hear because I get a BSOD when attempting to play a game compatible for Windows XP (It does work in Vista if run as and administrator and if you have sound playing to have sound enabled in game)
The name of the game is called Trickster Online hosted by NTreev.
Now upon starting up, the launcher will begin patching new files or nothing happen, just press start to begin the game.
The fun begins after. Trickster uses and antihack software called Gameguard. Gameguard starts as soon as Trickster starts. When playing the first time, Gameguard has to patch. Once patching I would receive the BSOD.
I have the debugged dump files right here below showing that it is messing up when Gamemon.des starts. I do play another game that uses the same exact Gameguard (different configuration for that game) with no error. Any suggestions?
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\091510-29983-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 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c1a000 PsLoadedModuleList = 0x82d62810
Debug session time: Wed Sep 15 00:07:27.185 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:35.494
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8a600882, 9c367a04, 0}
Probably caused by : memory_corruption ( nt!MiQueuePageAccessLog+9c )
Followup: MachineOwner
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: 8a600882, The address that the exception occurred at
Arg3: 9c367a04, Trap Frame
Arg4: 00000000
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
+12a
8a600882 8b11 mov edx,dword ptr [ecx]
TRAP_FRAME: 9c367a04 -- (.trap 0xffffffff9c367a04)
ErrCode = 00000000
eax=0000fe3d ebx=00000000 ecx=0000ff69 edx=00010001 esi=8a606890 edi=8a6070d0
eip=8a600882 esp=9c367a78 ebp=9c367a98 iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010216
8a600882 8b11 mov edx,dword ptr [ecx] ds:0023:0000ff69=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: GameMon.des
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8a60d4cc to 8a600882
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
9c367a98 8a60d4cc 00000001 852f9ab8 87de1ac0 0x8a600882
9c367b2c 82cb0411 82d4e74c 00000000 00000000 0x8a60d4cc
9c367bfc 82c564bc 87de1ac0 87417008 87417008 nt!MiQueuePageAccessLog+0x9c
9c367c14 82e57f6e 852f9ab8 87417008 87417078 nt!IofCallDriver+0x63
9c367c34 82e74d5f 87de1ac0 852f9ab8 00000000 nt!IopSynchronousServiceTail+0x1f8
9c367cd0 82e7753a 87de1ac0 87417008 00000000 nt!IopXxxControlFile+0x6aa
9c367d04 82c5d44a 000002f8 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
9c367d04 004192b3 000002f8 00000000 00000000 nt!KiFastCallEntry+0x12a
0012dd84 00000000 00000000 00000000 00000000 0x4192b3
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiQueuePageAccessLog+9c
82cb0411 c745fc01000000 mov dword ptr [ebp-4],1
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!MiQueuePageAccessLog+9c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x8E_nt!MiQueuePageAccessLog+9c
BUCKET_ID: 0x8E_nt!MiQueuePageAccessLog+9c
Followup: MachineOwner
I am going to begin by showing you thatI have a Compaq Presario Cq60z
Windows 7 32-bit Ultimate
If needed, I will post more information.
I am hear because I get a BSOD when attempting to play a game compatible for Windows XP (It does work in Vista if run as and administrator and if you have sound playing to have sound enabled in game)
The name of the game is called Trickster Online hosted by NTreev.
Now upon starting up, the launcher will begin patching new files or nothing happen, just press start to begin the game.
The fun begins after. Trickster uses and antihack software called Gameguard. Gameguard starts as soon as Trickster starts. When playing the first time, Gameguard has to patch. Once patching I would receive the BSOD.
I have the debugged dump files right here below showing that it is messing up when Gamemon.des starts. I do play another game that uses the same exact Gameguard (different configuration for that game) with no error. Any suggestions?
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\091510-29983-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 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c1a000 PsLoadedModuleList = 0x82d62810
Debug session time: Wed Sep 15 00:07:27.185 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:35.494
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8a600882, 9c367a04, 0}
Probably caused by : memory_corruption ( nt!MiQueuePageAccessLog+9c )
Followup: MachineOwner
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: 8a600882, The address that the exception occurred at
Arg3: 9c367a04, Trap Frame
Arg4: 00000000
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
+12a
8a600882 8b11 mov edx,dword ptr [ecx]
TRAP_FRAME: 9c367a04 -- (.trap 0xffffffff9c367a04)
ErrCode = 00000000
eax=0000fe3d ebx=00000000 ecx=0000ff69 edx=00010001 esi=8a606890 edi=8a6070d0
eip=8a600882 esp=9c367a78 ebp=9c367a98 iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010216
8a600882 8b11 mov edx,dword ptr [ecx] ds:0023:0000ff69=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: GameMon.des
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8a60d4cc to 8a600882
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
9c367a98 8a60d4cc 00000001 852f9ab8 87de1ac0 0x8a600882
9c367b2c 82cb0411 82d4e74c 00000000 00000000 0x8a60d4cc
9c367bfc 82c564bc 87de1ac0 87417008 87417008 nt!MiQueuePageAccessLog+0x9c
9c367c14 82e57f6e 852f9ab8 87417008 87417078 nt!IofCallDriver+0x63
9c367c34 82e74d5f 87de1ac0 852f9ab8 00000000 nt!IopSynchronousServiceTail+0x1f8
9c367cd0 82e7753a 87de1ac0 87417008 00000000 nt!IopXxxControlFile+0x6aa
9c367d04 82c5d44a 000002f8 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
9c367d04 004192b3 000002f8 00000000 00000000 nt!KiFastCallEntry+0x12a
0012dd84 00000000 00000000 00000000 00000000 0x4192b3
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiQueuePageAccessLog+9c
82cb0411 c745fc01000000 mov dword ptr [ebp-4],1
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!MiQueuePageAccessLog+9c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x8E_nt!MiQueuePageAccessLog+9c
BUCKET_ID: 0x8E_nt!MiQueuePageAccessLog+9c
Followup: MachineOwner
0