BSOD help please

my ram has already been tested and has no errors

hi there,

can i have some help with this please?

As mentioned, it could still be memory even if it passed through Memtest86+. Memtest86+ does not stress the memory in the same way Windows does, so it only catches certain ranges of errors. Sometimes, a better check is to run Windows normally with one module in one slot at a time and test each module and each slot.

Before proceeding with the above more time intensive task, we should check software/driver issues.

• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    Attachment 210234
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset
  -> Restart your computer.

hi there,

i will do another memtest and leave it running while i am out at the gym. the only thing with the driver verifier is that the BSOD happens at random times and doens`t happen day in day out can take awhile to get one.

hi there,

i have just ran memtest again and it got to about 15mins in and it came up with 2 errors so i stopped the test.
what does this mean? do i need to try and RMA it to corsair? and how do i do it if i do ?

hello,

just letting you know that i have just tested one stick of ram at a time to see if i could find out which one is faulty, i tested for the same time as i got the last errors which was 20mins in.

both sticks did not have any errors come up. i think the ram i have isn`t compatible with my motherboard set on auto and defult settings. because i am not good at changing bios settings i have put my ols sticks of ram back in for now, untill i get my new asus sabertooth 990fx board when the piledriver comes out.

if i still get the BSOD with my old sticks of ram back in then at least i will know that its either drivers or my motherboard.

Suggestion, do them one at a time until you find the offender. Then put the "good" one in it's place and retest. If it comes back clean, then that should rule out the MoBo. And yes RMA them.

hi,

well i have tested them in both of the motherboard slots that i was using at the time i got the BSOD and there is no errors. i think it is just that my ram is not compatible with my motherboard, i should of looked before buying them really but i didn`t think because i have never bought ram before. i think there are ways around it by changing settings in the bios but i would rather use my old sticks for now untill i get a new motherboard in the summer. if i get anymore BSOD with my old sticks in then i know it must be drivers.

Memory is rather finicky, so errors do not always show up in the same patterns. That is why we recommend running Memtest86+ for at least seven passes. I have seen cases where it took up to 21 passes to get one error and determine RAM was bad. I would recommend testing the RAM modules you have individually for more passes, or test one at a time in one slot at a time by doing your normal routine in Windows. If you do not crash in twice the amount of time it typically takes (on average) for you to get a crash, then the module and slot is probably good.

If you crash, try the module in another slot. If you crash with all slots, the module is likely bad. If you find a good module and slot, test all slots with the good module to make sure you do not have a bad slot. Then test the other modules in the good slot to find any bad modules.


The above is just a suggestion and is completely optional, and you can just run with the old RAM if you like until you get a new board.