Author Topic: Couple problems  (Read 508 times)

Offline 1701E

  • Silver Member
  • ****
  • Posts: 1896
      • VBF-18 Bearcats
Couple problems
« on: May 25, 2010, 02:16:54 PM »
Got a few troubles recently and I'm clueless as to what it is, so as always I thought I'd come looking for help. :)

Problem 1: While playing Aces High randomly I will see the screen flick and then the plane acts like it has a "White noise" filter applied.  Blue/white pixels (the color of the sky normally) will flash in random spots and in large quantities (about 60% of the plane has this "noise" over it).  The pixels will flash once and move so it's not a constant image of noise.  My Frame-rate gets cut in half while this is going on.  However if I look away from the plane everything is fine, but as soon as I look back it's there.  This has only happened in the WWI arena and it's only happened 3 times (once a month ago and twice yesterday).  Clueless as to what is causing this.  Also, this persists onto the desktop until I restart computer.

When gaming I have the following open/running in the background: Windows Media Center, Threatfire, ESET NOD32, Logitech Mouse/keyboard settings and Gamer profile and EVGA Precision.

Problem 2: This isn't in Aces High but it's very annoying to say the least.  In DiRT 2 I will randomly get a BSOD when doing anything from sitting at the menu to driving a race.  I have run Everest in the background to keep track of every possible sensor on the GPU/CPU/PSU and only ever get a warning on occasion about my GPU hitting 61C (CPU warns at 50C, GPU at 60-63C, and if any PSU voltage goes beyond +/- 5%).  I have seen at least 2 different types of BSOD's from this; one was a typical one that I barely caught before it reset and the other one sat there and said something about "Volmgrx.sys" and "atapi.sys".

When gaming I have the same things running as AH with the exception of WMC (has crashed with and without it open).

I have run ESET/Threatfire/Malware Bytes and Memtest 86+ V4.10 and nothing was found, no errors.

Specs are as such:

------------------
System Information
------------------
Time of this report: 5/25/2010, 14:47:46
       Machine name: XCELSIOR-PC
   Operating System: Windows 7 Ultimate 32-bit (6.1, Build 7600) (7600.win7_gdr.100226-1909)
           Language: English (Regional Setting: English)
System Manufacturer: BIOSTAR Group
       System Model: A785GE
               BIOS: Default System BIOS
          Processor: AMD Phenom(tm) II X2 555 Processor (2 CPUs), ~3.2GHz
             Memory: 2048MB RAM
Available OS Memory: 2048MB RAM
          Page File: 859MB used, 2211MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: Using System DPI
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
     DxDiag Version: 6.01.7600.16385 32bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
          Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (retail)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

---------------
Display Devices
---------------
          Card name: NVIDIA GeForce GTX 260
       Manufacturer: NVIDIA
          Chip type: GeForce GTX 260
           DAC type: Integrated RAMDAC
         Device Key: Enum\PCI\VEN_10DE&DEV_05E2&SUBSYS_12553842&REV_A1
     Display Memory: 1649 MB
   Dedicated Memory: 881 MB
      Shared Memory: 767 MB
       Current Mode: 1680 x 1050 (32 bit) (59Hz)
       Monitor Name: Acer LCD Monitor X223W
      Monitor Model: Acer X223W
         Monitor Id: ACR0009
        Native Mode: 1680 x 1050(p) (59.954Hz)
        Output Type: DVI
        Driver Name: nvd3dum.dll,nvwgf2um.dll,nvwgf2um.dll
Driver File Version: 8.17.0011.9713 (English)
     Driver Version: 8.17.11.9713
        DDI Version: 10
       Driver Model: WDDM 1.1
  Driver Attributes: Final Retail
   Driver Date/Size: 3/16/2010 02:51:59, 9386088 bytes
        WHQL Logo'd: Yes
    WHQL Date Stamp:
  Device Identifier: {D7B71E3E-46A2-11CF-037E-5E321FC2C535}
          Vendor ID: 0x10DE
          Device ID: 0x05E2
          SubSys ID: 0x12553842
        Revision ID: 0x00A1
 Driver Strong Name: oem24.inf:NVIDIA_SetA_Devices.NTx86.6.1:Section003:8.17.11.9713:pci\ven_10de&dev_05e2
     Rank Of Driver: 00E62001
        Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
