Pages

Showing posts with label Crash. Show all posts
Showing posts with label Crash. Show all posts

Wednesday, June 26, 2013

Prime95 failed after 6 hours of blend test! 1.4V Vcore (fixed)/LLC3

In the previous post I was talking about how my CPU overclock has become unstable and that I was trying everything to make it stable again. After many runs of stress tests using Prime95, I settled for 1.4V Vcore in UEFI and started stress testing. No thanks to the huge VDroop this motherboard has, I had to set such a high Vcore. But in reality, the CPU was only getting 1.336V. This is with LLC level 3. 

So I let Prime95 run overnight and went to sleep. Unfortunately after about 6hrs of stress testing, it had crashed with a BSOD with code 0x124. It requires more volts it seems. I wonder how I could get by with just 1.320~1.328V the last time. It definitely must have been the lack of AVX.

So I raised the Vcore to 1.405V in UEFI and came to work, letting Prime95 run while I was at work. It's been about 4hrs 15min and still it has not crashed. Seems like I will probably be able to make it completely stable in this go or at least the next. But what I don't get is, even at LLC level 3, there is a massive VDroop. Either everyone else is lying or they have very  high tolerance. They don't seem to imply the VDroop is that high with LLC2 and LLC3. I'm not sure if this has always been the case with this board. Without using the fixed Vcore mode, you really cannot see the VDroop. And I've been using the Offset mode all this time. 

I just hope that this will be it. 12hrs of Prime stability is good enough for me. This CPU must be a bad clocker. I mean, I bought this CPU second hand but unopened. Someone must have bought a batch of these CPUs and since the ones he tested weren't good clockers, he has returned the whole batch. I guess that's the only way I could have gotten an unopened but used CPU. 


Wednesday, November 30, 2011

Logitech Gaming Software crashing ATI driver or vise versa

Since you cannot live without the ATI driver, I blame Logitech for being irresponsible. Their *new* Logitech Gaming Software is so buggy. But I have to have it because I use those special 6 buttons on the left hand corner on my G15 keyboard. Logitech’s hardware is good, and so is ATI’s or Creative’s or many others’. Just that their drivers are so lame. Crashes PCs all the time, and people blame poor Microsoft. (Ok, one – they are not poor, two – they have their own faults too)

One of the main issues I had before this clash with the ATI driver was that it would stop working when I resume the PC from standby. How lame?? The LCD would show the G15 logo and nothing would work. I have to kill the lcore.exe (that’s the exe) process and launch it back – every time. The only way to fix it was using a batch file to kill the process and launch the app. Of course, thanks to the Windows Task Scheduler, you could do it automatically. But in your head you know, you are cheating. You are cheating for a company that made crappy software. ugh!

I hardly launch the app anyways, but the last two times I did it, I was playing BF3 and it crashed both the driver and the game. Why does the game has to crash, if the driver gets reloaded? It doesn’t happen with most games. Again, crappy software.

So how did I fix the problem? I went back the legacy software, which is not elegant, but is much more stable. It fixed the problem. Guess what? As a bonus, the standby issue got fixed as well. w00t! Guess Logitech recruited some morons to make things pretty but dumb inside. (Does that remind you of another company like that? Yes, that’s you Apple!)

Glad I fixed it finally. (Mostly the standby issue.)

Related Posts Plugin for WordPress, Blogger...