Tom's Hardware > Forum > Games General > PC Gaming > BSOD, help please?

BSOD, help please?

Forum Games General : PC Gaming - BSOD, help please?

Tom's Hardware: Over 1.4 million members in 6 different countries available to answer all your high-tech questions. Sign up now! Its free!
Word :    Username :           
 

Okay, so heres the story. I play "Restaurant City" (facebook game), it uses Adobe flash player 10. Although the game may not be the cause, it seems to be at the moment. I crash due to 'pool corruptions' and 'win2k' issues. Hopefully someone can aid me in this problem, thanks in advance.

Logs:

Spoiler :


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


Loading Dump File [C:\WINDOWS\Minidump\Mini041909-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is: C:\574391db8798deca33e760726b779f21\i386
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Apr 19 18:15:02.796 2009 (GMT-7)
System Uptime: 0 days 0:37:58.500
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {6595a38, 1c, 1, 8054519a}

*** WARNING: Unable to verify timestamp for mssmbios.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1ea )

Followup: Pool_corruption
---------

0: 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: 06595a38, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8054519a, address which referenced memory

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


WRITE_ADDRESS: 06595a38

CURRENT_IRQL: 1c

FAULTING_IP:
nt!ExAllocatePoolWithTag+31a
8054519a ?? ???

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 00000000 to 805446f0

STACK_TEXT:
aaae6c94 00000000 00000000 00000023 00000023 nt!ExDeferredFreePool+0x1ea


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+1ea
805446f0 ?? ???

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ExDeferredFreePool+1ea

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID: 0xA_nt!ExDeferredFreePool+1ea

BUCKET_ID: 0xA_nt!ExDeferredFreePool+1ea

Followup: Pool_corruption
---------



Spoiler :

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


Loading Dump File [C:\WINDOWS\Minidump\Mini041909-06.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is: C:\574391db8798deca33e760726b779f21\i386
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Apr 19 20:24:26.437 2009 (GMT-7)
System Uptime: 0 days 0:37:10.125
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
...............................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8053a8d3, aabd19e8, 0}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** WARNING: Unable to verify timestamp for win32k.sys
Probably caused by : win32k.sys ( win32k!vSrcCopyS32D32Identity+33 )

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

1: 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: 8053a8d3, The address that the exception occurred at
Arg3: aabd19e8, 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:
nt!IoFreeMapRegisters+3
8053a8d3 ?? ???

TRAP_FRAME: aabd19e8 -- (.trap 0xffffffffaabd19e8)
Unable to read trap frame at aabd19e8

CUSTOMER_CRASH_COUNT: 6

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from aabd1c04 to 8053a8d3

STACK_TEXT:
aabd1a58 aabd1c04 029c2c00 aabd1a88 bf836e39 nt!IoFreeMapRegisters+0x3
WARNING: Frame IP not in any known module. Following frames may be wrong.
aabd1a64 bf836e39 02752c00 029c2c00 02000a00 0xaabd1c04
aabd1a88 bf836af2 0000009a aabd1cec e1167c48 win32k!vSrcCopyS32D32Identity+0x33
aabd1c9c bf80a321 e1167c58 00000000 00000000 win32k!EngCopyBits+0x48d
aabd1d30 8054162c e1167c48 e3d49ae0 e10cb788 win32k!NtGdiBitBlt+0x463
aabd1d30 7c90e514 e1167c48 e3d49ae0 e10cb788 nt!KiInterruptTemplate+0x82
00b7fac4 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!vSrcCopyS32D32Identity+33
bf836e39 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: win32k!vSrcCopyS32D32Identity+33

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49900fc9

FAILURE_BUCKET_ID: 0x8E_win32k!vSrcCopyS32D32Identity+33

BUCKET_ID: 0x8E_win32k!vSrcCopyS32D32Identity+33

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

Sponsored Links
Register or log in to remove.

This topic has been moved from the section Tom's Hardware Forum related to section Games General by Justinblue

Reply to justinblue
Tom's Hardware > Forum > Games General > PC Gaming > BSOD, help please?
Go to:

There are 516 identified and unidentified users. To see the list of identified users, Click here.

Please mind

You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.

Add a reply Cancel
Sponsored links
  • Ask the community now
  • Publish
Ad
They won a badge
Join us in greeting them