Deinterlace Caps: too much to fit here
       D3D9 Overlay: Supported
            DXVA-HD: Supported
       DDraw Status: Enabled
         D3D Status: Enabled
         AGP Status: Enabled


-------------
Sound Devices
-------------
            Description: Speakers (SB Audigy)
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: PCI\VEN_1102&DEV_0007&SUBSYS_100A1102&REV_00
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: P17.sys
         Driver Version: 5.12.0001.2020 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 10/16/2009 03:11:56, 1168896 bytes
            Other Files:
        Driver Provider: CREATIVE
         HW Accel Level: Basic
              Cap Flags: 0xF1F
    Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

            Description: Digital Audio Interface (SB Audigy)
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID: PCI\VEN_1102&DEV_0007&SUBSYS_100A1102&REV_00
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: P17.sys
         Driver Version: 5.12.0001.2020 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 10/16/2009 03:11:56, 1168896 bytes
            Other Files:
        Driver Provider: CREATIVE
         HW Accel Level: Basic
              Cap Flags: 0xF1F
    Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No





Thanks for any help/ideas. :salute
ID: Xcelsior
R.I.P. Fallen Friends & Family

"The only ones who should kill are those prepared to be killed"

Offline Chalenge

  • Plutonium Member
  • *******
  • Posts: 15179
Re: Couple problems
« Reply #1 on: May 25, 2010, 02:28:18 PM »
Sounds like a memory problem I once had (RAM not brains). I would run memtest86 on individual modules (did you?) to test main memory. Its possible that just changing your memory voltage a little bit could get rid of the problem but you do want to test modules first. Good starting point in any case.

EDIT: Yes I read where you said you tested but you need to run single module tests overnight and let them repeat... wasnt clear if you did it that way.

And the bad news is there is a possibility of a latency/compatibility issue between your CPU/GPU and sound card. To me its incredible that so many manufacturers can get along at all but SB cards and Nvidia do not always play nice. Its one of the reasons I dumped SB.
« Last Edit: May 25, 2010, 02:35:48 PM by Chalenge »
If you like the Sick Puppy Custom Sound Pack the please consider contributing for future updates by sending a months dues to Hitech Creations for account "Chalenge." Every little bit helps.

Offline 1701E

  • Silver Member
  • ****
  • Posts: 1896
      • VBF-18 Bearcats
Re: Couple problems
« Reply #2 on: May 25, 2010, 02:34:50 PM »
Sounds like a memory problem I once had (RAM not brains). I would run memtest86 on individual modules (did you?) to test main memory. Its possible that just changing your memory voltage a little bit could get rid of the problem but you do want to test modules first. Good starting point in any case.

EDIT: Yes I read where you said you tested but you need to run single module tests overnight and let them repeat... wasnt clear if you did it that way.


Ah I just ran the default test (guess both at the same time?) for 2 passes.  Never used Memtest before so I wasn't sure what exactly to do.  I'll test individual modules tonight, Thanks. :)
ID: Xcelsior
R.I.P. Fallen Friends & Family

"The only ones who should kill are those prepared to be killed"

Offline Chalenge

  • Plutonium Member
  • *******
  • Posts: 15179
Re: Couple problems
« Reply #3 on: May 25, 2010, 02:37:08 PM »
Make sure you read that last part I added. You might also try using onboard audio without the SB installed and see if your BSOD happens. Its not good for AH but you need to know. Its the faster test anyway.
« Last Edit: May 25, 2010, 02:38:45 PM by Chalenge »
If you like the Sick Puppy Custom Sound Pack the please consider contributing for future updates by sending a months dues to Hitech Creations for account "Chalenge." Every little bit helps.

