GTX 460 possibly causing hard system crashes?

just a thought....i overclock all the time.....and have to keep image backups...cause when i screw up with wrong settings it will corrupt windows and all will seem fine...except weird little issue like your having

i have run linx, intel burn test, prime for hours, passed hyper pi...and yea know what i still wasn't stable...cause all of sudden when i wasn't doing anything bam windows would crash... and trust me when this happens something unseen gets corrupted and is unfixable without an image back up or os re install....your temps on your cpu are super high...god almighty high...way to high for overclocking

these people are trying to help you...and your not making it easy with that no it all attitude...if you already no it all why the fuck you here?
 
just a thought....i overclock all the time.....and have to keep image backups...cause when i screw up with wrong settings it will corrupt windows and all will seem fine...except weird little issue like your having

i have run linx, intel burn test, prime for hours, passed hyper pi...and yea know what i still wasn't stable...cause all of sudden when i wasn't doing anything bam windows would crash... and trust me when this happens something unseen gets corrupted and is unfixable without an image back up or os re install....your temps on your cpu are super high...god almighty high...way to high for overclocking

these people are trying to help you...and your not making it easy with that no it all attitude...if you already no it all why the fuck you here?

Let's just ignore the argument with that one fella.

You say god almighty high cpu temps, but I did post temps with the performance setting turned off, are those still too high as well? I know I sound like Dr. House in trying to diagnose this but It does point to certain things. It ran for over a month without flash without crashing, then all the sudden silverlight(also a video player application) started causing it as well. I searched and searched but I couldn't find out what changed over those couple hours. It's like all the sudden it just went to shit when it was fine.

I do find it strange that this all started on a different OS install then continued after I reinstalled due to one freezing occurrence corrupting the OS.

I hate reinstalling, but if I were to do it again, what process should I take in trying to pinpoint the specific driver causing the issue? I find it absolutely insane that I can remove drivers and fully clean them out of the system and i'm still stuck with the issue. Never ending loop.
 
Never told me what your 12v rail is doing.

Sandforce based SSDs are known to be random BSoD generators.

I dunno what else to tell you really at this point. I'd back everything off, run it at pure stock and see what's up. The CPU temps are just too damn high for me to think they aren't the culprit.
 
I believe this....I personally have never had a pc that developed software issues to the point it would trash an os install....or I'll say this its rare...anyway....something in the hardware is not stable...idk a bios setting....kinda like running a voltage to low or to high..i know in my bios just one setting in the wrong position....and its a junk pc...otherwise i can go years without blue screens or crashes...

I think it's helpful to reset bios to defaults...kinda like was mentioned by another person clearing the cmos sometimes does the trick....but after that some of the settings might need to be manually set...i know on mine i sure do...anyways

Something is causeing instability....not trying to state the obvious...but i think 99% of the time its hardware causing the issues some how (ram,mb,ps.card, you know)...I can tell you this regarding temps...you have a cooler about the same size as mine....the hottest mine ever reaches running burn test is around 80 degrees peak (i know were running different systems but im overclocked like mad and still running way cooler).....i was at 4400mhz and it would reach mid 80's and to me thats to hot....most would agree in needs to stay under 80 max.....you could be using to much paste possibly or its somehow not fitting correctly....idk something we need to figure out and not dismiss for sure.....

one advantage of some of the 8.1 iso's floating around is there practically already updated...so install time is pretty quick...last time i did win 7 for a customer all the updates annoyed me to death...time wise lol

might be a couple simple settings in your bios that for some reason your board needs..idk manually setting the cpu voltage...

now correct me if im wrong....but you said it was problem free running the video off the mb for that one day......might be worth trying again...i just don't personally think nvidias drivers are so bad there causing all these crashes..just my opinion.....why its not crashing without the card....thats a good question

lastly try to be open minded to all suggestions...were all doing our best to help you....the answer is here somewhere......if you had another pc it makes troubleshooting some much easier...cause then you could swap parts...just keep an open mind and you get it figured out...somebody mentioned the ssd...it actually could be something to look into as well...you never know

I'd back everything off, run it at pure stock and see what's up. The CPU temps are just too damn high for me to think they aren't the culprit.
I couldn't agree more:)

something else to consider...they make an iso (parted magic) that can be installed to usb.......i like it since it always you to do internal wipe on the drive between installs or backups....peace of mind keeping the ssd running smooth...certainly couldn't hurt anything...just don't go wipeing the wrong drive lol
 
