Windows 7 Blue Screen, error: ataport.sys

Original title: ataport.sys windows 7 bsod
ive been frequented by the ataport.sys bsod, and also some other bsods with little to no mention to what is causing them. my minidumps are uploaded here . please help!!! this has made school so much harder!!!!!!!
 
Question Info

Last updated July 12, 2018 Views 48,223 Applies to:
Answer
Hi,

In those minidumps there were 8 different Bug_Checks 0A (21), 1E (4), 24, 3B (7), 50,
7F, D1 (17), F7 (2).

All minidumps checked DumpCHK and BlueSceenView, and the last 10 with WinDBG.

When there are that many different Bug_Checks its best to take a broad bases
approach.

Use the methods such as SFC, CheckDisk, Driver Updates, and others in the troubleshooter referred
to in this link as they will help solve or at least narrow down the issues. After those you can post the
information from BlueScreenView and these other utilities so we can offer more specific advice. Of
course checking with a real computer shop or System Maker's Support would be a good idea however
I would try the possible solutions you can first.

Check this thread for information using BlueScreenView, MyEventViewer and other methods
to troubleshoot BlueScreens - top 3 replies (+1 other).

http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/c675b7b8-795f-474d-a1c4-6b77b3fcd990

-------------------------------------------------------------------------

Also do this so you can see the likely bluescreens.

Windows Vista automatically restarts if your PC encounters an error that causes it to crash.
(also Windows 7)
http://www.winvistatips.com/disable-automatic-restart-t84.html

===========================================================

BCCode: 0A     0x0000000A


Check these KB's

Error message on a blue screen on a computer that is running Windows 7 or Windows Server
2008 R2: "STOP: 0x0000000A"
http://support.microsoft.com/kb/979444

Stop error message on a computer that is running Windows 7 or Windows Server 2008 R2 and
that has iSCSI storage: "0x0000000A"
http://support.microsoft.com/kb/979711

Those and 5 other KB Articles are available
http://support.microsoft.com/search/default.aspx?mode=a&query=0x0000000A&spid=14019&catalog=LCID%3D1033&1033comm=1&res=10

-----------------------------------

Drivers could be at fault however disk issues or antivirus/antispyware/security products are
just as likely to be the root cause as they can force a driver to corrupt or go out of bounds.
The video driver or something affecting it would be very suspect.

Be sure the drivers, BIOS, and low level chipset drivers are all updated by manually checking
at the System maker and device makers's sites.

Below I will post a generic bluescreen troubleshooter and in the next message how to update
drivers and BIOS as well as do memory checks.

-----------------------------------

BCCode: 0A     0x0000000A

Cause

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

Resolving the Problem

If a kernel debugger is available, obtain a stack trace.

To resolve an error caused by a faulty device driver, system service, or BIOS

  1. Restart your computer.
  2. Press F8 at the character-based menu that displays the operating system choices.
  3. Select the Last Known Good Configuration option from the Windows Advanced Options menu. This option is most effective when only one driver or service is added at a time.

 

To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool

  1. Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
  2. Try disabling memory caching of the BIOS.
  3. Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.
  4. Make sure the latest Service Pack is installed.
  5. If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination.
  6. For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/subordinate/stand-alone setting. Try removing all IDE devices except for hard disks.

 If the message appears during an installation of Windows, make sure that the computer and all installed peripherals are listed in the Microsoft Windows Marketplace Tested Products List.

Comments

Before upgrading to a new version of Windows, remove all third-party device drivers and system services, and disable any virus scanners. Contact the software manufacturers to obtain updates of these third-party tools.

BCCode: 0A     0x0000000A  <-- read this link
http://www.faultwire.com/solutions-fatal_error/IRQL-NOT-LESS-OR-EQUAL-0x0000000A-*1025.html

==================================================================

BCCode: 1E   0x0000001E 