Offline Ghastly

  • Silver Member
  • ****
  • Posts: 1756
Re: Couple problems
« Reply #4 on: May 26, 2010, 07:45:13 AM »
I know you said you are running Everest, but if my own system was doing what you've described, I'd be very heavily focused on a bad or overheating vid card.   Bad Memory isn't going to cut frame rate in half when the video anomaly happens - a bad video card, or one that's engaging thermal throttling, would.

Just MHO.  Take it for what it cost you.

<S>
"Curse your sudden (but inevitable!) betrayal!"
Grue

Offline Chalenge

  • Plutonium Member
  • *******
  • Posts: 15179
Re: Couple problems
« Reply #5 on: May 26, 2010, 10:25:26 AM »
Could be. Its odd that it only happens in WW1 and that instead of pixel weirdness it changes to BSOD in DiRT2.

This latency issue with SB also causes random lockups of the OS (zero response) which he hasnt mentioned but it could still be driving the BSODs.
If you like the Sick Puppy Custom Sound Pack the please consider contributing for future updates by sending a months dues to Hitech Creations for account "Chalenge." Every little bit helps.

Offline 1701E

  • Silver Member
  • ****
  • Posts: 1896
      • VBF-18 Bearcats
Re: Couple problems
« Reply #6 on: May 26, 2010, 12:32:28 PM »
Well I let the RAM do 10 passes each (should I go longer?  Each one took 2.5 hours as it is) and got nothing.  Gonna try without the soundcard today and see what that does.  If there is some kind of issue between CPU, GPU or Soundcard I'd much rather it be the Sound....least that doesn't cost me 2-300$ to replace.

On another note, this never started happening until I installed my Phenom II X2 555.  Can not updating BIOS cause any of this?  Biostar stated depending on Motherboard Revision it may be needed to even run AM3, but since mine ran without it I assumed I had a newer revision.

