BSOD or RESTART randomly, new memory,hard drive, and OS

got a bsod that was actually logged:

i got it while verifier was running, i enabled that simulation option you did not require to enable, you said it does bring the bsod's faster though.... @zigzag

francoisdupie said:

got a bsod that was actually logged:

Finally driver verified and Related to a smserial.sys Motorola SM56 Modem WDM Driver Yours is almost 4 years old. I would update to one dated after July 2009, re-install this driver if there are no newer or remove it.

Hey zigzag, I couldn't find smserial.sys, so I went to device manager and checked the modem files there's, there was 2. So I placed the 1 on my desktop removing it from the system32 driver folder. The other one was moden.sys, I can't do anything with it, it tells me "you need permission from trusted installer". So I left it there. Is the smserial.sys file anywhere specific? I then started fsx again and still got a reboot, with no bsod or minidump written.

... can any one maybe tell me where to find the smserial.sys file?

francoisdupie said:

... can any one maybe tell me where to find the smserial.sys file?

Motorola, or your computer mfr.

hey all, new minidump, got it this morning again

The crash indicates a hard disk related problem. Check for data corruption, bad sectors, faulty hardware, Windows corruption, and viruses.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run the short and long tests with SeaTools.
  SeaTools for Windows
  
  SeaTools for DOS
  
  
• Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.
  
  
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the Good and Free system security combination. for better security steps and scanning tools. Make sure to update the security software before running the full scan.