Remove ALL power and reseat all the cards, memory, and cables (both ends when
possible)
- actually remove and replace - do not just snug. Those are for a PC and about all
that can be done for a laptop is reseat the memory and clear the vents. Make sure the BIOS,
low level chipset drivers, and major device drivers are all up to date by check manually at the
makers' sites.

Many Bluescreens are caused by BIOS, low level chipset drivers, and other major device drivers
which are not the most current even though the computer is new. Check manually for updates
using the methods for updates as indicated in the troubleshooter linked above and/or the methods
below (which are the same).

BCCode: 1E   0x0000001E  <-- read this link
http://www.faultwire.com/solutions-fatal_error/Check-to-be-sure-you-have-adequate-disk-space-0x0000001E-*1045.html?order=date

---------------------------------------------------------------------------------------------

Driver Verifier can help find some BSOD issues :

Using Driver Verifier to identify issues with Windows drivers for advanced users
http://support.microsoft.com/kb/244617

How To Troubleshoot Driver Problems in Windows Vista or 7.
http://www.winvistaclub.com/t79.html

Using Driver Verifier
http://msdn.microsoft.com/en-us/library/ff554113(v=VS.85).aspx

How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issueshttp://www.youtube.com/watch?v=_VwIDD9xngM

Driver Verifier
http://www.techsupportforum.com/2110308-post3.html

Using Driver Verifier
http://www.faultwire.com/solutions/using_driver_verifier.php

How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issueshttp://www.youtube.com/watch?v=_VwIDD9xngM

You can disable Driver Verifier
http://support.microsoft.com/kb/244617

Start - type in Search box -> verifier /reset      hit enter to disable

==================================================================

BCCode: 24    0x00000024

Remove ALL power and reseat the cards, memory, and cables (on both ends when possible)
- actually remove and replace - do not just snug.

The primary cause of this Bug_Check is disk issues however it can be caused by memory problems
and even antivirus/antispyware/security programs.

-----------------------------------

BCCode: 24      0x00000024

Cause

One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.

Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

Resolving the Problem

To debug this problem: Use the .cxr (Display Context Record) command with Parameter 3, and then use the kb (Display Stack Trace) command.

To resolve a disk corruption problem: Check Event Viewer for error messages from SCSI and FASTFAT (System Log) or Autochk (Application Log) that might help pinpoint the device or driver that is causing the error. Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system. You should also run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer. RunChkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.

To resolve a nonpaged pool memory depletion problem: Either add new physical memory to the computer (thus increasing the quantity of nonpaged pool memory available to the kernel), or reduce the number of files on the Services for Macintosh (SFM) volume.

BCCode: 24      0x00000024  <-- read this link
http://www.faultwire.com/solutions-fatal_error/NTFS-FILE-SYSTEM-0x00000024-*1051.html?order=votes

=============================================================

BCCode: 3B    0x0000003B

Try removing and reseating all cards, memory, and cables (both ends when possible) - actually
remove and replace - do not just snug (on a PC) and clean out the dust bunnies and vents. On
a laptop about all that can be done is reseat the memory and clean the vents.

3b is usually a graphic's driver (display adapter/video driver), other possibilities include
but are not limited to antivirus/antispyware/security programs and even memory (mapping).

BCCode: 3b    0x0000003b

Cause

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.


BCCode: 3b    0x0000003b  <-- read this link
http://www.faultwire.com/solutions-fatal_error/SYSTEM-SERVICE-EXCEPTION-0x0000003B-*1074.html

============================================================

BCCode: 50    0x00000050

References to Vista also apply to Windows 7.

Have you added any hardware lately? Have you updated any driver just before these started? (Check
Control Panel - Windows Updates to see if any drivers were updated there about the time this started)
Main likely culprits are Video driver, other major drivers, memory, and antivirus/antispyware/security
products could be at fault as well as drive issues.

Use the troubleshooter below and refer to the next message for drivers and memory when you get to
those sections and then return back to the troubleshooter as needed.