As for overheating GPU, I don't think it's that unless I have a bad sensor somewhere.  I run everest in the background on occasion but primarily I use EVGA Precision to watch temps in the OSD and they have been the same consistently since I bought the card (38-40c idle and 50-59c load with spikes to ~63c).  Plus it would be odd if it overheated only in those two games and not some of my other heavy use games.  If it is bad in someway (like my 7900GS' ram) at least I have a lifetime warranty. :)
ID: Xcelsior
R.I.P. Fallen Friends & Family

"The only ones who should kill are those prepared to be killed"

Offline TequilaChaser

  • AH Training Corps - Retired
  • Plutonium Member
  • *******
  • Posts: 10173
      • The Damned - founded by Ptero in 1988
Re: Couple problems
« Reply #7 on: May 26, 2010, 12:49:44 PM »
1701E,
I read in some thread or possibly another forum, that the SB Audigy sound cards do not work very well if at all, with Windows 7......

you might want to do some research into this, yourself, and see what others have posted regarding Windows 7 & SB Audigy soundcards

hope this helps
"When one considers just what they should say to a new pilot who is logging in Aces High, the mind becomes confused in the complex maze of info it is necessary for the new player to know. All of it is important; most of it vital; and all of it just too much for one brain to absorb in 1-2 lessons" TC

Offline MrRiplEy[H]

  • Persona Non Grata
  • Plutonium Member
  • *******
  • Posts: 11633
Re: Couple problems
« Reply #8 on: May 26, 2010, 02:55:22 PM »
I can't tell from the images if you overclocked your card or not but your symptoms fit video ram failures. If you have increased the memory speed on your vc it can cause 'artifacting' which look pretty much like the symptoms you described. Any videocard can be made to produce this kind of distorted images just by pushing the video ram speed too high.

First rule of thumb - when trouble arises, disable ALL overclocks on your system and see if it fixes your problem. Only if that won't help you have a true problem somewhere else.

As what goes for creative junk, I'd throw them away too. Not so long ago I trashed a perfectly good videocard by mistake. Symptoms were: whenever I started a 3D application (game) the computer would instantly reboot. I thought the culprit was the videocard and since my sons computer had an el-cheapo 4830 anyway I trashed it and got a 5850 instead. Only problem was that the reboot issue continued with the new card!

By then I went into full troubleshooting mode and isolated every component in the system. The culprit was the miserable Audigy soundcard that had worked for 2 years untill then. For whatever the reason, it caused the system to instantly reboot whenever 3D was initiated. Sound played fine..
Definiteness of purpose is the starting point of all achievement. –W. Clement Stone

Offline Chalenge

  • Plutonium Member
  • *******
  • Posts: 15179
Re: Couple problems
« Reply #9 on: May 26, 2010, 04:30:49 PM »
Well I let the RAM do 10 passes each (should I go longer?  Each one took 2.5 hours as it is) and got nothing. 

Sounds like your good on memory. Pulling the SB will be a good indication of which direction to go in next. Your temps are all in line but temps are not the only thing that can kill video memory. Lets hope pulling the SB makes everything right again.
If you like the Sick Puppy Custom Sound Pack the please consider contributing for future updates by sending a months dues to Hitech Creations for account "Chalenge." Every little bit helps.

Offline Masherbrum

  • Radioactive Member
  • *******
  • Posts: 22416
Re: Couple problems
« Reply #10 on: May 26, 2010, 05:08:53 PM »
I can't tell from the images if you overclocked your card or not but your symptoms fit video ram failures. If you have increased the memory speed on your vc it can cause 'artifacting' which look pretty much like the symptoms you described. Any videocard can be made to produce this kind of distorted images just by pushing the video ram speed too high.

First rule of thumb - when trouble arises, disable ALL overclocks on your system and see if it fixes your problem. Only if that won't help you have a true problem somewhere else.

As what goes for creative junk, I'd throw them away too. Not so long ago I trashed a perfectly good videocard by mistake. Symptoms were: whenever I started a 3D application (game) the computer would instantly reboot. I thought the culprit was the videocard and since my sons computer had an el-cheapo 4830 anyway I trashed it and got a 5850 instead. Only problem was that the reboot issue continued with the new card!

By then I went into full troubleshooting mode and isolated every component in the system. The culprit was the miserable Audigy soundcard that had worked for 2 years untill then. For whatever the reason, it caused the system to instantly reboot whenever 3D was initiated. Sound played fine..

Yep. 
FSO Squad 412th FNVG
http://worldfamousfridaynighters.com/
Co-Founder of DFC

Offline 1701E

  • Silver Member
  • ****
  • Posts: 1896
      • VBF-18 Bearcats
Re: Couple problems
« Reply #11 on: May 26, 2010, 06:55:37 PM »
Well I haven't had a BSOD in Dirt 2 after about 1.5 hours and I tried everything I could to get it to crash (recreated everything I have control over but without an OC or Soundcard).  I haven't played much AH to test that one yet, but with as random as that problem is it's hard to recreate it.  So hopefully it was the OC or Soundcard but I'm going to give it more time to be safe.
One thing I found weird is that the AH problem only seemed to happen when I turned my OC down from what I had it to something lower (pic shows it after lowering everything about 20-30 ticks).  I turned it down recently due to everything else seemed dieing around me electronic-wise so I was being safe.

If somehow it's VRAM failure wouldn't I notice it in other games such as Crysis, CnC or Resident Evil?  They are more graphics demanding so I figured they'd show signs of it too.  When my 7900GS had bad VRAM it showed signs in everything I did and only lowering the load on GPU helped any.  Then again I am likely way off here. :)


Also the OC on GPU is just barely above that of a factory Over-clocked GPU that EVGA sells.
Default is: 576 / 1242 / 999.
Picture shows 630 / 1358 / 1105.
Factory OC is: 626 / 1350 / 1053.
Max I ran for a short while was: 650 / 1401 / 1140.
ID: Xcelsior
R.I.P. Fallen Friends & Family

"The only ones who should kill are those prepared to be killed"