Solved BSOD when playing COD MW3 single player

M

Macdude

Member
When I play the Single player of MW3 my system crashes within a few minutes.

When I installed MW3 it crashed at first. I found out it had something to do with NERO (I thought) so I uninstalled it. At this moment i'm at 33.3% of MW3 and I can't get any further because within a few minutes I get a BSOD.

To my knowledge it isn't COD that is crashing but something else. I installed "Whocrashed " and that tells me that it mostly is the "usbport.sys" and the "ntoskrnl.exe"

http://home.scarlet.be/macdude2/crash.JPG
http://home.scarlet.be/macdude2/crashes.JPG

My system is from 2007 and I installed the latest Nvidia driver.

Specs:
C2D E6600
4GB DDR2
Twin2X PC5400
ASUS 8800GTS 640MB
Vista home premium 64 bit

The multiplayer works without problems. Also no BSOD's when I'm doing other things on the PC

EDIT: I made a rar file if that is ok. Get it here http://home.scarlet.be/macdude2/Windows_NT6_BSOD_jcgriff2.rar
 

My Computer

System One

Hi,

You crash file only shows 3Gig of RAM memory & this could be the issue.

Please remove the 1 Gig chip & see if that makes the system stable.
 

My Computer

System One

  • Manufacturer/Model
    HP-Pavilion m9280.uk-a
    CPU
    2.30 gigahertz AMD Phenom 9600 Quad-Core
    Motherboard
    ASUSTek Computer INC. NARRA3 3.02
    Memory
    3582 Megabytes Usable Installed Memory (4 Gig)
    Graphics Card(s)
    ASUS NVIDIA Geforce GTS450
    Sound Card
    Realtek High Definition 7.1 Audio (HP drivers)
    Monitor(s) Displays
    HP w2408 24.0" (Dual monitor)
    Screen Resolution
    1920 * 1200, 1920 * 1200
    Hard Drives
    3*500 Gigabytes Usable Hard Drive Capacity
    Plus 2x USB (160Gig each) external HDD
    BluRay & DVD Weiters
    HL-DT-ST BD-RE GGW-H20L SCSI CdRom (Bluray RW) Device
    AlViDrv BDDVDROM SCSI CdRom (Blueray) Device
    TSSTcorp CDDVDW TS-H653N SCSI CdRom
    Internet Speed
    40 Meg
Unfortunately no succes.

I removed one and then a second and still it crashed. After that I took out the remaining 2. I put the 2 that were already out and placed them in the other slots. Still bsod's.

My multiplayer also bsod on me.

I don't think it is a hardware problem. I really think it is software.
The latest WhoCrashed analysis:
On Fri 25/11/2011 20:14:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112511-02.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1168EC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFA60023188EC, 0xFFFFFA60005D5D08, 0xFFFFFA60005D56E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 285.62
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 285.62
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 285.62 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



@Lottimansion: thx for the help
 

My Computer

System One

Macdude said:
Unfortunately no succes.

I removed one and then a second and still it crashed. After that I took out the remaining 2. I put the 2 that were already out and placed them in the other slots. Still bsod's.

My multiplayer also bsod on me.

I don't think it is a hardware problem. I really think it is software.
The latest WhoCrashed analysis:
On Fri 25/11/2011 20:14:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112511-02.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1168EC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFA60023188EC, 0xFFFFFA60005D5D08, 0xFFFFFA60005D56E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 285.62
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 285.62
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 285.62 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



@Lottimansion: thx for the help
Click to expand...

Unfortunately who crashed is not always accurate. Though the video driver was involved the precursor was the USBPORT.SYS.

An un-named driver tried to access an invalid memory address.

You can run these two tests to verify your RAM (all 3 gigs) and find which driver is truly causing the crashes

Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.
Click to expand...
RAM - Test with Memtest86+ - Windows 7 Forums



2-Driver verifier

I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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

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.
Click to expand...

Driver Verifier - Enable and Disable - Windows 7 Forums
 

My Computer

System One

  • Manufacturer/Model
    Dell Inspiron E 1405
    CPU
    [email protected]
    Memory
    4 gigs
    Graphics Card(s)
    integrated intel 945
    Sound Card
    integrated
    Screen Resolution
    1440x900
    Hard Drives
    300 gig internal
    Internet Speed
    10 down 1.5 up
I let memtest run for more then 10hrs. 0 errors

On the second test my pc crashed 4 times. Each time the bsod told me it was the "USBPORT.SYS"
 

My Computer

System One

Small update here. I think I've found the problem.
When I game I use a Belkin Nostromo N52 gamepad. And it seems this is the reason for the game to crash.

I disconnected it and played a bit with the regular keyboard and no crash.

I just reinstalled the n52 software and will try it again tomorrow. If it starts to crash again I will use my keyboard.

Anyway I will definately post the outcome here.

Thx for all the help and let's hope that this is the end of my problem.
 

My Computer

System One

No more crashes with the regular keyboard.

The problem was with the Belkin Nostromo n52. I played it with the regular keyboard instead. To bad because I really like my n52.

I also have a Z board but that immediately stops working when I start it up. I'm talking to Steelseries about that.

It's a dam shame for the crappy drivers on that hardware.

I'm gonna mark this as solved. Thx for all the help.
 

My Computer

System One

You must log in or register to reply here.
Back
Top