BCCode: 50     0x00000050

Cause

The BCCode 50 usually occurs after the installation of faulty hardware or in the event of failure of installed
hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

Resolving the Problem

Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see
if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run
hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's
manual for your computer.

Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so,
contact the manufacturer of the system service about a possible update. If the error occurs during system
startup, restart your computer, and press F8 at the character-mode menu that displays the operating system
choices. At the resulting Windows Advanced Options menu, choose theLast Known Good Configuration
option. This option is most effective when only one driver or service is added at a time.

Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it
does, contact the manufacturer of the program about a possible update.

Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must
restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for
problems between the SCSI controller and the disk.

Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the
device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it.

BCCode: 50      0x00000050  <-- read this link

http://www.faultwire.com/solutions-fatal_error/PAGE-FAULT-IN-NONPAGED-AREA-0x00000050-*1095.html?order=votes

================================================================

BCCode: 7f 0x0000007f with the 00000008 parameter usually means a hardware issue.

Have you added hardware or updated drivers recently? Check Control Panel - Windows
Updates to see if any drivers have been updated there just before this started happening.

For 7f - this could be a hardware issue such as poorly seated cards or memory, though there are
other causes. Weak powersupply could also lead to this. Use the troubleshooters above and below
and when you get to the  drivers and memory sections refer to my next message below and then
return to the troubleshooters if needed

If a PC remove ALL power. Open case, remove and reseat ALL cards, memory chips, and ALL
cables (do not just try to snug) on both ends if they can be reached and on the device ends if not
(removing the cables and reseating them helps to eliminate minor corrosion).

Notice the 08 (double fault) as 1st parameter means there are likely two causes. Be sure to Update
your drivers manually as using Windows Updates only finds certified drivers and Microsoft and
the Device makers are far behind in that proces. Update NIC, WiFi, BIOS and Video/Display and
other major drivers

If a Laptop or a PC you might have to take to a shop (not BestBuy or other BigBox Stores) or your
System maker's Support.

----------------------------------------------------------------------

BCCode: 7F   0x0000007F  which is the same as 0x1000007F

The UNEXPECTED_KERNEL_MODE_TRAP bug check has a value of 0x0000007F. This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

This trap could be a bound trap (a trap the kernel is not permitted to catch) or adouble fault(a fault that occurred while processing an earlier fault, which always results in a system failure).

Parameters

The first parameter that appears on the blue screen specifies the trap number.

The most common trap codes include the following:

  • 0x00000000, or Divide by Zero Error, indicates that a DIV instruction is executed and the divisor is zero. Memory corruption, other hardware problems, or software failures can cause this error.
  • 0x00000004, or Overflow, occurs when the processor executes a call to an interrupt handler when the overflow (OF) flag is set.
  • 0x00000005, or Bounds Check Fault, indicates that the processor, while executing a BOUND instruction, finds that the operand exceeds the specified limits. A BOUND instruction ensures that a signed array index is within a certain range.
  • 0x00000006, or Invalid Opcode, indicates that the processor tries to execute an invalid instruction. This error typically occurs when the instruction pointer has become corrupted and is pointing to the wrong location. The most common cause of this error is hardware memory corruption.
  • 0x00000008, or Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault


CAUSE

Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.

A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same stack. For example, if two file system filter drivers are attached to the same stack and then the file system recurses back in, the stack overflows.

Resolving the Problem

Troubleshooting: If you recently added hardware to the computer, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. Run hardware diagnostics that the system manufacturer supplies to determine which hardware component failed.

The memory scanner is especially important. Faulty or mismatched memory can cause this bug check. For more informaiton about these procedures, see the owner's manual for your computer. Check that all adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean.

If the error appears on a newly installed system, check the availability of updates for the BIOS, the SCSI controller, or network cards. These kind of updates are typically available on the Web site or BBS of the hardware manufacturer.

