BSOD randomly (?) When waking laptop after sleeping, BSOD pic attached

[C3H5N3O9]

Is Windows 7 . . .
- x64
- the original installed OS on the system? Windows 7 Ultimate x64
- an OEM or full retail version? Retail

- What is the age of system (hardware)? ~1 year
- What is the age of OS installation (have you re-installed the OS?) ~1 year, I installed it when I got the laptop.

Also, one of my USB ports is not working, it has been like that for a while. The sound jack is also broken i fell on the headphone cord. The sound still works, just have to move it a bit. I'm about to send it in to get the hardware repaired and was hoping I could get an answer here on the BSOD before hand. The laptop is a Sager W860CU. Thanks!

I'm currently scanning with Avast.

I took a picture of the BSOD with my phone. Hopefully you can see all the characters.

Thanks!

C3

 

[zigzag3143]

Is Windows 7 . . .
- x64
- the original installed OS on the system? Windows 7 Ultimate x64
- an OEM or full retail version? Retail

- What is the age of system (hardware)? ~1 year
- What is the age of OS installation (have you re-installed the OS?) ~1 year, I installed it when I got the laptop.

Also, one of my USB ports is not working, it has been like that for a while. The sound jack is also broken i fell on the headphone cord. The sound still works, just have to move it a bit. I'm about to send it in to get the hardware repaired and was hoping I could get an answer here on the BSOD before hand. The laptop is a Sager W860CU. Thanks!

I'm currently scanning with Avast.

I took a picture of the BSOD with my phone. Hopefully you can see all the characters.

Thanks!

C3

Related to a smserial.sys Motorola SM56 Modem WDM Driver. Yours is 3 years old. I would update to most recent.

 

[C3H5N3O9]

Thanks for the quick response! I checked that driver and there were no updates, but since I have no use for a Fax Modem, I uninstalled the driver. I'll report back and see if that fixed it. Thanks!

 

[zigzag3143]

Thanks for the quick response! I checked that driver and there were no updates, but since I have no use for a Fax Modem, I uninstalled the driver. I'll report back and see if that fixed it. Thanks!

Good luck

 

[C3H5N3O9]

Alright, so I left my computer, came back with it sleeping, turned it on and I got a new BSOD. I updated all of the files from the previous zip to include this BSOD. When I turned on the computer, windows loaded and told me that it installed the driver that I just uninstalled. Anyways, all the necessary files should be attached.

Thanks!

C3

 

[zigzag3143]

Alright, so I left my computer, came back with it sleeping, turned it on and I got a new BSOD. I updated all of the files from the previous zip to include this BSOD. When I turned on the computer, windows loaded and told me that it installed the driver that I just uninstalled. Anyways, all the necessary files should be attached.

Thanks!

C3

I just noticed Soluto. Often a cause of BSOD's especially on starting.

 

[C3H5N3O9]

Ok, so I uninstalled Soluto and I still have the BSOD. I downloaded Bluescreenview and took a screenshot. The image is attached.

Also, it's only listing to like 1/10/12 but I got BSOD everyday since too.

Thanks,

C3

 

[zigzag3143]

Ok, so I uninstalled Soluto and I still have the BSOD. I downloaded Bluescreenview and took a screenshot. The image is attached.

Also, it's only listing to like 1/10/12 but I got BSOD everyday since too.

Thanks,

C3

First Blue screen view often incorrectly blames an OS file like it is doing now.

You seem to have two separate sets of issues.

In October you had a series of crashes that were blamed on a driver upsetting the power state.

You seem to have eliminated that and now have a different set blaming a memory exception.



These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[C3H5N3O9]

Ok, I ran the memtest for 7 passes and 15:30 0 errors. Now I then did the driver verifier and my computer hasn't had blue screen... I did restore it the first time but that was only to the past day, when I still had the problem. Now, my computer is going horribly slow, the browser is hanging, I can't download anything without it getting uninterrupted, my intelproset wireless just crashed. I can't get a speedtest.net to run and so on.

I have tried to get it to BSOD since it was doing it every time my computer went to sleep, but now it wakes up.

I did run avast the other day too.

EDIT: I just typed verifier /query into my cmd and it said verifier is not recognized as internal or external cmd....

EDIT2: Should I just backup the files I want and reinstall? It'll be annoying but probably less time than this.

Thanks for the help,

C3