Running an HP laptop with Win7 for over a year with no problems. Started about a week ago, random BSOD all with similar errors. Tried running Kapersky's rootkit, and Malwarebytes. Have both ZoneAlarm and AVG running. Even tried Win7 Repair command prompt "bootrec /fixmbr"and "bootrec /fixboot" with no positive results. Really stumped now....please help!

You ran TDSSKiller?

Yes, I did run the TDSSKiller from Kapersky. I thought the problem was with the ataport.sys file and I even removed the hard drive, and using an external USB drive adapter, on another laptop running the same version of Win7, I tried to rename ataport.sys to ataport.sy_ in an effort to replace this file. I got a message was that I was not permitted to do that (which is really strange), even though I could copy and rename the same file on the Win7 system that was running. I then booted the infected laptop with an Ubuntu CD. I was then able to rename and replace ataport.sys with the file from the unaffected laptop. Still get the same BSOD's.

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible. If you are overclocking STOP You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking. Please follow these instructions to collect data from the crashes and upload them here, to your Skydrive or a file sharing service like Rapidshare. http://www.sysnative.com/forums/showthread.php/68-Blue-Screen-of-Death-%28BSOD%29-Posting-Instructions-Windows-8-7-amp-Vista?p=303&viewfull=1#post303 http://sysnative.com/0x8/BSOD_Windows7_Vista_v2.64_jcgriff2_.exe To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure: * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine. * Zip up the contents of that folder Please upload them to skydrive or a file sharing service and put a link to them in your next post. Please also go to start>search/run>cmd>msinfo32 and include it in the upload To ensure minidumps are enabled: * Go to Start, in the Search Box type: sysdm.cpl, press Enter. * Under the Advanced tab, click on the Startup and Recovery Settings... button. * Ensure that Automatically restart is unchecked. * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies). * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump. * OK your way out. * Reboot if changes have been made. http://www.sysnative.com/forums/showthread.php/325-BSODs-but-no-Dump-Files http://www.osronline.com/article.cfm?article=545 Please also go to start>run>msinfo32 and save the results. Upload it with the DMP files, thanks. MS-MVP 2010, 2011, 2012 Sysnative.com Team ZigZag

Thank you for helping me! Followed the instructions and here is the zipped files. http://sdrv.ms/Nr5TkL Mike

Mike There are many things going on here. All of which can be solved. First Literally all of these crashes were related to your MBAM and Zone alarm is contributing. I would remove and replace BOTH with MSE and the win 7 firewall AT LEAST TO TEST. http://www.microsoft.com/security_essentials/ They are all c00000005 (which is a memory exception. Usually that is either RAM or more frequently a driver. Your second issue is really ancient drivers from as far back as 2002 that absolutely must be updated. Especially Aspi32.SYS Aspi32.SYS 5/6/2002 12:43:02 PM ghpciscan.sys 12/16/2003 10:41:37 PM mdmxsdk.sys 6/19/2006 5:26:59 PM HpqKbFiltr.sys 6/18/2007 6:12:03 PM SynTP.sys 4/17/2008 8:15:05 PM IntcHdmi.sys 6/30/2008 8:52:24 AM LMIRfsDriver.sys 7/14/2008 12:26:22 PM CHDRT32.sys 10/3/2008 2:39:26 PM HSX_CNXT.sys 2/13/2009 4:57:25 PM HSXHWAZL.sys 2/13/2009 4:58:15 PM HSX_DPV.sys 2/13/2009 5:00:17 PM Rt86win7.sys 2/26/2009 5:04:22 AM XAudio32.sys 4/29/2009 2:20:55 PM spldr.sys 5/11/2009 12:13:47 PM RtsUStor.sys 6/4/2009 4:45:47 AM 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 http://www.carrona.org/dvrref.php http://sysnative.com/drivers/ - - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.htm Now if you continue to crash we can identify any additions source by running these to tests. These crashes were caused by memory corruption c00000005(probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem. *Dont forget to upload any further DMP files (especially those when verifier is running) *If you are overclocking anything reset to default before running these tests. In other words STOP!!! If you dont know what this means you probably arent 1-Memtest. *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org *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. 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. *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. *Further Reading "http://support.microsoft.com/kb/244617" Using Driver Verifier to identify issues with Windows drivers for advanced users MS-MVP 2010, 2011, 2012 Sysnative.com Team ZigZag

Mike There are many things going on here. All of which can be solved. First Literally all of these crashes were related to your MBAM and Zone alarm is contributing. I would remove and replace BOTH with MSE and the win 7 firewall AT LEAST TO TEST. http://www.microsoft.com/security_essentials/ They are all c00000005 (which is a memory exception. Usually that is either RAM or more frequently a driver. Your second issue is really ancient drivers from as far back as 2002 that absolutely must be updated. Especially Aspi32.SYS Aspi32.SYS 5/6/2002 12:43:02 PM ghpciscan.sys 12/16/2003 10:41:37 PM mdmxsdk.sys 6/19/2006 5:26:59 PM HpqKbFiltr.sys 6/18/2007 6:12:03 PM SynTP.sys 4/17/2008 8:15:05 PM IntcHdmi.sys 6/30/2008 8:52:24 AM LMIRfsDriver.sys 7/14/2008 12:26:22 PM CHDRT32.sys 10/3/2008 2:39:26 PM HSX_CNXT.sys 2/13/2009 4:57:25 PM HSXHWAZL.sys 2/13/2009 4:58:15 PM HSX_DPV.sys 2/13/2009 5:00:17 PM Rt86win7.sys 2/26/2009 5:04:22 AM XAudio32.sys 4/29/2009 2:20:55 PM spldr.sys 5/11/2009 12:13:47 PM RtsUStor.sys 6/4/2009 4:45:47 AM 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 http://www.carrona.org/dvrref.php http://sysnative.com/drivers/ - - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.htm Now if you continue to crash we can identify any additions source by running these to tests. These crashes were caused by memory corruption c00000005(probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem. *Dont forget to upload any further DMP files (especially those when verifier is running) *If you are overclocking anything reset to default before running these tests. In other words STOP!!! If you dont know what this means you probably arent 1-Memtest. *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org *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. 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. *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. *Further Reading "http://support.microsoft.com/kb/244617" Using Driver Verifier to identify issues with Windows drivers for advanced users MS-MVP 2010, 2011, 2012 Sysnative.com Team ZigZag

Hello, I am not able to download the dumps. However, I would recommend proceeding like that: Update all possible driversUninstall all unused programsRun chkdsk /r /f and sfc /scannowPerform a clean boot: http://support.microsoft.com/kb/929135Disable temporary all security softwares you haveRun memtest86+ to check your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support for assistance Once done, check again. You can also contact Microsoft CSS for assistance. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer