Frequent BSOD (like once a day)

Hi,

While searching the Internet for a solution for my problem i found this (good and clear) forum.


What happens:

My pc (laptop Acer Aspire 5741G Windows 7 Home premium 64bits) Started crashing after a major virus, after deleting the virus and scanning my pc the pc started giving BSOD's. It started with one a day then it stopped for 3 weeks and now its back again once a day.

What I have done:

Driver updates (one hell of a job)
Bios Update
found a solution to: LMS service cannot connect to Intel(R) MEI driver I know (a) is my network card. To address (b), I have tried uninstalling and reinstalling the Intel chip set drivers.

But nothing worked,

This is my last hope.

I don't have the time and can't miss my pc for sending it back and letting Acer repair it.

Much Thanks

Tinus Scheppers

Try a SFC scan SFC /SCANNOW Command - System File Checker

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
You can use MagicDisc as an alternative.

Code:

sptd.sys        fffff880`010ac000    fffff880`011d2000    0x00126000    0x4ad24632    12/10/2009 00:55:14

All dumps point to ntoskrnl.exe as the probable cause. We know this is not the case, as this is the core OS file, and will definitely not cause a BSOD. It is just the default file the debuggers blame when they can't see a better cause. We need to run driver verifier to pinpoint the faulting driver...

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

Then upload the new dumps created in C:\Windows\Minidump

Ok, I'll try that and thanks for the fast 'response'!

I did what you discribed but no new dump file was created, But i do have older dump files.

I cant get an dump because my pc needs the 'repair' itself in order to work.
I did manage to make a picture of the BSOD but i guess it wont help much.

Devenda said:

I cant get an dump because my pc needs the 'repair' itself in order to work.
I did manage to make a picture of the BSOD but i guess it wont help much.

Can you boot in safemodw with networking?

yowanvista said:

Devenda said:

I cant get an dump because my pc needs the 'repair' itself in order to work.
I did manage to make a picture of the BSOD but i guess it wont help much.

Can you boot in safemodw with networking?

Yes but there isn't any new dump file created

I guess the dump posted before also contains info of the BSOD.

a shameless BUMP

You may need to do a clean install
Clean Install Windows 7