BulletProof Nerds Gaming Community
February 09, 2012, 04:01:31 PM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: TO POST ON THE FORUMS YOU MUST REGISTER ON THE BPN HOMEPAGE, ONCE YOU ARE LOGGED IN THERE, IT AUTOMATICALLY LOGS YOU INTO THE FORUMS AS WELL.  IF YOU STILL CAN'T POST THEN LOG OUT OF THE WEBSITE AND LOG BACK IN, THEN COME BACK TO THE FORUMS.
 
   Home   Help BPN HOMEPAGE Search Login Register  
Pages: 1   Go Down
  Print  
Author Topic: MW2 Screen Goes Black  (Read 1160 times)
0 Members and 1 Guest are viewing this topic.
Got_Amm0
250 POSTS CLUB
*

BPN Props: 2
Offline Offline

Posts: 252



WWW Awards
« on: March 08, 2010, 06:22:40 AM »

i wanted to see if anyone else is having this problem.

ill be playing mw2 and after an hour or so my screen will go black, and the sound loops. I need to turn off my pc and turn it back on. all my motherboard drivers are up to date and im running 196.21 nvidia drivers.

specs
amd 965
msi nf980-g65
8gb ddr3
850watt PSU

thanks guys

Thanks, William
BPN Admin
cygnus
250 POSTS CLUB
*

BPN Props: 7
Offline Offline

Posts: 307



Awards
« Reply #1 on: March 08, 2010, 09:19:15 AM »

Do you have a sound card installed?  Is it installed in the slot next to the video card?  If not, try moving to the PCI slot beside the video adapter.



Proud video junkie and addict since 1978 - Space Invaders rulz!
Schlup
Master Admin
1000 POSTS CLUB!!!
*
*

BPN Props: 1226
Offline Offline

Posts: 6595



WWW Awards
« Reply #2 on: March 08, 2010, 09:34:07 AM »

Very well may be your OC being unstable.  You need to run some stability tests for OVER an hour to rule that out.

Malhovic
100 POSTS CLUB
*

BPN Props: 7
Offline Offline

Posts: 144

Later BPN


Awards
« Reply #3 on: March 08, 2010, 10:43:58 AM »

Being that the system could run all the checks from 3DMark05 and there weren't any voltage increases I would doubt there is an issue with the clocks. Especially since the memory is at stock rating, just had to manually set it so the mobo would use it (just like most 1600 rated memory). As for the processor, GA if you go back into your BIOs and change the multiplier from x19 to x18. See if that fixes the issue. If so, we may need to boost your voltage slightly to hold the 3.8GHz.
Schlup
Master Admin
1000 POSTS CLUB!!!
*
*

BPN Props: 1226
Offline Offline

Posts: 6595



WWW Awards
« Reply #4 on: March 08, 2010, 11:03:42 AM »

Running a 10 min long 3DMark05 hardly guarantees stability, just means it will run for 10 minutes.  You need to run a stress test for as long as you can see yourself using the computer.  Personally I may be on my computer for 10 hours at a time during some runs so I run stress tests for 10 hours to make sure it doesn't crash during that period.  That being said, IF you can boot up and and run a 3DMark05 you are VERY close to being right on your OC.  I wouldn't change any settings just yet, run the stress test for a couple hours and see if it crashes.  If it does then I'd bump your VCore up one notch, you'll get more heat but stability is worth it!

P.S. You know what a good stress test is?  Folding at home SMP high performance client!

Stuntin
Guest
« Reply #5 on: March 08, 2010, 11:08:28 AM »

Very well may be your OC being unstable.  You need to run some stability tests for OVER an hour to rule that out.
+1 seems like its a oc issue not on the cpu but the ram put your ram back to stock and then try it.U said ddr3 but wat kind of ram is it?
Schlup
Master Admin
1000 POSTS CLUB!!!
*
*

BPN Props: 1226
Offline Offline

Posts: 6595



WWW Awards
« Reply #6 on: March 08, 2010, 11:24:20 AM »

He didn't overclock his ram, he simply got it to what should have been stock settings.

tehfunk101
Guest
« Reply #7 on: March 08, 2010, 02:09:37 PM »

my guess is that theres a temperature issue or the ram is undervolted (some mobo's out there run will run ram at a set voltage, rather than the manufacturer's recommended value)
Pages: 1   Go Up
  Print  
 
Jump to:  


Powered by SMF 1.1.16 | SMF © 2011, Simple Machines Page created in 0.267 seconds with 22 queries.