I think we've lost... two televisions, a router, and various other things to lightning. Needless to say, storms make me a bit nervous these days.
But as for OCing, nothing is. While I'm not against it either, I didn't feel the need to OC anything with this build. It's been stock since it was built. The only thing that's been adjusted at all would be the memory set to XMP-1 to run at the rated speed... but it's been that way since day 1.
In any event, here's the CPU-Z screens.
At a quick look, everything looks fine on the cpuz screenshots. Do you have Precision X or a similar program? If not get one so you can set a custom fan profile and monitor the temps. Then I would like you to run Furmark Video Card Stress Test (Video Card - Stress Test with Furmark). If you have never run it before, it stresses your card out and temps will rise very quick and very high. Stop the test if they get too high. Let it run until the temps stop increasing and level out which should be a few minutes. But again, stop the test if the temps get too hot. Look for any artifacts while it is running too.
As far as temps go, I use SpeedFan to monitor them. This motherboard has a spiffy little LED on it that tells me the CPU temp at a glance (55c currently, with a game, Firefox, and mIRC running). As far as the GPU temp goes, I actually haven't monitored the 760 since I had to RMA the last 570 and they sent the 760 in its place.
With the summer temperatures in mind, I just recently replaced two case fans and reapplied TIM to the CPU heatsink. I'm seeing lower temps now than I have in a long time. The highest it gets is around 70c with a Source game running (TF2, Portal 2, etc.), but they run hotter than others for whatever reason. It gets around 60-62c with WoW running, 60-65c with ESO. Depends on how much is going on and where I currently am in the game.
I'll give SpeedFan a go and see what the GPU is running at. I actually hadn't used it in a long time since a streak of BSODs a while back... I'd say around 8 months or so.
Edit: SpeedFan currently states:
CPU: 55-57c (Accurate, as I can peek at the LED on the motherboard to confirm.)
GPU: 57-59c (Seems about right for this game, and for a GPU in general.)
I'll give Furmark a go here in just a bit though. I'd used it once before in the past, but haven't in a while.
OK, But Precision X and Afterburner allow you to set a custom fan profile for the GPU and put allkinds of reading on screen during gaming so you always know what's going on with your card.
After a few minutes with Furmark, the hottest the GPU climbed was 81c, with no artifacts.
About the only thing I know to try at this point would be to take the modules out, clean the contacts, reseat them, and potentially do the same with the video card... and check all my connections to make sure they're good while I've got the case open.
Everything was thoroughly cleaned when I reapplied the TIM a couple weeks ago. Since I live in the South, off of a dirt road, things can get pretty dusty pretty quick, so I have to stay on top of this especially in the Spring/Summer months.
Speaking of reseating the modules, they're currently in the right side of the paired-slots (0/x 0/x 0/x; x = slotted module); think I should switch them back to the left sides if I'm going to clean the contacts anyway?
Another BSOD; BCCode 10e, "video memory manager has encountered an error" or something of the like.
Updating video driver.. and done. Probably really needed to do that, as the nvidia folder had gotten quite large with driver updates over the course of a year or so. About 2.6GB worth of junk. Now there's a clean install with only the Graphics/PhysX drivers. Meant to do this earlier, but put it off and then forgot. Bleh.
Worth noting, I guess, is that this only seems to reliably happen when playing Team Fortress 2. I can sit here and play something else for hours on end, but run TF2 and get a BSOD within 5-10 minutes it seems.
Tomorrow I'll try again and see how it goes.
Last edited by Requimatic; 27 May 2015 at 03:07.
Here's what it said
What you did was probably the best thing you can do.Code:VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e) The video memory manager encountered a condition that it can't recover from. By crashing, the video memory manager is attempting to get enough information into the minidump such that somebody can pinpoint what lead to this condition. Arguments: Arg1: 0000000000000016, Driver broke the guaranteed DMA buffer model contract. Arg2: fffffa800891d720 Arg3: 0000000000003000 Arg4: 0000000000000400
Well, this PC is still doing weird things and I'm at a loss as to what's causing it at this point.
I played TF2 for a bit a little while ago, and while it didn't BSOD in the time I played it (I quit when I noticed a missing texture on a crate that was stacked on top of crates using the same texture), when I exited the game, Steam's Game Overlay UI crashed (with user32.dll as the faulting module). After I ended it, I attempted to open the task manager and it froze up. CPU usage spiked, as the temperature rose quite high during this.
After a few minutes of that, I logged off this user profile, back on, and it was still doing this mess, so I restart. All's fine now, it seems, but I tried running SFC and ran in to the same problem as earlier in the thread (with seemingly the same items from before in CBS.log).
So, I don't know what's wrong with this thing. I know it's old, so hardware failure over time is expected, but when it checks out via testing and things are still going awry, it's frustrating being unable to pinpoint the cause of these kinds of things.
Edit: I ran the findstr command from earlier and uploaded the results.
Edit2: And now MSE just randomly shut off and won't restart.
Last edited by Requimatic; 27 May 2015 at 14:54.
Run Seatools For DOS, if you haven't already. Run the short and the long tests
SeaTools for DOS and Windows - How to Use
Please go into BIOS and tell me the values of the +12V, +5V and +3.3V. While you are in there look at your Sata controller and see what the Mode is (IDEM AHCI or Raid) Set optimized defaults, set the Sata Controller to what it is right now, set the ram at Manufacturer's specs, set your Boot order, save and exit.
I would run the Seatools first.
The WD DOS tool didn't want to run (after typing the executable's name, the screen just goes black and does nothing for however long I left it), so I'll try that again with Seatools.
Voltages:
12v = 12.03v
5v = not sure, the only one close to 5v was "VCC" at 4.83v
3.3v = 3.15v
The Sata controller was set to AHCI.
Last edited by Requimatic; 27 May 2015 at 16:41.
Quote