new install of win7 x64 various random bsods

Hello,
I have been having some issues with my new install of win7. A few days ago I used a win7 upgrade disk to install win7 from xp. All was fine at first until I started installing all my software and drivers. I started getting BSODs related to my graphics driver, which I actually had to roll back to a later version (apparently the newest version of CCC is bugged). I was getting the bsod error associated with atikmdag.sys. once I rolled the driver back to an older version I thought the bsods stopped but instead I started getting 0x0000001E errors, and then today I have had three bsods, one IRQL Not Less or Equal, and one related to USBPort.sys, and one I forgot to write down I think it was 0x00000024. I have already run memtest86+ overnight and it passed just fine. I also checked the integrity of my hard disks using the manufacturers programs and they were fine (the HD my OS is installed on is approximately 4 years old). I have been getting the bsods while at and away from the computer, regardless of if anything else is running. on a side not my firefox has been crashing even after I disabled all the plugins, and MS Security Essentials has been constantly stopping even after I reinstalled both both programs. I don't know if these are in any way related or not. Thank you very much for the help. I have attached my zipped dmp files.


p.s. my display drivers just stopped...Im thinking these may still need to be uninstalled and rolled back to an even later version.

Gopher42 said:

Hello,
I have been having some issues with my new install of win7. A few days ago I used a win7 upgrade disk to install win7 from xp. All was fine at first until I started installing all my software and drivers. I started getting BSODs related to my graphics driver, which I actually had to roll back to a later version (apparently the newest version of CCC is bugged). I was getting the bsod error associated with atikmdag.sys. once I rolled the driver back to an older version I thought the bsods stopped but instead I started getting 0x0000001E errors, and then today I have had three bsods, one IRQL Not Less or Equal, and one related to USBPort.sys, and one I forgot to write down I think it was 0x00000024. I have already run memtest86+ overnight and it passed just fine. I also checked the integrity of my hard disks using the manufacturers programs and they were fine (the HD my OS is installed on is approximately 4 years old). I have been getting the bsods while at and away from the computer, regardless of if anything else is running. on a side not my firefox has been crashing even after I disabled all the plugins, and MS Security Essentials has been constantly stopping even after I reinstalled both both programs. I don't know if these are in any way related or not. Thank you very much for the help. I have attached my zipped dmp files.


p.s. my display drivers just stopped...Im thinking these may still need to be uninstalled and rolled back to an even later version.

The most recent are related to USBPORT.sys as you stated. I suspect a driver (possibly your 2 year old raid driver).

To confirm which driver please run driver verifier.

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

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.

I did the procedure for the driver verifier and I have attached another copy of the dmp files. I wasn't sure how to visualize the fault otherwise. I actually updated the raid drivers after it went bsod with the driver verifier. please let me know which driver is causing my issue or if I need to provide any other information. Thank you so very very much. also I assume that I will need to do something to stop the driver verifier? i have found that my system is hanging a fair bit especially when starting firefox.

So I am still having issues and I just got a new BSOD. The newest one was Memory_Management. I will attach my DMP files again. I am also needing help in figuring out the driver verifier and how to know which drivers are causing my problems (never used the software before). Thank you again for any help. It is greatly appreciated.

I could really use any more info on these BSODs Please. Or if there is any other data that is needed from me, just let me know. Thanks.

Gopher42 said:

So I am still having issues and I just got a new BSOD. The newest one was Memory_Management. I will attach my DMP files again. I am also needing help in figuring out the driver verifier and how to know which drivers are causing my problems (never used the software before). Thank you again for any help. It is greatly appreciated.

According to your driver verified DMP the file causing it can either be a Microsoft Security essential file or malware dependent on where it is located.

Please download Malwarebytes and run it, and llok for the file in the snip and see where it is located.

Malwarebytes Anti-Malware - Free software downloads and software reviews - CNET Download.com

I ran malwarebytes. If MSE is installed, than it BSODs before it can complete a scan. for it to complete a scan MSE has to either not be installed, or if windows is in safe mode. when MBAM runs it finds one file repeatedly even after quarantining and deleting said file. this file keeps coming back after each restart. I don't know if it is a false pos, or if it is actually something that needs to be taken care of. I couldn't find anything online about this file. the file in question is below.


c:\Windows\winsxs\amd64_microsoft-windows-wininit_31bf3856ad364e35_6.1.7600.16385_none_8ce7aa761e01ad49\wininit.exe (Trojan.FakeMS) -> Quarantined and deleted successfully.

Gopher42 said:

I ran malwarebytes. If MSE is installed, than it BSODs before it can complete a scan. for it to complete a scan MSE has to either not be installed, or if windows is in safe mode. when MBAM runs it finds one file repeatedly even after quarantining and deleting said file. this file keeps coming back after each restart. I don't know if it is a false pos, or if it is actually something that needs to be taken care of. I couldn't find anything online about this file. the file in question is below.


c:\Windows\winsxs\amd64_microsoft-windows-wininit_31bf3856ad364e35_6.1.7600.16385_none_8ce7aa761e01ad49\wininit.exe (Trojan.FakeMS) -> Quarantined and deleted successfully.

Where is msseces.exe located?

it is located in C:\Program Files\Microsoft Security Client

Gopher42 said:

it is located in C:\Program Files\Microsoft Security Client

Good that is the correct location for the client file. So probably not malware.

Since that malware re-emerges on boot I would suspect you have malware that Malwarebytes cant fis (ie something in MBR perhaps.). If I were you I would start a new thread in the security section where some of our malware experts can see it.