Sign in to follow this  
brianbash

I'm a victim of the nVidia driver beast.

Recommended Posts

This post is to voice my most recent experience regarding the issues some have been having with the new drivers.

 

The reboot needed to complete driver installation was the last my i7-5930K would have. Power cycling began, would never post to windows or even DOS. It would freeze and reboot at different times. Every blue moon, it would tease me with the windows sign-in screen, so I would try to enter my password...hah! Reboot. Even after replacing the motherboard, PSU, ram, video card, pulled all the hard drives to get to BIOS only, it still wouldn't get to windows. I was exhausted and knew the dreaded had occurred. After dropping it to the wonderful tech personnel at Fry's for diagnostic tests, my fears were confirmed. My i7-5930K had lost a core. I purchased another and am currently back home repairing my gigantic P3D install. I have switched sides and will remain with Team Red from now on. One thing I noticed from my first glance with my new Fury X is that the famous anti-aliasing shimmer had died with my CPU. Good Riddance!  :Tounge:

 

Sure, it could be an extremely odd coincidence it happend when it did, but nonetheless I feel it needs to be spoken for.

 

 

Blue Side Up gentlemen.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

I really don't think a GFX driver would kill your CPU.  How OCd was it?

Share this post


Link to post
Share on other sites

 

 


I really don't think a GFX driver would kill your CPU. How OCd was it?

 

Agreed.  As a former hardware computer engineer, I just don't see how this is possible and I overclocking as well (or an unstable core at purchase that finally went).

 

Was it core 0?

Share this post


Link to post
Share on other sites

Definitely something off here. Really don't see how a GPU could kill a CPU in that manner.

Share this post


Link to post
Share on other sites

if anything, a bad driver would eat the GPU or just corrupt files but in  no way would it blow a core on the CPU. Something else happened.

 

Vic

Share this post


Link to post
Share on other sites

 


I really don't think a GFX driver would kill your CPU.  How OCd was it?

 

No OC'ing done by me. I stay away from doing that. This is also my SoundGrid server for my production work so it's vital that I keep things stock and stable. I'm not saying that it was 100% the driver, I'm just saying it's an extremely odd coincidence and wanted to share what had happend. Is there any power connection between the GPU and CPU that could cause something like this? Either way, my system didn't want to go into windows and maybe in my troubleshooting rage I killed the CPU somehow.

 

Oh well, I was told that Intel is a great company when it comes to RMA situations and the fact that I got the processor less than 2 months ago may be enough for them to fix the situation I have had.

 

 


Was it core 0?

 

 

Not sure, I was told a core was gone but thats it. Thank you for the insight though, I will ask which core is bad in the future if I have to.

Share this post


Link to post
Share on other sites

Often times when Windows gets close to booting or actually does boot and then crashes/reboots it can be a bad stick of ram. Upgrading your VC driver and having a bad ram is certainly quite a coincidence but it's worth a try. Hopefully you know the drill, i.e: remove all but one stick of ram, boot, try again,...etc

Share this post


Link to post
Share on other sites
Oh well, I was told that Intel is a great company when it comes to RMA situations and the fact that I got the processor less than 2 months ago may be enough for them to fix the situation I have had.

 

 

 

They certainly will "fix the situation" if the CPU is defective. You will get a replacement. It's a three year warranty.

 

I would say make sure you update the motherboard BIOS, as a corrupted BIOS can lose a core... but you say you've replaced the motherboard.

Share this post


Link to post
Share on other sites

I think it'd be more likely to be a power supply issue with the re-booting than a software driver....

Share this post


Link to post
Share on other sites

Could be, I had a PSU issue that caused re-booting.

 

OP should check all power cables. Check they are properly seated. And very importantly, check the ATX connector pins for scorching. I had a faulty ATX extender that caused the pins to arc out and scorch resulting in re-booting.

Share this post


Link to post
Share on other sites

probaly something with the memcontroller, well known problem with the Hasfail-E

 

They suddenly don't want to boot even after a normal shutdown or ar completely dead.

 

It happen for me with a 5820k , worked perfect normal shutdown next start dead.

 

The thing it was no OC no fast mems default voltages, a Cad workstation.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this