BDOS due to ataport.sys - Windows 7 x64

iman

New member
Joined
Jul 16, 2014
Posts
1
Kindly analyse attachments and guide me what needs to be done.

Thanks a lot!


· OS - Windows 8.1, 8, 7, Vista ? Windows 7
· x86 (32-bit) or x64 ? x86
· What was original installed OS on system?
Windows 7
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Retailer
· Age of system (hardware) 5+ years
· Age of OS installation - have you re-installed the OS? 2+ years

· CPU
· Video Card
· MotherBoard
· Power Supply - brand & wattage (if laptop, skip this one)

· System Manufacturer
· Exact model number (if laptop, check label on bottom)

· Laptop or Desktop?
 
Hi,

The attached DMP files are of the KERNEL_DATA_INPAGE_ERROR (7a) bug check.

This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.

Code:
BugCheck 7A, {c044d0c0, [COLOR=#ff0000]c000000e[/COLOR], 43bbd860, 89a189c4}

The 2nd argument is an NTSTATUS, specifcally 0xc000000e which indicates a device which does not exist was specified (i.e your disk which was once detected is now all of a sudden not detected).

Code:
CHKIMG_EXTENSION: !chkimg -lo 50 -d !ataport
    89a18000-89a18091  146 bytes - ataport!DeviceAllocatePdoCallBack+34
    [ 8a 48 01 88 8e 10 03 00:2d 01 1b 01 8c 01 1b 01 ]
    89a18093-89a181ab  281 bytes - ataport!DeviceAllocatePdoCallBack+c7 (+0x93)
    [ 56 e8 bb fa ff ff 3b c3:01 ac 0c 1b 01 ba 0c 1b ]
    89a181ad-89a182b2  262 bytes - ataport!DeviceRemoveDevice+af (+0x11a)
    [ 0a ff 70 14 ff 70 10 e8:35 1b 01 a3 35 1b 01 20 ]
    89a182b4-89a182be  11 bytes - ataport!ChannelFilterResourceRequirements+7c (+0x107)
    [ 00 00 68 49 64 65 50 ff:34 47 1b 01 69 47 1b 01 ]
    89a182c0-89a1838d  206 bytes - ataport!ChannelFilterResourceRequirements+88 (+0x0c)
    [ ff 15 80 12 a1 89 89 45:db 47 1b 01 ed 47 1b 01 ]
    89a1838f-89a18392  4 bytes - ataport!ChannelFilterResourceRequirements+157 (+0xcf)
    [ 4a 14 83 c0:01 e1 61 1b ]
    89a18394-89a184e6  339 bytes - ataport!ChannelFilterResourceRequirements+15c (+0x05)
    [ 13 ce 83 f8 08 75 72 3b:de 63 1b 01 11 64 1b 01 ]
    89a184e8-89a184fe  23 bytes - ataport!ChannelQueryBusRelation+3a (+0x154)
    [ 56 e8 fa b4 ff ff 53 ff:39 95 1b 01 8c 95 1b 01 ]
    89a18500-89a187b2  691 bytes - ataport!ChannelQueryBusRelation+52 (+0x18)
    [ 00 00 75 18 8b 73 60 57:bd 98 1b 01 e1 98 1b 01 ]
    89a187b4-89a187de  43 bytes - ataport!ChannelAddDevice+64 (+0x2b4)
    [ 00 00 57 6a 08 59 68 49:bc fb 1b 01 c3 fb 1b 01 ]
    89a187e0-89a187ed  14 bytes - ataport!ChannelAddDevice+90 (+0x2c)
    [ 00 00 57 53 e8 59 d8 ff:cd fc 1b 01 cf fd 1b 01 ]
    89a187ef-89a187fc  14 bytes - ataport!ChannelAddDevice+9f (+0x0f)
    [ 8d 85 4c ff ff ff 50 57:01 52 ff 1b 01 3d 00 1c ]
    89a187fe-89a188ad  176 bytes - ataport!ChannelAddDevice+ae (+0x0f)
    [ 00 00 00 e8 ec d8 ff ff:1c 01 56 01 1c 01 6c 01 ]
    89a188af-89a1899a  236 bytes - ataport!ChannelAddDevice+15f (+0xb1)
    [ 60 22 a1 89 89 83 44 11:01 c8 11 1c 01 1e 12 1c ]
    89a1899c-89a189f2  87 bytes - ataport!ChannelAddDevice+24c (+0xed)
    [ 00 00 c0 85 ff 74 09 6a:fd 27 1c 01 04 28 1c 01 ]
    89a189f4-89a18a02  15 bytes - ataport!ChannelQueryDeviceRelations+30 (+0x58)
    [ 68 ae 84 a1 89 ff 30 ff:f1 2d 1c 01 ee 2e 1c 01 ]
    89a18a04-89a18bd6  467 bytes - ataport!ChannelQueryDeviceRelations+40 (+0x10)
    [ 00 00 eb 11 fe 42 23 83:7e 2f 1c 01 8e 2f 1c 01 ]
    89a18bd8-89a18c73  156 bytes - ataport!ChannelAllocateProxyPdo+52 (+0x1d4)
    [ 00 00 53 c6 86 10 03 00:48 5b 1c 01 50 5b 1c 01 ]
    89a18c75-89a18c7d  9 bytes - ataport!ChannelValidateAtaMiniportIoctl+b (+0x9d)
    [ 8b 40 0c 56 8b 71 08 83:68 1c 01 c1 68 1c 01 de ]
    89a18c7f-89a18c91  19 bytes - ataport!ChannelValidateAtaMiniportIoctl+15 (+0x0a)
    [ 72 2f 83 38 1c 74 07 b8:01 e3 69 1c 01 6d 6a 1c ]
    89a18c93-89a18c97  5 bytes - ataport!ChannelValidateAtaMiniportIoctl+29 (+0x14)
    [ 83 fa 1c 72 18:01 ac 6b 1c 01 ]
    89a18c99-89a18ca3  11 bytes - ataport!ChannelValidateAtaMiniportIoctl+2f (+0x06)
    [ d0 72 14 39 51 04 73 0b:6c 1c 01 4f 6c 1c 01 ab ]
    89a18ca5-89a18e6c  456 bytes - ataport!ChannelValidateAtaMiniportIoctl+3b (+0x0c)
    [ b8 23 00 00 c0 eb 09 33:6d 1c 01 4b 6d 1c 01 d9 ]
    89a18e6e-89a18fff  402 bytes - ataport!IdeRegMigrateDriverKeys+70 (+0x1c9)
    [ 75 f8 89 75 fc e8 c4 b9:1c 01 c9 89 1c 01 d0 89 ]
[COLOR=#ff0000]4073 errors[/COLOR] : !ataport (89a18000-89a18fff)

Over 4k errors regarding ataport.sys (IDE storage port driver). I took a look at your loaded modules and I see the likely problem, which is you have two security suites installed.



1. Remove and replace avast! and Kaspersky with Microsoft Security Essentials for temporary troubleshooting purposes as they are conflicting and causing file system conflicts:

avast! removal - avast! Uninstall Utility | Download aswClear for avast! Removal

Kaspersky removal - Service articles

MSE - Microsoft Security Essentials - Microsoft Windows

One of the biggest problems as far as antivirus suites go in terms of conflicts, is if there is more than one antivirus or anti-malware suite installed on the system. In the most basic example, I will use avast! Kaspersky . Let's say you have both installed and running, this is not a good scenario at all. Why? Most/if not all modern day antivirus suites are allowed direct access (come and go, whenever they want) to the kernel because an antivirus installs interceptors of system events within the kernel code, which passes intercepted data to the antivirus engine for analysis. This data is network packets, files, and other various critical data.

2. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

3.

Code:
0: kd> lmvm asacpi
start    end        module name
937fe000 937ff420   ASACPI     (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
    Image name: ASACPI.sys
    Timestamp:        Thu Aug 12 22:52:52 [COLOR=#ff0000]2004[/COLOR]

Your Asus ATK0110 ACPI Utility driver is dated from 2004, which is nearly ten years old. All pre-2009 versions of this driver are known to cause massive problems, so please update yours ASAP - http://support.asus.com/download/download.aspx

After following all of the above, your system should work just fine.

Regards,

Patrick
 
Hi -

You likely have a hard drive issue. The dumps list I/O errors.

One dump contained a 0xc000014d exception error, which = STATUS_REGISTRY_IO_FAILED

Another contained:
Code:
ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

Run SeaTools for DOS, LONG test - https://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics.html

Run chkdsk /r

Other items:

Update Asus ATK0110 utility driver. This 2004 version is known to cause BSODs in Windows 7 systems -
Code:
ASACPI.sys   Thu Aug 12 22:52:52 2004 (411C2D04)
http://sysnative.com/drivers/driver.php?id=ASACPI.sys

Remove Kaspersky Internet Security 2012 version - you have Avast installed.

Use the KIS Removal Tool - http://kb.eset.com/esetkb/index?page=content&id=SOLN146

Run the HDD diagnostics first. Be sure to back up important files before running SeaTools.

Regards. . .

jcgriff2
 
No problem, John.

Hard disk issues are a possibility, but with two suites and 10 year old ASACPI driver, I believe that may be our culprit.

Good catch on SP1.

Regards,

Patrick
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top