Steam, COD Black Ops blue screen crash, freezing

I can play MOH in single player with no problems and I can play in multiplayer with no problem, however when I exit the game from the multiplayer mode my computer will blue screen crash. Now I have Black Ops and my computer will freeze, stutter, and lock up to the point I have to hard crash my computer and when I put the latetest video driver the in-game screen will not fill up my wide screen monitor no matter what I do and I still get the freezes, stutters, and have to either hard crash or if I get lucky enough to exit out of it then it will blue screen crash. I was able to play single player ok this morning but when I tried multi-player I again had to hard crash my computer due to it locking up. I have a new alienware with two gts-240 video cards and no viruses of any sort on my computer.

devgroup2 said:

I can play MOH in single player with no problems and I can play in multiplayer with no problem, however when I exit the game from the multiplayer mode my computer will blue screen crash. Now I have Black Ops and my computer will freeze, stutter, and lock up to the point I have to hard crash my computer and when I put the latetest video driver the in-game screen will not fill up my wide screen monitor no matter what I do and I still get the freezes, stutters, and have to either hard crash or if I get lucky enough to exit out of it then it will blue screen crash. I was able to play single player ok this morning but when I tried multi-player I again had to hard crash my computer due to it locking up. I have a new alienware with two gts-240 video cards and no viruses of any sort on my computer.

These were caused by a bad driver (XenoVa64.sys?). Only way to be sure is to run 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


ken J

ok devgroup is my buddy i pointe him to this site searching for fixes to his problems.

so i have a question what if we disabled that xeno nic card and he used a different one???

CD82 said:

ok devgroup is my buddy i pointe him to this site searching for fixes to his problems.

so i have a question what if we disabled that xeno nic card and he used a different one???

As I said it is a driver and which we wont know till driver verifier is run.

OK Zig i had him disable that card and use his other nic card. and he is not having anymore issues at all no more crashes or blue screens

Well, I looked at that suggested driver issue and disabled my killer xeno pro card and using my regular eathernet and have not had any issues with crashing, freezing, etc. Man thanks so much for helping me out.