Bsod

Page 3 of 4 FirstFirst 1234 LastLast

  1. Posts : 25
    windows 7 home premium 64bit
    Thread Starter
       #21

    re did the driver got a couple more bsod's
      My Computer


  2. Posts : 1,314
    Windows 7 64-bit
       #22

    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.
      My Computer


  3. Posts : 25
    windows 7 home premium 64bit
    Thread Starter
       #23

    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
      My Computer


  4. Posts : 25
    windows 7 home premium 64bit
    Thread Starter
       #24

    i was running prime95 and i got this
      My Computer


  5. Posts : 2,573
    Win7 Ultimate X64
       #25

    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
      My Computer


  6. Posts : 25
    windows 7 home premium 64bit
    Thread Starter
       #26

    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
    Last edited by cowboy5345; 04 Feb 2013 at 21:10.
      My Computer


  7. Posts : 1,314
    Windows 7 64-bit
       #27

    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.
      My Computer


  8. Posts : 25
    windows 7 home premium 64bit
    Thread Starter
       #28

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


  9. Posts : 25
    windows 7 home premium 64bit
    Thread Starter
       #29

    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?
      My Computer


  10. Posts : 1,314
    Windows 7 64-bit
       #30

    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.
      My Computer


 
Page 3 of 4 FirstFirst 1234 LastLast

Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 22:26.
Find Us