Crashes during various PC actions.

Great. We can rule out RAM now as a cause as after 11 passes I'm sure something would have been picked up if there were issues.

Lets see if we can find out if there is a driver issue:

• 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
    
  • 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.
  
  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.

Then upload the dumps following the https://www.sevenforums.com/crashes-d...tructions.html.

If you have any questions, feel free to ask
Stephen

I set up Driver Verifier and so far no crashes for the past 4 hrs trying everything that crashed before. Either that fix you posted earlier with the usb worked or my computer isn't co-opperating. I'll run it some more and try to see if we get a crash.

Ok then. Dave knows more about RAM than I do so here is my suggested plan of action.

Continue running driver verifier for up to 12 hours. If no crashes happen during the 12 hours, disable verifier and report back.

Once that is complete, run memtest again. As Dave pointed out, the first two tests sort-of failed so we cannot be sure the RAM is stable. Download a fresh ISO file and burn it on to a fresh CD. Run memtest for each stick of RAM, i.e, remove all but one stick for each test. Once all the ram modules are tested separately report back.

Stephen

Got a bsod with driver verifier on going to try to get a few more then if thats inconclusive run memtest again individually.

Once you've got 2-4 crashes with verifier, upload the dumps here before doing anything else. I'll see what driver is causing the crashes, if any.

Stephen

The program still isnt grabbing the .dmp files so I'll upload C:\Windows\MEMORY.DMP to filesonic and hopefully that'll work.

karlsnooks said:

I use a binary method of locating offending dirver(s).
Cut the number of drivers checked off in half.
Keep the half that causes the problem and just keep halving to you locate an offending driver.
After updating that driver, then I repeat the process is case there is more than one offending driver.
Slow method and not as quick as analysis of a dmp file, but the procedure works for me.

I also recommend using NirSoft's DriverView: Loaded Windows Drivers List

The output is very thorough and allows sorting on various fields. My top choice is to sort with the oldest files listed first. Quite often you will find that a fundamental chip driver for the motherboard is out-of-date.

That's a good method to follow when the BSOD's aren't creating minidumps. However, if they are, just upload the dumps following the posting instructions. Then I can debug them.

Regarding Driver View, it's a useful program but thanks to the fantastic worn of Writhziden, I now have a custom made tool for doing that and more. It's stills useful program however.

So, Salamandrex, what I want you to do us wait until you get a few more crashes with Driver Verifier enabled. Then disable verifier and follow the posting instructions to upload the dumps. I'll then analyse them and post back. Then you can either update the offending driver or run some more hardware checks.

Stephen