Last edited:
Sandforce based SSDs are known to be random BSoD generators.
Only if the drive has either locked or is just about to. I've never heard of them blue screening for an extended period of time. Mine (stupid OCZ 240 GB Vertex 2e) locked totally the first time.
 
checklist

1. Bad RAM
2. Unstable memory settings/voltage
3. Unstable CPU overclock
4. Too much dust build-up
5. Software corruption due to crashes caused by 1, 2, 3, 4.
6. Specific software bugs
7. Cheap/inadequate/old power supplies
8. ESD damage (latent defects from static electricity)
9. Bad or dying CPU or GPU
10. Unstable GPU voltage (too little when underclocking, too little when overclocking)
11. CPU or GPU that isn't cooled enough
12. Bad power (brownouts, surges), including lightning
13. Gamma rays (for equipment in space)
14. Malware
15. Specific hardware bugs (e.g. Sandforce's "panic mode")
16. Physical damage caused by user, shipping, etc. (e.g. bent pins, shorts from metallic grease)
17. Bad cables (including using extension cords and power strips)
18. Poor and/or inadequate case airflow
19. Failing pumps for water cooling
20. Incompatible hardware (conflicting)
21. Incompatible software (conflicts)
22. Incorrect BIOS settings and/or outdated/buggy BIOS
23. Hackers (physical malware, such as NSA-modified routers and network cards)
24. Inadequate RAM (relying too much on swap file)
25. Incorrect OS or software settings
26. Failing hard disk or SSD
27. Out of date driver
28. Memory leakage (restart computer to "fix")
 
The list should also have loose cables/connections and connections that are hampered by corrosion/dirt.
 
checklist

1. Bad RAM
2. Unstable memory settings/voltage
3. Unstable CPU overclock
4. Too much dust build-up
5. Software corruption due to crashes caused by 1, 2, 3, 4.
6. Specific software bugs
7. Cheap/inadequate/old power supplies
8. ESD damage (latent defects from static electricity)
9. Bad or dying CPU or GPU
10. Unstable GPU voltage (too little when underclocking, too little when overclocking)
11. CPU or GPU that isn't cooled enough
12. Bad power (brownouts, surges), including lightning
13. Gamma rays (for equipment in space)
14. Malware
15. Specific hardware bugs (e.g. Sandforce's "panic mode")
16. Physical damage caused by user, shipping, etc. (e.g. bent pins, shorts from metallic grease)
17. Bad cables (including using extension cords and power strips)
18. Poor and/or inadequate case airflow
19. Failing pumps for water cooling
20. Incompatible hardware (conflicting)
21. Incompatible software (conflicts)
22. Incorrect BIOS settings and/or outdated/buggy BIOS
23. Hackers (physical malware, such as NSA-modified routers and network cards)
24. Inadequate RAM (relying too much on swap file)
25. Incorrect OS or software settings
26. Failing hard disk or SSD
27. Out of date driver
28. Memory leakage (restart computer to "fix")

thats actually a pretty good list.....i agree 100%...it really can be any of those
 
continued:

29. Is the computer plugged in securely and the power active for the circuit?
30. Is the monitor turned on, if it’s an external one? Is it connected correctly and set to the right input?
31. Loose cables or poor connections from corrosion/dust/oil/dirt.
32. Incompatible mixture of RAM sticks (different chips that have differing voltages and speeds)
33. Motherboard that may have problems with having more than a pair of RAM sticks (e.g. P35-DS3L).
34. RAM not compatible with motherboard (capacity, speed, or voltage).
35. Hot spots on chip (usually CPU) from incorrect application of thermal compound.
36. Damage to aluminum heatsink from liquid metal thermal compound causing overheating.
37. Excessive thermal compound, too little thermal compound, thermal pads that aren't very effective.
38. Strain on motherboard from heavy heat sinks or graphics cards causing motherboard to bend.
39. Damage to motherboard from moving case with heavy heat sink or graphics card attached.
40. Too-optimistic specs for hardware, such as a motherboard claiming that it can power a 135 watt CPU, despite thin traces, lackluster VRM cooling, and few power phases.
41. Old capacitors.
42. Electromigration, which causes "aging" of chips, resulting in instability. Lower voltages and clock speeds may help bring back the stability.
 
Back
Top