* *
 
Welcome, Guest. Please login or register.
Did you miss your activation email?
March 28, 2024, 03:06:02 PM

Login with username, password and session length

Support Us


BFV Server Fund

Donate with PayPal!
March Goal: $41.00
Due Date: Mar 31
Total Receipts: $0.00
 0%

Pages: [1]   Go Down
  Print  
Author Topic: COD:MW3 Causing Blue Screen of Death  (Read 6947 times)
0 Members and 1 Guest are viewing this topic.
rip|CoyotezEye
Clan Council
User


Respect: 23
Offline Offline

Posts: 1,226


coyotezeyescoyotezeye
Awards
« on: February 07, 2012, 09:19:38 AM »

Hey so I need some tech advice.
When I play COD:MW3 & only when I play this I get a Blue Screen of Death.
I dont have the problem with any other game. Just this one.

Its happened when it goes to load a map. Its also happened in the middle of a game. And even when I am customizing a kit. It usually doesnt happen right away. Can take 30mins to a couple of hrs. But it seems to happen eventually every day.

I have done some google searches and came back empty. But I did find a video of what I have happen to me.
http://www.youtube.com/watch?v=KSfTz96rdJA

His seems to crash in single player when loading the level. but still looks like the same error I get.

It only pops up for a few seconds so I dont get to read the whole thing. But I do believe I see the same error:
Driver_TRQL_Not_Less_or_equal.


My specs:
Windows 7 Home Premium 64 Bit
ASRock P67 PRO3 (B3) LGA 1155 Intel P67 SATA 6Gb/s USB 3.0 ATX Intel Motherboard
Intel Core i5-2500
Refurbished: Seagate Barracuda ES ST3400620NS 400GB 7200 RPM SATA 3.0Gb/s 3.5" Hard Drive
Bigfoot Killer 2100 Gaming Network Card
SAPPHIRE 100314-3L Radeon HD 6870 1GB 256-bit GDDR5


Any ideas? I believe I have the latest drivers for everything.
Logged

rip|Council BO2 Veteran 6+ Years' Service BlackOps Veteran BC2 Veteran rip|member LAN Partier CoD6: MW2 Service Ribbon CoD5 Service Ribbon CoD4 Service Ribbon MVP in a Match Scrimmed BFV Service Ribbon


rip|buzinator
Administrator
User


Respect: 46
Offline Offline

Posts: 3,556


ripclanbuz
WWW Awards
« Reply #1 on: February 07, 2012, 09:39:08 AM »

There's a setting to let you keep the BSoD up on screen so you can read it fully and note the hex stop code or identify a specific driver dll.

Control Panel, System, Advanced System Settings (left pane), Advanced tab, Startup and Recovery / Settings, System failure / uncheck 'Automatically restart'.
« Last Edit: February 07, 2012, 09:44:13 AM by rip|buzinator » Logged

rip|Council 11+ Years Service LAN Partier Recruiting Legend Racing Licence BF2142 Service Ribbon Scrimmed Prodigious Poster BFV Service Ribbon Scrim Arranger BF2 Service Ribbon BF1942 Service Ribbon Légion du Pantalon Nu D'âne



rip|CoyotezEye
Clan Council
User


Respect: 23
Offline Offline

Posts: 1,226


coyotezeyescoyotezeye
Awards
« Reply #2 on: February 07, 2012, 09:47:55 AM »

Gotcha so doing that will give me time to read the whole message and see if it lists a specific error.

Logged

rip|Council BO2 Veteran 6+ Years' Service BlackOps Veteran BC2 Veteran rip|member LAN Partier CoD6: MW2 Service Ribbon CoD5 Service Ribbon CoD4 Service Ribbon MVP in a Match Scrimmed BFV Service Ribbon


rip|buzinator
Administrator
User


Respect: 46
Offline Offline

Posts: 3,556


ripclanbuz
WWW Awards
« Reply #3 on: February 07, 2012, 12:09:48 PM »

Right, gives you at least a chance to identify which driver and/device might be having the prob, or google the stop error.

There's a chance it may just be hardware too, like bad ram, or something. it does happen occasionally.
Logged

rip|Council 11+ Years Service LAN Partier Recruiting Legend Racing Licence BF2142 Service Ribbon Scrimmed Prodigious Poster BFV Service Ribbon Scrim Arranger BF2 Service Ribbon BF1942 Service Ribbon Légion du Pantalon Nu D'âne



rip|CoyotezEye
Clan Council
User


Respect: 23
Offline Offline

Posts: 1,226


coyotezeyescoyotezeye
Awards
« Reply #4 on: February 07, 2012, 12:30:06 PM »

