Solved Bsod

[cowboy5345]

re did the driver got a couple more bsod's

 

[Vir Gnarus]

I'm seeing some data suffering bit flips, which means a bit of data got inadvertently zeroed (removed) so it means something is either smearing it or the hardware (most likely RAM) that is holding the data isn't retaining it properly. It may be caused by driver bugs (not often, though), so I recommend turning on Driver Verifier again and letting it crash the system and have us check the new crashdump. If you've altered anything during this troubleshooting period, you should always test with Driver Verifier afterwards, as those crashdumps are more accurate than without DV on.

I'm late in the scene, so correct me if I'm wrong, but how many passes on Memtest did you run? You could have Memtest run at least 7 consecutive passes. Also, if you haven't already, run Prime95 on Torture Test on Blend settings for a few hours (make sure to check temps with HwInfo - sensors only option - cuz it can run hot!). If it crashes/fails, then run again but on Large FFT settings this time. Report to us results of each test.

I've been alerted from others that you may not be setting up Driver Verifier correctly. Provided that you are following instructions on the article here, one thing you need to make sure of is that you click the Finish button at the end and that you restart the system cleanly afterwards. The system must at least shut down in a clean manner for Driver Verifier settings to kick in, otherwise all settings will be lost. If the system crashes, locks up or you manually shut down the system, again the settings will be lost.

Now, there is a chance DV may cause the system to enter a boot loop after a restart, in which case that means it is doing its job by detecting a driver bug during driver load at Windows startup and is BSODing the system as a result. You can enter Safe Mode (consult the article) to disable Driver Verifier from there and then restart into normal Windows to upload the new crashdumps to us for evaluation.

 

[cowboy5345]

im hoping it is ram because that's cheap and easy to replace, it did start these bsod's after i put the new parts in i will do all that and if i get a crash from any of those i will upload them

 

[cowboy5345]

i was running prime95 and i got this

 

[Pauly]

Were you monitoring temperatures while doing it as instructed ?
Any signs of overheating while running ?

Did you run memtest yet, if not give it a run overnight, let us know

 

[cowboy5345]

i was running prime both tests crashed on both and also temps are good i have a hyper 212 on it, here are the dumps

 

[Vir Gnarus]

Define 'good'? Have you actually confirmed the temps are good? Just because the cooler is sufficient doesn't mean it may not be installed properly, or that the thermal paste has wasted away. Having Hwinfo on Sensors only will suffice in checking to see if temps are stable. Again run Prime95 during it to stress test it.

Judging by the Prime95 failures on both counts, if your temps have been fine, and you have not been overclocking the system any, then out of the PSU, Mobo and CPU suspects I put most blame on the CPU being bad. The PSU and Mobo can still be suspect, but the Large FFT test failing often tells that it's more likely the CPU, since Large FFT test primarily (not entirely, though) tests the internal CPU caches and instruction set.

Btw, speaking of overclocking, if you know you have not personally overclocked this system, check your motherboard's default settings to make sure they aren't set to some 'optimal' defaults, and set them to any safe default values. Often times I've seen mobos actually overclocking the system in even their 'normal default' because they assume it's good enough for any setup, which is erroneous.

 

[cowboy5345]

is this a sign its going bad because its been like that for almost a year

 

[cowboy5345]

i pulled a stick of ram out and ran both tests again no crashes n so far ive been playing some heavy load games and no blue screens could it have been just a tricky stick of ram?

 

[Vir Gnarus]

Sounds either that or an incompatibility with that stick or the RAM setup. Sometimes changing the way the RAM is installed (like how much and which slots) can make the difference between being compatible and being incompatible. Make sure to check with your motherboard's memory compatibility table.

Btw, the CPU-Z thing only is describing details of the processor. It is not displaying any diagnostic information beyond that. It will neither tell you if it's going bad or doing good, it's just to present spec details.

 

[cowboy5345]

i know it supports up to 16 gigs of ram and i had 8 and took a 2 gig stick out and i never had dual channel engaged, so is it possible that stick is still good??

 

[Vir Gnarus]

I don't know. You'll need to go to your motherboard vendor's website and check the RAM compatibility table for your motherboard and see if the setup you have is listed as compatible. It doesn't have to be exactly the same model, but if a similar model works with the same configuration (same amount of RAM, slots used, etc.) then there's a good possibility that what you have should be good for your mobo.

The think I just don't understand though is how that stick evaded Memtest. If you wish you can try testing just that solitary stick with Memtest overnight to really pressure it. Otherwise I'm pretty baffled, especially since Prime95 on Large FFT tests very little RAM and is almost solely CPU.