Confirm that all hard disk drives, hard disk controllers, and SCSI adapters are listed in the Microsoft Windows Marketplace Tested Products List.

If the error occurred after the installation of a new or updated device driver, you should remove or replace the driver. If, under this circumstance, the error occurs during the startup sequence and the system partition is formatted with NTFS, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you have to start the computer by using the Recovery Console in order to access the file.

Also restart your computer, and then press F8 at the character-based menu that displays the operating system choices. At theAdvanced Options menu, select theLast Known Good Configuration option. This option is most effective when you add only one driver or service at a time.

Overclocking (setting the CPU to run at speeds above the rated specification) can cause this error. If you have overclocked the computer that is experiencing the error, return the CPU to the default clock speed setting.

Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing the error. You can also disable memory caching of the BIOS to try to resolve the problem.

If you encountered this error while upgrading to a new version of the Windows operating system, the error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. If possible, remove all third-party device drivers and system services and disable any virus scanners before you upgrade. Contact the software manufacturer to obtain updates of these tools. Also make sure that you have installed the latest Windows Service Pack.

Finally, if all the above steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can also cause this error.


BCCode: 7F   0x0000007F  which is the same as 0x1000007F  <-- read this link
http://www.faultwire.com/solutions-fatal_error/Run-a-system-diagnostic-utility-supplied-by-your-0x1000007F-*1304.html

=================================================================

BCCode: D1     0x000000D1

Check these KB's

Stop error when you resume a computer that is running Windows 7 or Windows Server 2008 R2
from sleep or from hibernation: "STOP: 0x000000D1"
http://support.microsoft.com/kb/978982

Stop error on a Windows Server 2008 R2-based or Windows 7-based computer when the operating
system uses a virtual storport miniport driver to save a dump file or a hibernation file: "0x000000D1"
http://support.microsoft.com/kb/2320550

Those and 7 other KB Articles are available
http://support.microsoft.com/search/default.aspx?mode=a&query=0x000000D1&spid=14019&catalog=LCID%3D1033&1033comm=1&res=10

--------------------------------------------------

Think Video drivers mainly though it can be others. See the driver section in my generic bluescreen
troubleshooting methods below. BIOS, low level chipset drivers and antivirus/antispyway/security
programs can also cause this. Check the troubleshooter and when you get to the driver and memory testing sections refer to the generic methods in next message and then return to the troubleshooter
if needed.


Cause

A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high.

This bug check is usually caused by drivers that have used improper addresses.

If the first parameter has the same value as the fourth parameter, and the third parameter indicates an execute operation, this bug check was likely caused by a driver that was trying to execute code when the code itself was paged out. Possible causes for the page fault include the following:

  • The function was marked as pageable and was running at an elevated IRQL (which includes obtaining a lock).
  • The function call was made to a function in another driver, and that driver was unloaded.
  • The function was called by using a function pointer that was an invalid pointer.

BCCode: d1   0x000000d1  <-- read this link
http://www.faultwire.com/solutions-fatal_error/DRIVER-IRQL-NOT-LESS-OR-EQUAL-0x000000D1-*1210.html?order=votes

================================================================

BCCode: F7     0x000000F7

The DRIVER_OVERRAN_STACK_BUFFER bug check has a value of 0x000000F7. This indicates that a driver has overrun a stack-based buffer.

Important Information If You Have Received a STOP Code

If you have received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact information for Microsoft or your computer manufacturer Contact Support.

If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article Resolving STOP (Blue Screen) Errors in Windows.

The following actions might prevent an error like this from happening again:

  1. Download and install updates and device drivers for your computer from Windows Update.
  2. Scan your computer for computer viruses.
  3. Check your hard disk for errors.

Cause

A driver overran a stack-based buffer (or local variable) in a way that would have overwritten the function's return address and jumped back to an arbitrary address when the function returned.

This is the classic "buffer overrun" hacking attack. The system has been brought down to prevent a malicious user from gaining complete control of it.

