Crashing out of game BSOD follows

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

brentallen16 said:

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:

Code:

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

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

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

brentallen16 said:

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

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

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

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.

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.

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