BSOD shortly after logging in

[R00N]

I'm pretty sure it's a driver issue, ignore the old DMP files this issue has only occurred today. I also got a weird anti-virus message saying that svchost.exe was a virus but that isn't possible as far as I know being that svchost is a system file. I ran a full system scan regardless and nothing has shown up.

Specs: Windows 7 Ultimate 32bit (Retail)
Pentium Dual Core @ 3.0
2GB RAM
ATI 5670
I built this computer myself so I pretty much know everything that has been installed on it. I checked to download history and nothing but a mp3 encoder has been downloaded since yesterday but the problem random started today.

 

[zigzag3143]

SVCHOST is a system file but can also be malware (depending on it location). Just in case

Please download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.

Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!






These crashes were caused by memory corruption/exception (cx05) 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!!!

* If you have raid update its Driver.



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



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.

So, I'd suggest that you first backup your stuff 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).

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 "Special Pool", "Force Pending I/O Requests" and "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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

Old drivers

giveio.sys    4/3/1996 10:33:25 PM        
ATITool.sys    11/10/2006 9:08:51 AM       
Rt86win7.sys    2/26/2009 5:04:22 AM        
GEARAspiWDM.sys    5/18/2009 8:16:53 AM        
LHidFilt.Sys    6/17/2009 12:49:04 PM        
LMouFilt.Sys    6/17/2009 12:49:08 PM       
LUsbFilt.Sys    6/17/2009 12:49:11 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

 

[R00N]

Well I found the problem, it was the giveio.sys driver something to do with speed fan. Fixing it was easy enough, thanks for the help.

 

[zigzag3143]

Well I found the problem, it was the giveio.sys driver something to do with speed fan. Fixing it was easy enough, thanks for the help.

Well I hope that is the problem. Good luck.