Driver conflicting with my game?

[Thisistunaktunak]

I've recently been playing the game Vindictus, and randomly started to blue screen after a few minutes or a few hours of playing. My friend said he had a similar problem when he tried playing ArmA. He told me to use Driver Verifier to see if it was a driver issue, and sure enough right when I launched the game with Verifier running I blue screened. I don't know what to do from here or if it is a completely different problem. But recently, after a system restore only a few hours before the blue screen, Vindictus only crashes instead of blue screens.

I was wondering, how do I pin point what driver it is? And how do I fix it?

 

[Thisistunaktunak]

There was only one memory dump, not sure why cause it crashed. I don't know why I said it was my problem, it's my friends. But anyway, he sent me his dump file. I opened it and it says,

Symbol search path is: SRV*c:\symbols*http/msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02819000 PsLoadedModuleList = 0xfffff800`02a5e650
Debug session time: Fri Jul 29 20:45:43.900 2011 (UTC - 4:00)
System Uptime: 0 days 20:32:40.617
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 3c889, 2, 3c861}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000003c889, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000003c861, 0

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


BUGCHECK_STR: 0x4E_99

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff8000291ed7c to fffff80002898d00

STACK_TEXT:
fffff880`0920c1c8 fffff800`0291ed7c : 00000000`0000004e 00000000`00000099 00000000`0003c889 00000000`00000002 : nt!KeBugCheckEx
fffff880`0920c1d0 fffff800`028409ed : 00000000`00000000 fffffa80`00a2d980 0000000f`ffffffff fffff800`028b2e0e : nt!MiBadShareCount+0x4c
fffff880`0920c210 fffff800`0288e6f1 : e8e00000`00000000 fffff680`00066b30 00000000`00000200 000fffff`00000001 : nt! ?? ::FNODOBFM::`string'+0x336c8
fffff880`0920c290 fffff800`02885ee2 : fffff880`0920cbc8 00000000`00000000 fffffa80`04b40270 fffffa80`04b40608 : nt!MiDecommitPages+0x1a1
fffff880`0920cb20 fffff800`02897f93 : ffffffff`ffffffff 00000000`007fe4c0 00000000`007fe4b8 00000000`00004000 : nt!NtFreeVirtualMemory+0x382
fffff880`0920cc20 00000000`772e14fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`007fe488 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772e14fa


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiBadShareCount+4c
fffff800`0291ed7c cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiBadShareCount+4c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c

Followup: MachineOwner

 

[Hawkeye22]

Use blue screen view to narrow down which driver is causing problems.

http/www.nirsoft.net/utils/blue_screen_view.html