Icezed,
My apology for the delay...did not see your post.
BugCheck Analysis is just not my thing, however, can see how an entry for ataport! leads one to look at atapi.sys Also, atapi.sys has been a common target of the TDSS TDL4 (Alureon) RootKit.
In this particular case,
TDSSKiller, a prime candidate for finding the rootkit and resolving the bluescreen issue, detected nothing, as you mentioned, in both normal and safe mode.
The
Farbar Recovery Scan Tool (FRST), another outstanding tool for detecting RootKits and hard to detect malware, did not identify anything pertinent to ataport or atapi.sys
We can run more tools, like
GMER and
Malwarebytes Anti-Malware, if you wish, but, personally, do not expect these additional tools to find entries related to ATA Port's interface.
The
Additions.txt produced by FRST does show an entry under
Faulty Device Manager Devices, as well as
Event Log errors.
The use of
sxstrace.exe is indicated,
WinMgmt based entries are identified, and, interestingly enough, one of the Event Log errors is:
Error: (07/04/2013 00:46:55 AM) (Source: Microsoft Security Client Setup) (User: Icezed-PC)
Description: HRESULT:0x8004FF66
Description:
Windows did not pass genuine validation....etc.
This is rather unusual for a new computer!
Also, not sure that pursuing all these issues is going to get us ahead...
Was this computer built by someone you paid to do so, or is it a brand name machine that came out of a box? If brand name, can it be restored to factory defaults?
Also see where
Arc suggested to go for a
http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html
Will qualify these comments with the assertion that I am not an expert at anything. Just like bustin' malware.
If someone sees something else here, please jump in!
