Discussion in 'NVIDIA' started by ericfomley, Jan 30, 2013.
Check what Alex MT said. Also did your ATI card ever do this? Ever?
I made sure that it was plugged in properly with the 6 pins provided with the card and even tested some 6 pins i already had and same story.
Heres the GPU-Z Log of a different and new incident. My games instead of crashing and me having to do a hard shut down, everything in game was torn and i couldnt see anything except for what apeared to be dirt. the enemies were still shooting at me and i could shoot back but all i saw on screen was a single texture. Heres the log for that:
is this issue related to the freezing?
Again what does the event viewer say.
Here are some of the errors in the event viewer:
Log Name: Application
Source: Windows Error Reporting
Date: 1/27/2013 11:24:07 PM
Event ID: 1001
Task Category: None
Fault bucket -1074341762, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0
These files may be available here:
Rechecking for solution: 0
Report Id: b2f5fed9-691b-11e2-be68-5404a6b4f0e9
Report Status: 16
Hashed bucket: 7d384db9bc83c1d066188e72d2e3f2da
<Provider Name="Windows Error Reporting" />
<TimeCreated SystemTime="2013-01-28T07:24:07.000000000Z" />
and heres another:
<Provider Name="Application Error" />
<TimeCreated SystemTime="2013-01-28T16:07:39.000000000Z" />
Ok the walls of text are not helping.
Third time. WHAT DOES THE EVENT VIEWER SAY? WHAT ERROR DOES IT THROW BEFORE THE KERNAL POWER ERROR?!?!
sorry i didnt know what that was, i found it i think
Is that the error that tripped right before the power kernel error?
yes, it occurs in each instance
i'm going to hazard a guess here. drop back to a single stick of ram and see what happens.
i'm going to assume that the problem you've got is not the video card, but is in fact your system being unstable.
I did install a new stick of ram when I installed the card and i am running on only one stick, what can i do to fix that?
remove the new stick. try with *one* of the old sticks only.
did it not occur to you prior to now that installing ram might have been the problem, not the video card? :/
i didn see that coming... lol good luck...
It was the ram i inserted. I reinserted the old ram and am returning the newer ram i had picked up. Sorry for wasting everyones time over something so simple, im glad its fixed though and thank you for all of your help.
Still having issues
Ok so the card runs great and memory was clearly the issue and i can play for about an hour now without issue. My only problem now is that after that hour all the textures get jumbled and messed up, is that because im now back to only the 4 gb ram?
After messing around with all the drivers and such and all the trouble shooting you did I would personally just reinstall windows.
I will reset my pc and see if that changes anything. It did once again freeeze. but only once.
my guess is that the ram is set up wrong, or overheating. point a fan at the RAM and see if it stops occuring.
if that doesnt work, go into the BIOS and manually set your ram voltages and timings.
I never thought of that, he should mention ram change earlier, I ran mem86+ every time for ram upgrades or change, just to make sure it is good ram and under correct timing.
if he was doing some other task with this computer such as photo shop, or VM it may crush too, and we may think it was not gpu related.
But ram problems are very difficult to find, I did up my i3 notebook form 2gb to 6gb, and start to have BSOD, I never thought of ram, since it pass 4times of mem86+, each dump is related to memory or driver, so I write to MS, and MS support discussed with me for weeks, I did clean reinstall, up bios, up driver, all failed, it would randomly BSOD. once a month or once a week. finally, I though it is dual channel, and the 2 rams are different size, but google results show lately system can do dual channel with different size. so just by guessing, I got another 4gb same make ram and changed it to 8gb. Now this BSOD stops!!!!!!!!
2+4 never have problems in winxp, but do BSODs in win7, I think is that some program lock the timing in win7, and different make of the ram have unstable issue if the timing is locked to the higher ones.
the reason 2+4 never had issues in XP is because XP cant use more than 4GB. so it simply wasnt using enough of the ram.
you are correct that RAM can behave like that, its why i never mix and match. doesnt matter if it powers up or not, doesnt mean its stable or that the memory controller can handle it.
yes, mostly, if it is notebook, no timing to change, very little setting in bios
Separate names with a comma.