Crashing out of game BSOD follows

[brentallen16]

Please Help:I have been playing the game vindictus and i am having a hard time recently. The game will crash on me and i will get BSOD soon after, i updated all my drivers, reinstalled the game, ran startup repair on my Windows OS and nothing seems to help. My memtest says that all my memory is good and my PSU is 1000w so i dont think that that could be the issue so im lost. Im not too savvy with the troubleshooting of software issues but the dmp files and perfmon are attached. The following are my Computer specifications:

Windows 7 Home premium 64bit
ASUS P7P55D PRO Motherboard
8GB DDR3 RAM
Intel Core i7 860 @ 2.8GHz
NVidia GeForce GTX 275 (x2)
1000w PSU
System Manufacturer System manufacturer Model System Product Name Total amount of system memory 8.00 GB RAM System type 64-bit operating system Number of processor cores 4 Storage Total size of hard disk(s) 1397 GB Disk partition (C 1287 GB Free (1397 GB Total) Media drive (D CD/DVD Graphics Display adapter type NVIDIA GeForce GTX 275 Total available graphics memory 4095 MB Dedicated graphics memory 896 MB Dedicated system memory 0 MB Shared system memory 3199 MB Display adapter driver version 8.17.12.6099 Primary monitor resolution 1920x1080 DirectX version DirectX 10 Network Network Adapter Realtek PCIe GBE Family Controller Network Adapter Killer Xeno NDIS EDGE Interface

 

[zigzag3143]

Please Help:I have been playing the game vindictus and i am having a hard time recently. The game will crash on me and i will get BSOD soon after, i updated all my drivers, reinstalled the game, ran startup repair on my Windows OS and nothing seems to help. My memtest says that all my memory is good and my PSU is 1000w so i dont think that that could be the issue so im lost. Im not too savvy with the troubleshooting of software issues but the dmp files and perfmon are attached. The following are my Computer specifications:

Windows 7 Home premium 64bit
ASUS P7P55D PRO Motherboard
8GB DDR3 RAM
Intel Core i7 860 @ 2.8GHz
NVidia GeForce GTX 275 (x2)
1000w PSU
System Manufacturer System manufacturer Model System Product Name Total amount of system memory 8.00 GB RAM System type 64-bit operating system Number of processor cores 4 Storage Total size of hard disk(s) 1397 GB Disk partition (C 1287 GB Free (1397 GB Total) Media drive (D CD/DVD Graphics Display adapter type NVIDIA GeForce GTX 275 Total available graphics memory 4095 MB Dedicated graphics memory 896 MB Dedicated system memory 0 MB Shared system memory 3199 MB Display adapter driver version 8.17.12.6099 Primary monitor resolution 1920x1080 DirectX version DirectX 10 Network Network Adapter Realtek PCIe GBE Family Controller Network Adapter Killer Xeno NDIS EDGE Interface

I believe it to be an invictus driver. Here is the results .DONT DO THE RECOMMENDED REGISTRY CHANGE UNLESS YOU ARE VERY PROFICIENT.

PROCESS_HAS_LOCKED_PAGES (76)
Caused by a driver not cleaning up correctly after an I/O.
Arguments:
Arg1: 0000000000000000, Locked memory pages found in process being terminated.
Arg2: fffffa8008e29060, Process address.
Arg3: 0000000000000019, Humber of locked pages.
Arg4: 0000000000000000, Pointer to driver stacks (if enabled) or 0 if not.
Issue a !search over all of physical memory for the current process pointer.
This will yield at least one MDL which points to it. Then do another !search
for each MDL found, this will yield the IRP(s) that point to it, revealing
which driver is leaking the pages.
Otherwise, set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management\TrackLockedPages to a DWORD 1 value and reboot. Then the system
will save stack traces so the guilty driver can be easily identified.
When you enable this flag, if the driver commits the error again you will
see a different bugcheck - DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (0xCB) -
which can identify the offending driver(s).


Instead I would recommend running driver verifier.

Beyond that, please run Verifier with these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users


Let us know if you need assistance.



Ken J

 

[brentallen16]

awesome i will try the driver verifier since im not too proficient in Computers i will post back with what I can find. Such a relief to be headed in a direction finally, no one has been able to help me at all lol

 

[brentallen16]

Ok well i followed the directions u gave me and now my PC wont boot. it started system startup repair on its own and it seems to be stuck there....

 

[zigzag3143]

Ok well i followed the directions u gave me and now my PC wont boot. it started system startup repair on its own and it seems to be stuck there....

A warning about verifier. Make sure you have a backup and restore point. A win7 dvd. Just in case.


Ken J

 

[brentallen16]

i do have both, my PC just said it couldnt fix the error and shut down. what steps should i take from here?

 

[brentallen16]

Ok sigh of relief kinda lol i booted my PC back up and it started right up with no issues.

 

[brentallen16]

Well i got verifier to run without crashing at startup but when i did what i know crashes my pc it just BSOD and loop booted till i used system recovery. It never told me anything about a corrupt driver... Would be willing to try additional options seeing as how the game that I enjoy playing is about unplayable now with all the crashing and rebooting.

 

[DeanP]

If there is no BSOD crashes after you set the Driver Verifier on, you may have to wait 36 hours (in my experience of Driver Verifier).

If you do get BSOD crashes after you set the Drivier Verifier on, upload the latest dumps (zip them up in a .zip file) and zigzag3143 (Ken) will analyze it for you.

If you can't get into normal mode, boot into Safe Mode. Press f8 before Windows starts booting. Then turn off Driver Verifier.

 

[brentallen16]

Here is the most recent data after all the verifier issues yesterday

 

[brentallen16]

Still have not been able to fix this, someone please help. Attached is the latest information on the BSOD the only thing i have done recently is flash the BIOS to most recent but it was no help.

 

[DeanP]

GEARAspiWDM.sys??? - iTunes

Yes, this is installed by iTunes in system\sysWow64\Drivers\GEARAspiWDM.sys . (Running Server 2003 x64 R2) This driver will cause errors due to its incompatibality with x64 architecture (e.g., XP x64 Edition, Server 2003 x64). Specifically, if you're running ATI Catalyst Control Center (cli.exe) it will cause the ATI program set to fail. Simply uninstalling iTunes is the only way to resolve the issue. After iTunes is removed, all problems will be solved. FYI, if you try to just remove gearaspiwdm.sys only, this will likely cause your CD/DVD drives to fail as the redbook driver will not work

 

[brentallen16]

Well I uninstalled Itunes and all the apple crap I had and it still crashed me

 

[brentallen16]

Any other Ideas? or can zigzag please let me know how to do the registry fixes he referred to earlier?

 

[zigzag3143]

Any other Ideas? or can zigzag please let me know how to do the registry fixes he referred to earlier?

Sorry you are still having trouble. NON OF THE DMPS i HAVE LOOKED AT ARE DRIVER VERIFIED ENABLED. Are you sure it was running?

The latest like all the rest are a bugcheck 76 which means
PROCESS_HAS_LOCKED_PAGES (76)
Caused by a driver not cleaning up correctly after an I/O.

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


PROCESS_NAME: Vindictus.exe

DEFAULT_BUCKET_ID: DRIVER_FAULT_0x76

Regarding the "registry changes" those were if you could not get you computer booted again., since you obviously can they are not valid.


There is one thing you might want to try. Sometimes antivirus apps can cause havoc. Your AVG may be doing that. I removing it and replacing it with Microsoft security essentials.

AVG - Download tools

http://www.microsoft.com/security_essentials/


Its either that or the game.



Ken J

 

[brentallen16]

Earlier today I did just that. I uninstalled AVG and Dl MS Security essentials. I also did a full uninstallation of the game and reinstalled but I didnt have any improvements with either of those. But if it is the game maybe I will just have to stop playing it although i know people that run it just fine on windows 7. I will try to run Driver verifier again and upload any additional information that I can find. Thanks again Ken.

 

[DeanP]

This is how to do Driver Verifier:
http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[brentallen16]

OK, I was able to run Verifier. It wouldnt let me past the windows startup screen without BSOD but I managed to get back into my OS on safe mode instead of Recovery to turn it off. I noticed that it did generate a new dmp file so i ran the BSOD app again and here is the new information. Thank you guys for the help again I can only imagine how busy you are trying to help everyone... you guys deserve medals or somethin lol

 

[DeanP]

you guys deserve medals or somethin lol

Thanks for those words. It is possible to get medals in forums. Although, it is very difficult and can take months or even years to get one medal. I think there is 3 medals altogether.

I have no idea what's causing it to BSOD. May be related to hardware issue, but a BSOD expert will check additional info for you.

If I was you, I'd check for hardware issues right now.

To test for memory issues. Use Memtest86 to see if any of the memory are causing BSOD:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Do it overnight - can take several hours.
Run at least 7 passes
Test each RAM individually
Do this on a cold boot (after your computer has been off for a while).

To test for CPU issues. Use Prime95 to see if the CPU are causing BSOD:
http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

 

[reventon]

Hi,

Please avoid posting the same problem on different forums. BSOD experts are few in number and we do not like wasting our time suggesting the same things that have already been suggested by our colleagues elsewhere.

The other thread: Vindictus Crashes and BSOD follows Plz Help - Tech Support Forum

It's your choice which thread to follow from this point on, please do not continue posting in both at once.

As for your BSODs - from the type of bugcheck alone I would expect this one to be a software problem, however hardware faults are always a possiblity.

You have dealt with the AVG possiblity, and with iTunes too. What is left? Well...

[FONT=lucida console]
[B]Rt64win7.sys[/B] [COLOR=Red]Wed Jun 23 21:10:45 2010 [/COLOR](4C21CF95) - Realtek networking

[B]Xeno7x64.sys[/B] Mon Nov 02 06:43:32 2009 (4AEDC8C4) - EVGA Xeno networking [url=http://www.evga.com/articles/00467/]EVGA | Articles | EVGA Killer Xeno Pro[/url]
[B]Edge7x64.sys[/B] Mon Nov 02 06:43:31 2009 (4AEDC8C3) - EVGA Xeno networking [url=http://www.evga.com/articles/00467/]EVGA | Articles | EVGA Killer Xeno Pro[/url]
[/FONT]

Two sets of networking drivers/adapters, the first of which has a driver dated prior to Windows 7 RTM.

I see that the active networking device is currently the Xeno. I suggest removing the Xeno and uninstalling the drivers for now.

At the same time update the Realtek driver - Realtek (choose one of the Go links to the right of the Win7 and WinServer 2008 R2 Auto Installation Program (SID:1432824) entry).

Then use your computer normally for a few days and see if you have more problems. If not then start using the Xeno again, but this time make sure to disable the Realtek driver after you have installed the Xeno.

Regards,
Reventon

BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Dec 21 19:16:48.476 2010 (GMT+13)
System Uptime: 0 days 0:00:16.506
Probably caused by : CI.dll ( CI!SHATransform+eb0 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00003010`00520050 00000000`00000002 00000000`00000000 fffff800`02cee2b3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Dec 20 20:01:07.582 2010 (GMT+13)
System Uptime: 0 days 0:20:29.613
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+18126 )
PROCESS_NAME:  Vindictus.exe
DEFAULT_BUCKET_ID:  DRIVER_FAULT_0x76
BUGCHECK_STR:  0x76
Bugcheck code 00000076
Arguments 00000000`00000000 fffffa80`0ac625e0 00000000`00000013 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Dec 20 17:37:19.407 2010 (GMT+13)
System Uptime: 0 days 0:24:53.438
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+18126 )
PROCESS_NAME:  Vindictus.exe
DEFAULT_BUCKET_ID:  DRIVER_FAULT_0x76
BUGCHECK_STR:  0x76
Bugcheck code 00000076
Arguments 00000000`00000000 fffffa80`08d83b30 00000000`00000010 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Dec 19 20:41:16.567 2010 (GMT+13)
System Uptime: 0 days 22:22:13.613
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+18126 )
PROCESS_NAME:  Vindictus.exe
DEFAULT_BUCKET_ID:  DRIVER_FAULT_0x76
BUGCHECK_STR:  0x76
Bugcheck code 00000076
Arguments 00000000`00000000 fffffa80`0bbceb30 00000000`0000000f 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec 18 20:38:57.638 2010 (GMT+13)
System Uptime: 0 days 0:49:34.684
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+18126 )
PROCESS_NAME:  Vindictus.exe
DEFAULT_BUCKET_ID:  DRIVER_FAULT_0x76
BUGCHECK_STR:  0x76
Bugcheck code 00000076
Arguments 00000000`00000000 fffffa80`07267800 00000000`00000006 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec 18 19:43:51.306 2010 (GMT+13)
System Uptime: 0 days 0:00:15.352
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiAddDevice+fc2 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xBE
PROCESS_NAME:  System
Bugcheck code 000000BE
Arguments fffff800`02ca5c84 00000000`02ca5121 fffff880`03361ca0 00000000`0000000a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec 18 05:17:17.425 2010 (GMT+13)
System Uptime: 0 days 0:53:19.471
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+18126 )
PROCESS_NAME:  Vindictus.exe
DEFAULT_BUCKET_ID:  DRIVER_FAULT_0x76
BUGCHECK_STR:  0x76
Bugcheck code 00000076
Arguments 00000000`00000000 fffffa80`078a1060 00000000`00000012 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec 18 04:18:49.739 2010 (GMT+13)
System Uptime: 0 days 0:23:17.785
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+18126 )
PROCESS_NAME:  Vindictus.exe
DEFAULT_BUCKET_ID:  DRIVER_FAULT_0x76
BUGCHECK_STR:  0x76
Bugcheck code 00000076
Arguments 00000000`00000000 fffffa80`0b44cb30 00000000`00000015 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec 18 00:29:58.997 2010 (GMT+13)
System Uptime: 0 days 0:16:59.043
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+18126 )
PROCESS_NAME:  Vindictus.exe
DEFAULT_BUCKET_ID:  DRIVER_FAULT_0x76
BUGCHECK_STR:  0x76
Bugcheck code 00000076
Arguments 00000000`00000000 fffffa80`07387b30 00000000`00000006 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 17 23:18:57.646 2010 (GMT+13)
System Uptime: 0 days 0:23:10.692
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+18126 )
PROCESS_NAME:  Vindictus.exe
DEFAULT_BUCKET_ID:  DRIVER_FAULT_0x76
BUGCHECK_STR:  0x76
Bugcheck code 00000076
Arguments 00000000`00000000 fffffa80`06ea4060 00000000`00000015 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 17 22:54:51.242 2010 (GMT+13)
System Uptime: 0 days 0:40:30.288
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+18126 )
PROCESS_NAME:  Vindictus.exe
DEFAULT_BUCKET_ID:  DRIVER_FAULT_0x76
BUGCHECK_STR:  0x76
Bugcheck code 00000076
Arguments 00000000`00000000 fffffa80`06f16b30 00000000`0000000c 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 17 22:13:22.262 2010 (GMT+13)
System Uptime: 0 days 0:10:54.308
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+18126 )
PROCESS_NAME:  Vindictus.exe
DEFAULT_BUCKET_ID:  DRIVER_FAULT_0x76
BUGCHECK_STR:  0x76
Bugcheck code 00000076
Arguments 00000000`00000000 fffffa80`0b43d520 00000000`00000006 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 17 21:45:30.749 2010 (GMT+13)
System Uptime: 0 days 0:35:56.795
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+18126 )
PROCESS_NAME:  Vindictus.exe
DEFAULT_BUCKET_ID:  DRIVER_FAULT_0x76
BUGCHECK_STR:  0x76
Bugcheck code 00000076
Arguments 00000000`00000000 fffffa80`075a1b30 00000000`0000000c 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/font]