BCCode: F7    0x000000F7  <-- read this link
http://www.faultwire.com/solutions-fatal_error/A-driver-has-overrun-a-stack-based-buffer-0x000000F7-*1244.html?order=votes

====================================================================

See the top link posted above for methods to troubleshoot BlueScreens.

Hope this helps.

Rob Brown - Microsoft MVP - Windows and Devices for IT 2010 - current
Windows Insider MVP 2016 - current

Did this solve your problem?

Sorry this didn't help.

Answer

Hi,

These are the specific issues which might help :

1. Most of the minidumps referenced CAUSE as Windows components which means something else drove them into Fault.

2. Some of the minidumps referenced MEMORY as possible CAUSE so
thoroughly check it using the methods in the troubleshooting link at the
top of the previous message. (This is not likely to be the only CAUSE.)

3. Several minidumps referenced Daemon Tools and SPTD.sys which
has been known to CAUSE or aggravate issues such as those. Uninstall
DT and disable/remove SPTD.sys. Those can always be re-installed
after the issues are reserved.

4. Several minidumps referenced McAfee which has been known to
CAUSE or aggravate these type of issues. Uninstall McAfee and run
the McAfee Removal Tool to prevent remnants which can cause strange
issues. Below are recommendations to use while testing, even better
permanently.

McAfee Removal Tool
http://service.mcafee.com/FAQDocument.aspx?id=TS100507

=================================

Here is what I use and recommend : (These are all Free versions and very effective.) 

Avast and Prevx have proven extremely reliable and compatible with everything I have
thrown at them. Microsoft Security Essentials and Prevx have also proven to be very
reliable and compatible. Use MSE and Prevx or Avast and Prevx however not all 3.

Avast Home Free - stop any shields you do not need except leave Standard, Web, and
Network running.

Prevx - Home - Free

Windows Firewall

Windows Defender (not needed if using MSE)

IE - Protected Mode

IE 8 - SmartScreen Filter ON  (IE 7 Phishing Filter)

I also have IE to always start with InPrivate Filter active if IE 8.
(You occasionally have to turn it temporarily off with the little Icon on LEFT of the + bottom
right of IE)

Two versions of Avast are available 5.x and 4.8x

Avast 5.x - Home - Free - Stop the Shields you do not use (except File, Web, Network, &
Behavior) - double click the Orange Icon in Notification Area - Real Time Shields - click the
Shield you want to stop - STOP. To stop the Orange Icon from showing an error indicator -
click the Orange Icon - Upper Right - Settings - click Status Bar - uncheck the Shields you
disabled - click OK
http://www.avast.com/free-antivirus-download

Avast 4.8x - Home - Free - stop any shields you do not need except leave Standard, Web,
and Network running. (Double Click Blue icon - details next to OK. - upper left Shields -
Terminate those you do not use.)
http://www.avast.com/free-antivirus-download#tab4

Or use Microsoft Security Essentials - Free
http://www.microsoft.com/Security_Essentials/

Prevx works well along side Avast or MSE

Prevx - Home - Free small, fast, exceptional CLOUD protection, works with other security
programs. This is a scanner only, VERY EFFECTIVE, if it finds something come back here
or use Google to see how to remove. 
http://www.prevx.com/   <-- information
http://info.prevx.com/downloadcsi.asp  <-- download

PCmag - Prevx - Editor'a Choice
http://www.pcmag.com/article2/0,2817,2346862,00.asp

Also get Malwarebytes - free - use as scanner only. If you ever suspect malware, and that
would be unsual with Avast and Prevx running except for an occasional low level cookie
(no big deal), UPDATE it and then run it as a scanner. I have many scanners and they
never find anything of note since I started using this setup.

http://www.malwarebytes.org/

Hope this helps.

Rob Brown - Microsoft MVP - Windows and Devices for IT 2010 - current
Windows Insider MVP 2016 - current

Did this solve your problem?

Sorry this didn't help.