Crashing out of game BSOD follows

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.

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

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

brentallen16 said:

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

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. :)

This is how to do Driver Verifier:
Using Driver Verifier to identify issues with Drivers

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

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:
RAM - Test with Memtest86+

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:
https://www.sevenforums.com/tutorials...t-prime95.html

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...

Code:

Rt64win7.sys Wed Jun 23 21:10:45 2010 (4C21CF95) - Realtek networking

Xeno7x64.sys Mon Nov 02 06:43:32 2009 (4AEDC8C4) - EVGA Xeno networking EVGA | Articles | EVGA Killer Xeno Pro
Edge7x64.sys Mon Nov 02 06:43:31 2009 (4AEDC8C3) - EVGA Xeno networking EVGA | Articles | EVGA Killer Xeno Pro

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

Code:

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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``