BSOD at random times

I have a program called Advanced systemcare pro 5 I noticed that it happens when you are running a deepscan and then you go to internet explorer. It also happens at other times such as when the desktop is not doing anything also when playing games some times. The screen turns blue then restarts. If yall could help that would be wonderful thanks all!

Is Windows 7 . . .
- x64
- the original installed OS on the system? Windows 7
- an OEM or full retail version? OEM
- What is the age of system (hardware)? 1 Year
- What is the age of OS installation? About 2 months

Attachment 193564

There are a few issues here. I am going to deal with a few and my partner JMH will do the others

First. You have a 2003 BIOS that cant possibly work correctly in win 7.

It needs to b e updated to newest.

Before updating your BIOS be sure to make a backup (just in case)

Code:

BIOS64.sys    6/7/2003 7:12:00 PM  

Code:

      
Lachesis.sys    8/17/2007 2:48:44 AM           
BS_I2cIo.sys    6/16/2008 1:45:18 AM                           
ElRawDsk.sys    7/26/2008 12:59:09 PM                   
BS_TPIO64.sys    4/29/2009 10:17:44 PM                           

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads


My partner will deal with the memory exception seen in your BSOD'S.

Follow zigzag's advice then read below...

These crashes were caused by memory exception (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.

RAM - Test with Memtest86+



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.

Driver Verifier - Enable and Disable


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


*** I note you also use Advanced system Care pro 5.
We don't recommend this as it is NOT necessary on Windows 7 & can do more harm that good.
Would suggest you remove same.

I went into my bios and it says 2010 I dont understand where the 2003 one came from.
And does advanced system care pro 5 really damage it? because thats mainly when it crashes is when it is doing deep care. Are there any recommended safe optimizers?

Firefox60 said:

I went into my bios and it says 2010 I dont understand where the 2003 one came from.
And does advanced system care pro 5 really damage it? because thats mainly when it crashes is when it is doing deep care. Are there any recommended safe optimizers?

Im not keen on anything IOBIT makes.

The driver is Related to BIOS64.sys I/O Interface driver file from BIOSTAR Group. That is the one from 2003.

We dont recommend "optimizers", or defraggers most of the time as in win 7 they often do more harm than good.

Firefox60 said:

And does advanced system care pro 5 really damage it? because thats mainly when it crashes is when it is doing deep care. Are there any recommended safe optimizers?

Opinions always vary...

Current accepted wisdom with Win 7 is to NOT use a cleaner.

If you ever think your Registry needs to be cleaned, repaired, boosted, tuned-up, cured, tweaked, fixed, or optimized it shouldn't.

In other words, injudicious use of "Registry cleaners" CAN & DOES cause problems.