Everything is brand new except the HD which is Refurb but everything is less than a month old.
And like I said it only happens on COD:MW3.

Hopefully its just a driver. I will check it tonight or tomorrow to see what kind of error it comes up with.
Logged

rip|Council BO2 Veteran 6+ Years' Service BlackOps Veteran BC2 Veteran rip|member LAN Partier CoD6: MW2 Service Ribbon CoD5 Service Ribbon CoD4 Service Ribbon MVP in a Match Scrimmed BFV Service Ribbon


rip|forkev
Clan Members
User


Respect: 10
Offline Offline

Posts: 879


overheadservice
Awards
« Reply #5 on: February 07, 2012, 02:43:27 PM »

It is because you a playing the wrong game.  Ripper hacked your HD to give you blue screen if you play anything other than BF3. 
Logged

6+ Years' Service BlackOps Veteran BC2 Veteran CoD6: MW2 Service Ribbon QW:ET Service Ribbon CoD5 Service Ribbon Racing Licence CoD4 Service Ribbon Scrimmed Prodigious Poster BF2 Service Ribbon rip|member


Where do you want me to stick ya?  Cuz you're done!!



rip|MightyMax
Clan Council
User


Respect: 25
Offline Offline

Posts: 923


MightyMax505mightymax505
Awards
« Reply #6 on: February 07, 2012, 03:31:03 PM »

Just for giggles ...  I would try to eliminate the 2100 network card for troubleshooting.  I have a E2100 embedded in my system board and had a few challenges to work through.  A firmware update seemed to fix most if not all glitches for me. 

I would go in two phases ...

-- In the "Bigfoot Networks Killer Network Manager" control panel go to the advanced tab and disable the application control for a test run of MW3.

--Next, I would go in "offline mode" in Steam and then pull the network cable for a another test.


Capturing the blue screen error as Buz stated above could be key to finding the root case as well.



And MW3 co-op mode as well as the single player are very good..  :-)   Haven't touched the multiplayer ... 
Logged

rip|Council BO2 Veteran 5+ Years' Service BlackOps Veteran BC2 Veteran LAN Partier CoD6: MW2 Service Ribbon QW:ET Service Ribbon CoD5 Service Ribbon CoD4 Service Ribbon BF2 Service Ribbon BF2142 Service Ribbon MVP in a Match Scrimmed Prodigious Poster


rip|CoyotezEye
Clan Council
User


Respect: 23
Offline Offline

Posts: 1,226


coyotezeyescoyotezeye
Awards
« Reply #7 on: February 07, 2012, 04:53:23 PM »

Yeah already played & beat single player. Not a bad story line.
Havent touched the co-op yet.

Multiplayer is same as always. Although they did tweek somethings like the perks. They renamed some, got rid of others, combined some? Some killstreaks are a bit different as well. Only seen 1 for sure hacker so far. All headshots like 30-0. I was on same team but he admitted to hacking. Seen some others I wasnt sure of.

And its only been the mutiplayer I believe when it crashed. But I will see what the code says and see about if its the Killer Nic card.

Thanks
Logged

rip|Council BO2 Veteran 6+ Years' Service BlackOps Veteran BC2 Veteran rip|member LAN Partier CoD6: MW2 Service Ribbon CoD5 Service Ribbon CoD4 Service Ribbon MVP in a Match Scrimmed BFV Service Ribbon


rip|Flatout42
Clan Members
User


Respect: 0
Offline Offline

Posts: 7


Awards
« Reply #8 on: February 07, 2012, 06:19:02 PM »

i had the exact same blue screen in all my DirextX 11 games

i used this page to figure out my problem http://www.computerhope.com/issues/ch001143.htm

it turned out that my motherboards northbridge needed more voltage for the ram so i raised the voltage by +0.10V and it fixed it, so check ur mobo's bios settings, run memtestx86, some graphical benchmarks to test your video card.
Logged

rip|member

rip|bonuspoints
Clan Members
User


Respect: 13
Offline Offline

Posts: 424



Awards
« Reply #9 on: February 07, 2012, 08:45:18 PM »

Coyote BSOD's are usually caused by driver or hardware failure. If you added something new and then you started seeing BSOD's that could very well be the culprit. Video driver's are also capable of doing this.
Logged

rip|member 4+ Years' Service BO2 Veteran BlackOps Veteran BC2 Veteran CoD5 Service Ribbon CoD4 Service Ribbon Scrimmed MVP in a Match

Pages: [1]   Go Up
  Print  
 
Jump to:  

US Eastern



TinyPortal 1.0 RC1.1 | © 2005-2010 BlocWeb