BSOD Vista ataport.sys

So I ran computer in safe mode because the normal mode does not work.

Can not turn on microsoft security databases.

The screen displays this error.

STOP: 0X0000008E (0XC000005, 0X85F9EA65)

ataport.sys address 85F9EA65 base at 85f9aooo.

Any help will be apreciated.

Hello

Maybe this might help you:

http://www.pchelpforum.com/win-7-Vista-BSOD/103587-blue-screen-death-ataport-sys.html

Start with your Win Vista DVD and access to the command prompt and type (press enter on each line):

c:
Bootrec /fixmbr
Bootrec /fixboot

LC

Tags: Windows

Similar Questions

  • BSOD Vista KS.sys

    Just started getting the BSOD with the ks.sys BSOD error. I am attaching the .dmp files as I do not understand what is the cause.

    Signature of the problem:
    Problem event name: BlueScreen
    The system version: 6.0.6001.2.1.0.768.3
    Locale ID: 2057
    More information about the problem:
    BCCode: 3B
    BCP1: 00000000C 0000005
    BCP2: FFFFFA600421A0FE
    BCP3: FFFFFA60051F3E40
    BCP4: 0000000000000000
    OS version: 6_0_6001
    Service Pack: 1_0
    Product: 768_1

    Hello AndrewMenzies,

    I took a look in the dump that you file sent and it seems that ks.sys may actually be the victim here.

    Before ks.sys, atihdLH6.sys appears in the stack.  Since it is a minidump, I can't read the dismount, but we generally see a third-party driver sending an invalid parameter to the top of the stack.

    The atihdLH6 driver is fairly new - March 2011.  We check with ATI to see if they have an update for it.  If this isn't the case, then we could revisit the driver that came out before this iteration.

    Here is my analysis of the discharge.  My comments are in "BOLD":

    The mini kernel dump file: only registers and the trace of the stack are available

    Symbol search path is: SRV * c:\websymbols* http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) free x 64
    Product: WinNt, suite: TerminalServer personal TerminalServer
    By: 6001.18538.amd64fre.vistasp1_gdr.101014 - 0432
    Computer name:
    Kernel base = 0xfffff800' 01b 59000 PsLoadedModuleList = 0xfffff800'01e1edb0
    The debugging session: 11:43:14.656 Wed Jul 20 2011 (UTC - 05:00)
    System Uptime: 0 days 0:00:23.825

    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    Use! analyze - v to obtain detailed debugging information.

    Bugcheck 3B {c0000005, fffffa600421a0fe, fffffa60051f3e40, 0}

    Probably caused by: ks.sys (ks! KspPinPropertyHandler + 17 (a)<-- debugger="" blames="" ks.sys-="" but="" it="" looks="" like="" it="">
    Follow-up: MachineOwner actually the victim here.
    ---------

    2: kd >! analyze - v
    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    System_service_exception (3B)<-- stop="" code="" and="">
    An exception occurred during the execution of a system service routine.
    Arguments:
    Arg1: 00000000c 0000005, Exception that caused the error checking code
    Arg2: fffffa600421a0fe, the address of the instruction that caused the error checking
    Arg3: fffffa60051f3e40, address of the context record to the exception that caused the error checking
    Arg4: 0000000000000000, zero.

    Debugging information:
    ------------------

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - the instruction at 0 x % lx 08 referenced memory at 0 x % 08 lx. The memory could not be %s.

    FAULTING_IP:
    Msg KspPinPropertyHandler + 17
    fffffa60'0421a0fe 448b0a mov r9d, dword ptr [rdx]<-- this="" could="" very="" well="" be="" from="" a="" bad="" parameter="" that="">
    CONTEXT: fffffa60051f3e40-(.cxr 0xfffffa60051f3e40) spent on top of the stack.
    Rax = fffffa80071324e8 rbx = 0000000000000000 rcx = 0000000000000000
    RDX = 0000000000000000 rsi = rdi fffffa80071322b0 = 0000000000000008
    RIP = fffffa600421a0fe rsp = fffffa60051f46a0 rbp = 0000000000000001
    R8 = 0000000000000001 r9 = 0000000000000002 r10 = fffff8800096e140
    R11 = 00000000fffffff8 r12 = r13 0000000000000008 = fffff8800096e140
    R14 = 00000000ffffffff r15 = 0000000000000001
    iopl = 0 nv in pe of na EI pl nz nc
    CS = 0010 ss = 0018 ds = 002 b're = 002 b fs = 0053 gs = 002 b efl = 00010202
    MSG KspPinPropertyHandler + 0x17a:
    fffffa60'0421a0fe 448b0a mov r9d, dword ptr [rdx] b ds:002: 00000000'00000000 =?
    Reset the default scope

    2: kd > .cxr 0xfffffa60051f3e40<-- getting="" context="">
    Rax = fffffa80071324e8 rbx = 0000000000000000 rcx = 0000000000000000
    RDX = 0000000000000000 rsi = rdi fffffa80071322b0 = 0000000000000008
    RIP = fffffa600421a0fe rsp = fffffa60051f46a0 rbp = 0000000000000001
    R8 = 0000000000000001 r9 = 0000000000000002 r10 = fffff8800096e140
    R11 = 00000000fffffff8 r12 = r13 0000000000000008 = fffff8800096e140
    R14 = 00000000ffffffff r15 = 0000000000000001
    iopl = 0 nv in pe of na EI pl nz nc
    CS = 0010 ss = 0018 ds = 002 b're = 002 b fs = 0053 gs = 002 b efl = 00010202
    MSG KspPinPropertyHandler + 0x17a:
    fffffa60'0421a0fe 448b0a mov r9d, dword ptr [rdx] b ds:002: 00000000'00000000 =?
    2: kd > kv
    Resets to the last context set-.thread/.cxr stack trace it
    Child-SP RetAddr: Args to child: call Site
    "fffffa60 '051f46a0 fffffa60' 0422001b: fffffa80 '071322b 0 fffffa80 ' 07189460 fffffa80' 071322b 0 fffff880 ' 009a 8880: ks! KspPinPropertyHandler + 0x17a
    "fffffa60 '051f46f0 fffffa60' 042f4f32: 00000000' 7070534b fffffa80 ' 07189460 fffff880 ' 009a57e0 00000000'00000020: ks! KsPinPropertyHandler + 0x1b
    fffffa60 '051f4730 fffffa60' 042172ab: fffffa80 '071322b 0 fffffa80' 066f53f0 00000000'00000000 00000000'00000003: portcls! PcPinPropertyHandler + 0 x 152
    fffffa60 '051f4770 fffffa60' 0422059b: 00000000 '00000000 fffff880' fffffa60 00000003 '051f4880 fffff880' 009a8ab0: ks. KspPropertyHandler + 0x6cb
    fffffa60 '051f47d0 fffffa60' 042f5904: fffffa60 ' 051f4880 fffff880 '009a8ab0 fffffa80' 071322b 0 fffffa80 ' 0675dcc0: ks. KsPropertyHandler + 0x1b
    "fffffa60'051f4820 fffffa60'0430869 c: 00000000 ' 00000001 fffffa80 ' 071322b 0 fffffa80 '066f5540 fffffa60' 042d90cb: portcls! PcHandlePropertyWithTable + 0 x 64
    fffffa60 '051f4850 fffffa60' 042f4b01: fffffa80 ' 071322b 0 fffffa80 '066f53f0 fffffa80' 066f5540 fffffa60 ' 051f4a88: portcls! CPortFilterWaveRT::DeviceIoControl + 0 x 144
    fffffa60'051f48b0 fffffa60'042176 8 d: 00000000' c000000d fffffa80 '071324e8 fffffa80' 066f53f0 00000000'60000000: portcls! DispatchDeviceIoControl + 0 x 79
    fffffa60 '051f48e0 fffffa60' 042f406c: fffffa60'051f4a18 11cf51ad '134960 0000 8 c 101' 00000001 f8948a87 c' 00000003: ks! KsDispatchIrp + 0xd8
    fffffa60'051f4910 fffffa60'042 d 3765: 00000000 ' 00000001 fffffa80' 07132530 fffffa60 '051f4a00 fffffa60' 04336a 87: portcls! PcDispatchIrp + 0x5c

    "fffffa60'051f4940 00000000 00000001': fffffa80 ' 07132530 '051f4a00 fffffa60' fffffa60 04336a 87 fffffa80 ' 071322b 0: AtihdLH6 + 0x1b765<-- 3rd="" party="">

    fffffa60'051f4948 fffffa80'07132530: fffffa60'051f4a00 fffffa60 '04336-87 fffffa80' 071322b 0 00000000 00000000': 0 x 1
    fffffa60 '051f4950 fffffa60' 051f4a00: fffffa60'04336 has 87 fffffa80 '071322b 0 00000000 00000000' fffffa80' 0675dcc0: 0xfffffa80'07132530
    fffffa60 '051f4958 fffffa60' 04336a 87: fffffa80' 071322b 0 00000000 00000000' fffffa80 '0675dcc0 fffffa80' 071322b 0: 0xfffffa60'051f4a00
    "" fffffa60 '051f4960 fffffa60' 043367dd: 00000000 ' 00000001 fffffa80 ' 071324e8 fffffa80 ' 07132530 fffffa80 ' 071322b 0: ksthunk! CKSThunkDevice::DispatchIoctl + 0xcf
    fffffa60 '051f4990 fffff800' 01f31a6a: fffffa80 '0675dcc0 fffffa60' 051f4ca0 00000000'00000000 00000000'00000001: ksthunk! CKernelFilterDevice::DispatchIrp + 0x11d
    fffffa60 '051f49f0 fffff800' 01f4a966: fffffa80'06e87c10 00000000'00000000 00000000'00000000 00000000'00000000: nt! IopXxxControlFile + 0x5da
    fffffa60 '051f4b40 fffff800' 01cadeb3: fffff880'0aea91e0 fffffa80 '06ebd700 00000000'00000300 fffff800' 01f2a634: nt! NtDeviceIoControlFile + 0 x 56
    fffffa60 '051f4bb0 00000000' 7739507a: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiSystemServiceCopyEnd + 0 x 13 (TrapFrame @ fffffa60'051f4c20)
    00000000' 0160f3a8 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: 0x7739507a
    2: kd > lmvm AtihdLH6
    start end module name
    fffffa60'042 b 8000 fffffa60'042 d 8000 AtihdLH6 T (no symbol)
    Loaded symbol image file: AtihdLH6.sys
    Image path: \SystemRoot\system32\drivers\AtihdLH6.sys
    Image name: AtihdLH6.sys
    Timestamp: Kills Mar 31 02:15:13 2011 (4D942A01)<-- driver="" is="" fairly="" new. ="" we="" should="" check="" for="" an="" update="" for="" it="" or="" revert="" to="" earlier="">

    Let us know if you have any questions.

    Best regards

    Matthew_Ha

  • Windows 7 bugcheck 0 x 00000027 - ataport.sys

    Hello

    I have a freshly built PC Windows 7 Professional, who runs since October 2010 with no new software installed and all the latest updates installed Windows.  This PC will act as the Golden Image PC for all future installations of PC.  Friday the PC has been issued to a member of staff as the first person to use the new configuration of the OS, well!  However the staff member who reported when she returned to her PC once it has rebooted automatically and when she opened a session it displays a message on Windows stops unexpectedly.  Never during the time that I built this PC had no BSOD.

    I checked the event log and the PC suffered a BSOD, so I ran the Windows Dumpcheck on the PC tool and identified the shutdown was caused by an accident about ataport.sys.  I ran the TSSDKiller tool to make sure that the PC has not received a kit of root infection, it's clean.

    I do not know where to go from here, and any advice would be appreciated as to what are the common causes of this error.  The screenshot of the properties real crash dump are as follows:

    The minidump files showed a stop RDR_FILE_SYSTEM error (27) referencing the rdbss.sys:

    BUCKET_ID: X64_0x27_rdbss! RxUpdateFobxPowerState + ef

    endpointservice.exe (Bitdefender process) was the process that crashed, but the problem may be with the rdbss.sys himself.

    The first minidump file showed that the same mistake took place on October 16, 2014.

    The mistake was almost identical to what has been reported in the following link:

    http://windowsforum.com/threads/BSOD-0x-27-Rdbss-sys.88939/

    From this link the only similarity in the drivers, that I could see was the Realtek Lan driver (Rt64win7.sys) so I recommend you to update this driver:

    http://www.Realtek.com.tw/downloads/downloadsView.aspx?langid=1&PNid=13&pfid=5&level=5&Conn=4&DownTypeID=3&GETDOWN=false#1

    If the error persists, or you can do now is install the following hotfix:

    http://support.Microsoft.com/kb/2732673

    There is a link at the top of the article to request the hotfix.

    This hotfix includes the following hotfix that may apply in your situation, which is a fix for the Rdbss.sys:

    http://support.Microsoft.com/kb/2839149

  • Receiver ataport.sys blue screen with windows 7.

    original title: reception ataport.sys bsod with windows 7.

    help someone? I have here minidumps

    There is a lot of confusion about this blue screen virus and how to get rid of.  This virus is in the root of the system, which is what makes it difficult because usually anti-virus programs that either do not offer the option scan the root or you need to tell him to do. As long as you use your computer, at least in Safe Mode, go to Kaspersky.com and download their RootKiller. Run a scan and if it works for you, pass it.  No need to analyze the minidumps, etc..

  • BSOD (DRIVER_IRQL_NOT_LESS_OR_EQUAL igdkmd64.sys)

    Hi, I am facing the problem of BSOD - DRIVER_IRQL_NOT_LESS_OR_EQUAL igdkmd64.sys on my laptop (HP ENVY 15-j126tx)

    OS: Windows 8.1

    Intel HD Graphics 4600 with the version of the driver 10.18.10.3277

    I try updating the driver, but the problem doesn't seem to be resolved. I also try to restore the pilot but after cancellation, I have been unable to adapt to my screen resolution and brightness (I'm not sure he always get BSOD DNon).

    What should I do to fix this?

    I hope that it was able to solve this problem with the resolution of the screen and able to adjust brightness.

    Thank you.

    Can be resolved by updating the driver manually by using the Device Manager.

  • Need help with BSOD PAGE_FAULT_IN_NONPAGED_AREA win32k.sys

    Hello

    How it started:

    I turned on my com and the screen was obscured for a few minutes, I force shut it down by pressing the start on my laptop and tried to back button - turn on the laptop, and it came on the screen

    Which was posted on the bsod:

    Win32k.sys

    PAGE_FAULT_IN_NONPAGED_AREA

    Technical information:

    STOP: 0 X 00000050 (0XFFFFF901C06729B4, 0 X 0000000000000000, 0XFFFF9600006CCA3, 0 X 0000000000000005)

    win32K.sys - address FFFFF9600006CCA3 base at FFFFF96000000000, Datestamp 53c5df64

    It's probably something that I installed, however I have not installed any new devices to my com, what I did was clean by removing unwanted programs (Non-windows) and clean my com through defragmentation and free disk space.

    I can't seem to find a solution on the forum who can solve my problem, I restarted my com and tried to start in safe mode, safe mode with network, safe mode with command prompt all brings back me to the BSOD. Most assistance in the forum would require me to start working on Windows, but I'm unable to access the windows because regardless of the command I run the com will return to the BSOD. Then I tried pressing F8 startup and select "System, restoration" and by running the backup, the computor invites you to me, ' the selected backup could not be found. System Restore is looking for a restore point that is located on your backup. Choose a different restore point. "I tried to run the backup of all and the same mistake has been invited.

    Finally, I did a system recovery Image so I can't use any device to restore the computor to previous state, while it was working fine.

    Any help is appreciated, thanks for reading.

    Hello

    Thanks for the reply.

    For you to get the dump files the computer should start first and then only you can provide us with the dump files.

    I suggest you follow the steps in the link below.

    http://Windows.Microsoft.com/en-us/Windows7/resolving-stop-blue-screen-errors-in-Windows-7#section_2

    Note: Please ignore the steps under System Restore and reinstall Windows 7.

  • System interupts causing the high CPU usage, possibly ataport.sys

    I have worked on this for a month now and have had no luck looking in other posts. Interrupts system uses a core of my 100% computer. I ran windows performance monitor and it seems to be caused by ataport.sys. The problem happens periodically and will last for a few hours and then disappear. I did a full AVG and Malwarebytes full scan. I tried to update all my drivers. I don't know what else to do.

    Thanks in advance

    The problem occurred, so I think it's fixed, it for 36 hours.

    First my problem (high utilization of the processor system interruptions) occurred only when there was a large amount of disk use, for example when copying the files, open a program or running a program that accesses the floppy disk a lot at run time, such as a virus scan.

    Here's what I did, but I don't know exactly which corrects the problem.

    I downloaded and ran Auslogics Registry Defragmenter-Auslogics Registry cleaner and Disk Defragmenter Auslogics. When you run Disk Defragmenter, I chose the option to move the files to the front of the drive system and ran the defragmentation and the optimizer, as opposed to only the defragmentation.

    So I ran Chkdsk using the administrator following command command prompt: Chkdsk /f /r: C

    After the words, I downloaded Seatools from Seagate and ran long Fix All option on my hard drive.

  • How can I fix my windows32\drivers\ataport.sys

    I can start my computer normally but when I try to run the bases of microsoft scanner works too high a few minutes and then a blue screen appears and tells my ataport.sys does not work and stops. I can't run my security or the necessary critical update

    Hi Matthew,

    1. have you made changes on the computer before this problem?

    2 is the issue limited while performing the update Windows and running Microsoft Essentials?

    Windows operating system provides the port driver ATA (Ataport.sys), a port driver storage which is particularly suitable for use with the IDE controllers.

    Usually, this can happen due to a driver issue or a rootkit malware.

    I suggest you to provide us with the Mini Dump files to get a better understanding of the issue.

    Follow the steps to copy the contents of the minidump files:

    (a) copy the contents of \Windows\Minidump to another (temporary) location or anywhere on your machine.

    (b) zip copy.

    (c) attach ZIP archive to your message by using the button (attachments) "trombone".

    (d) please upload them to a service like Skydrive file sharing.

    You can view the following link to find out how to send the files minidump using Skydrive:

    http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

    Refer to the steps in the following Microsoft article and check.

    Resolve stop (blue screen) errors in Windows 7:http://windows.microsoft.com/en-US/windows7/Resolving-stop-blue-screen-errors-in-Windows-7

    Notes:

    Running chkdsk on the drive if bad sectors are found on the disk hard when chkdsk attempts to repair this area if all available on which data can be lost.

    When you perform the system restore to restore the computer to a previous state, programs and updates that you have installed are removed.

    Before you perform the upgrade on the spot, I would recommend you to back your files using windows backup.

    Keep us informed on the status of the issue.

  • BSOD on startup Vista crcdisk.sys

    Hello.
    I just installed Vista SP2.

    Rebooted and everything went well.

    I've also updated my BIOS of motherboard (Intel G35EC) to its latest version.
    At the next restart I got BSOD, and the system restarted before I could read anything.

    I tried 'Safe Mode'. It loads the files, and then gets the file: crcdisk.sys crashes for a few seconds and then restarts.
    I tried to change the settings for the SATA controller to IDE emulation still with no success.

    What could be? How I can fix?

    Thank you.

    Uh, did him updated BIOS might have something to do with it?
    He has clearly stated that it has installed SP2, rebooted and everything was fine, then it has updated its BIOS and now he has problems.

    Thank you

  • BSOD Vista caused by Ntkrnlpa.exe Ntfs.Sys, random hal.dll, etc..

    A friend of mine gave me this computer about 2 or 3 months without a hard drive, thanks to a little research because I am not a professional of any kind, I knew that, because of the lack of a disk hard computer did not have an operating system. Having had an old computer just sitting with a 60 GB hard drive I connected on the computer I have now. After buying a new installation of Windows Vista Service Pack 2 disc, just well installed on the hard drive (which has been formatted to remove the old operating system, and all other things potentially buggy) and the computer has given new life. Following these time immediately, I downloaded and installed Microsoft security Essentials to protect my computer and a few other things to Rainmeter, steam, and that's it. Not even which in fact through the first day, however it has begun its random cycle without blue screening end who, after looking hard and troubleshooting, I've yet to find a solution for. Especially, it occurs whenever trying to read a chart highlighting / demanding the game, but also random triggers when nothing works and it's just sitting here. Ironically, I am writing this issue on the same computer in the hope I can find a fix to the Microsoft community.

    He still run Windows Vista Service Pack 2 (32-bit) and my computer is a PC of Compaq Presario SR5710Y so that you know what the material consists of.

    Here's my last 4 crashes

    Mini042815 - 04.dmp 28/04/2015-18:59:23 0x864e3aa8 0x8471ad78 0x000000e3 RESOURCE_NOT_OWNED 0x00000000 0 x 00000002 Ntfs.sys Ntfs.sys + 12012 NT File System Driver

    Mini042815 - 03.dmp 28/04/2015-18:23:07 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0 x 00000004 0x00000002 0 x 00000000 0x822d9abf ntkrnlpa.exe ntkrnlpa.exe + 4de7d NT Kernel & System

    Mini042815 - 02.dmp 28/04/2015-18:14:28 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0x006301be 0x00000002 0 x 00000001 0x822dab50 ntkrnlpa.exe ntkrnlpa.exe + 4de7d NT Kernel & System

    Mini042815 - 01.dmp 0x0000001a MEMORY_MANAGEMENT 15/04/2015-18:12:40 x 0 00005003 0xc0802000 00000197 0 x 0 x 77635101 hal.dll hal.dll + 770c Hardware Abstraction Layer DLL

    DJ

    If he continued to hang after re-installing windows, but before installing other programs, there is probably material.  I'd start with memtest

    2-Memtest. (You can learn more about running memtest here)

  • Win 7 64 random BSOD (nvlddmkm.sys, ataport.sys, dxgmms1.sys)

    Looking for help to detect which continues, started getting random BSOD for the last weeks of both systems has been stable for months at 100%.  Nothing has changed hardware wise over the last 9 months, software wise, I updated my video card drivers.  I've since gone back to the old drivers video and am still getting the BSOD.  Any help would be appreciated, thanks.

    Mini dump files

    GR

    Verified and associated avc3.sys driver driver filter Active Virus Control of BitDefender STROKE.  I remove it and use MSE in its place

    http://www.Microsoft.com/security_essentials/

  • Need to atapi.sys and ataport.sys solve corruption in Windows Vista

    How can I find these files?  Anyone can provide for me?  They are not on the CD/DVD I have.

    1 repair indicates that 2 files are corrupt.

    2. don't know if this applies.

    I was able to find the files in the incentive off another PC with Vista.  Reinstall the device driver is not possible if the PC will not boot into the operating system.  Because they are system files I don't know if they are organized by the suppliers of specific device or if it is the only creation of Microsofts.  Copy the 2 files using the repair console was able to put me into the BONE without any additional problems.

  • IRQL_NOT_LESS_OR_EQUAL BSOD Vista

    I have a Vista computer and get the BSOD, and then stops. It happens in safe mode as well

    Here is some information I found in the dump file

    Ntkrnlpa.exe ntkrnlpa.exe + 2b83c 0x81c12000 0x81fcc000 0x003ba000 0x513a901f 08/03/2013 9:27:59 PM system Microsoft® Windows® NT Kernel operating system & 5.1.2600.6368 (xpsp_sp3_gdr.130307 - 0422) Microsoft Corporation C:\WINDOWS\system32\ntkrnlpa.exe
    RASPPTP.sys raspptp.sys + cc84 x 0 82397000 0x823ab000 0 x 00014000 0 x 47919112 01/19/2008 1:56:34 AM Microsoft® Windows® Operating System - to - Peer Tunneling Protocol 5.1.2600.5512 (xpsp.080413 - 0852) Microsoft Corporation C:\WINDOWS\system32\drivers\raspptp.sys

    Tracy

    These have been associated with raspptp.sys - to-Peer Tunneling Protocol of Microsoft Corporation, but the underlying cause is Symantec I think.  I would like to remove and replace with MSE

    Symantec is a common cause of BSOD.


    I remove and replace it with Microsoft Security Essentials at LEAST FOR TESTER
    http://us.Norton.com/support/kb/web_view.jsp?wv_type=public_web&docURL=20080710133834EN
  • BSOD Vista - stop 0x7F {8, 801fd000, 0, 0}

    Yesterday, my computer vista laptop just crashed twice.  First time it was just hung up and I had to do a cold reboot.  Second time, he gave me a BSOD.  I ran WinDbg with analyze - v command.  Here is the result.  Thanks in advance for your help

    Debug version of Microsoft Windows (R) 6.12.0002.633 X 86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading dump file [C:\Windows\MEMORY. DMP]
    The core dump file summary: the single kernel address space is available

    WARNING: A space at the end of the trace element
    Symbol search path is: SRV * c:\websymbols* http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack2) MP (2 processors) free x 86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    By: 6002.18327.x86fre.vistasp2_gdr.101014 - 0432
    Computer name:
    Kernel base = 0x88a48000 PsLoadedModuleList = 0x88b5fc70
    The debugging session: 14:28:43.605 Wednesday, August 31, 2011 (UTC - 07:00)
    System Uptime: 0 days 3:17:16.142
    WARNING: Directory of process 00118520 base Table does not match CR3 00122000
    WARNING: Directory of process 00118520 base Table does not match CR3 00122000
    Loading the kernel symbols
    ...............................................................
    ................................................................
    ........................................................
    Loading user symbols
    PEB is paginated on (Peb.Ldr = 7ffd300c).  Type ".hh dbgerr001" for more details
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    Use! analyze - v to obtain detailed debugging information.

    Bugcheck 7F, {8, 801fd000, 0, 0}

    ERROR: Module load completed but symbols can be loaded for tmlwf.sys
    ERROR: Module load completed but symbols can be loaded for dne2000.sys
    ERROR: Module load completed but symbols can be loaded for IPSECDRV.sys
    Probably caused by: NETIO. SYS (NETIO! CompareSecurityContexts + 47)

    Follow-up: MachineOwner
    ---------

    0: kd >! analyze - v
    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means an interruption occurred in kernel mode, and it's a trick of nature
    that the kernel is not allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first digit of the
    bugcheck params is the number of the trap (8 = double fault, etc.)
    Consult an Intel x 86 family manual to learn more about what these
    traps are. Here's a * part * of these codes:
    If kv shows a taskGate
    Use .tss on the part before the sign colon, then kv.
    Otherwise, if kv shows a trapframe
    use .trap on that value
    On the other
    . Trap on the appropriate frame will show where the trap was taken
    (on x 86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    Ko poster then the battery has been corrected.
    Arguments:
    Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 801fd000
    Arg3: 00000000
    Arg4: 00000000

    Debugging information:
    ------------------

    BUGCHECK_STR: 0x7f_8

    TSS: 00000028--(.tss 0 x 28)
    EAX = d498d1a8 ebx = 00000000 ecx = d498d0fc edx = 8ce93594 esi = d498d278 edi = 00000001
    EIP = 88af7058 esp = d498d000 ebp = d498d018 iopl = 0 nv up ei pl zr pe nc
    CS = 0008 ss = 0010 ds = 0023're = 0023 fs = 0030 gs = 0000 efl = 00010246
    NT! SepSidInTokenSidHash + 0 x 2:
    88af7058 push ebp 55
    Reset the default scope

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    Nom_processus: TmProxy.exe

    CURRENT_IRQL: 2

    LAST_CONTROL_TRANSFER: from 88af704c to 88af7058

    STACK_TEXT:
    d498cffc 88af704c 00000000 00000000 00000000 nt! SepSidInTokenSidHash + 0x2
    d498d018 88af6e56 00000000 00000000 00000000 nt! SepSidInToken + 0 x 29
    d498d044 88af6a97 00000001 d498d1a8 d498d1a8 nt! SepNormalAccessCheck + 0x6c
    d498d0ec 88af614b 8ce93570 00000000 00000000 nt! SepAccessCheck + 0x1f7
    d498d148 88 has 89328 8ce93500 d498d198 00000001 nt! SeAccessCheck + 0x1a4
    d498d584 90daecc6 8ce93570 80fae7dc 00000000 nt! SeAccessCheckFromState + 0xe4
    d498d5c4 90daed08 8ce93568 8ce93558 00000000 NETIO! CompareSecurityContexts + 0 x 47
    d498d5e8 90dad2e6 8ce93560 00000000 d498d890 NETIO! MatchValues + 0xee
    d498d600 90dad8e5 8ce93558 d498d890 8cedc4c8 NETIO! MatchCondition + 0x4b
    d498d61c 90dad879 d498d96c 00000000 d498d7d0 NETIO! FilterMatch + 0 x 49
    d498d640 90dad7ba 8b7971b0 d498d96c d498d7d0 NETIO! IndexListClassify + 0 x 25
    d498d680 90dad4d8 d498d96c 00000001 d498d7d0 NETIO! FindMatchingEntries + 0xd6
    d498d75c 90e771de d498d96c d498d7d0 NETIO 0000002 c! KfdClassify + 0 x 145
    d498d784 90e79f6a d498d96c d498d7d0 8d6aa2b8 tcpip! WfpAleClassify + 0 x 36
    d498d9e4 90e79675 8cc0bd60 0000002c 90ec039c tcpip! WfpAlepAuthorizeReceive + 0x6a9
    d498db54 90e77434 8cc0bd60 00000002 00000011 tcpip! WfpAleAuthorizeReceive + 0x2fb
    d498dbc8 90e76861 8cc0bd60 00000002 00000011 tcpip! WfpAleConnectAcceptIndicate + 0xb5
    d498dc38 90e7814f d498dcf0 00000011 00000002 tcpip! ProcessALEForTransportPacket + 0xf3
    d498dce8 90e77d30 8cc0bd60 d498dfa8 00000011 tcpip! ProcessAleForNonTcpIn + 0xa1
    d498dfb4 90e78470 00000002 00000011 000032f4 tcpip! WfpProcessInTransportStackIndication + 0 x 436
    d498e008 90e786e2 8cc0bd60 00000002 00000011 tcpip! InetInspectReceiveDatagram + 0xce
    d498e08c 90e78d6d 8cb848c0 8cc1ebe0 00000000 tcpip! UdpBeginMessageIndication + 0 x 33
    d498e0d4 90e7424e 8cb848c0 8cc1ebe0 00000000 tcpip! UdpDeliverDatagrams + 0 x 108
    d498e120 90e7429b 8cb848c0 00b 78000 d498e15c tcpip! UdpReceiveDatagrams + 0 x 112
    d498e130 90e73a8b d498e144 c000023e 00000000 tcpip! UdpNlClientReceiveDatagrams + 0x12
    d498e15c 90e734b8 90ecb048 d498e1b0 c000023e tcpip! IppDeliverListToProtocol + 0 x 49
    d498e17c 90e73908 90ecacd0 d498e1b0 00000011 tcpip! IppProcessDeliverList + 0x2a
    d498e1d4 90e75120 90ecacd0 00000000 00000011 tcpip! IppReceiveHeaderBatch + 0x1eb
    d498e264 90e71628 998f7860 88b2b801 00000000 tcpip! IpFlcReceivePackets + 0xbe1
    d498e2e0 90e70f39 999d 2920 8d6aa2b8 00000000 tcpip! FlpReceiveNonPreValidatedNetBufferListChain + 0x6e3
    d498e308 90d430b0 999d 2920 8d6aa2b8 00000000 tcpip! FlReceiveNetBufferListChain + 0 x 104
    d498e33c 90d35d25 00ab6240 8d6aa2b8 00000000 ndis! ndisMIndicateNetBufferListsToOpen + 0xab
    d498e364 90d35c9c 8bdb7098 00000000 99a62e08 ndis! ndisIndicateSortedNetBufferLists + 0x4a
    d498e4e0 90c7657f 00000000 00000000 ndis 8e6ad0e8! ndisMDispatchReceiveNetBufferLists + 0 x 129
    d498e4fc 90ca1ccd 8e6ad0e8 8d6aa2b8 00000000 ndis! ndisMTopReceiveNetBufferLists + 0x2c
    d498e518 90ca1ca4 99ab4c10 8d6aa2b8 00000000 ndis! ndisFilterIndicateReceiveNetBufferLists + 0x20
    d498e534 895daaa3 99ab4c10 8d6aa2b8 00000000 ndis! NdisFIndicateReceiveNetBufferLists + 0x1b
    WARNING: Information not available stack unwind. Sequence of images may be wrong.
    d498e560 895dacd8 8d6aa2b8 0098e57c tmlwf 00000040 + 0x2aa3
    d498e580 895e0ffc c9668008 8d6aa340 00000000 tmlwf + 0x2cd8
    d498e5a0 895e23dc c9668008 8d6aa340 8d6aa340 tmlwf + 0x8ffc
    d498e69c c9668008 00000001 8e6ad0e8 tmlwf 895d9e05 + 0xa3dc
    d498e6c8 90d482ba 99a62e08 00000000 00000000 tmlwf + 0x1e05
    d498e714 90d42ba0 026ad0e8 d498e758 00000001 ndis! ndisMIndicatePacketsToNetBufferLists + 0xe9
    d498e750 90d68bfc 8c0f4eb0 999050ac 974f5ab0 ndis! ndisLWM5IndicateReceive + 0x31d
    d498e774 897e822a 8e629b30 999050ac 974f5ab0 ndis! EthIndicateReceive + 0x1f
    d498e7f8 897e2392 999050ac 977f18e0 974f5ab0 dne2000 + 0x1822a
    d498e850 974e8611 977f18e0 90800550 977ad4d0 dne2000 + 0 x 12392
    d498e8a8 974dafd3 90800550 8e395f90 8b 978808 IPSECDRV + 0 x 14611
    d498e8e8 974de8bb 8dbee288 d498e90c 0000020d IPSECDRV + 0x6fd3
    00000000 00000000 00000000 00000000 00000000 IPSECDRV + 0XA8BB

    STACK_COMMAND: .tss 0 x 28; Ko

    FOLLOWUP_IP:
    NETIO! CompareSecurityContexts + 47
    90daecc6 84 0 test al, al

    SYMBOL_STACK_INDEX: 6

    SYMBOL_NAME: NETIO! CompareSecurityContexts + 47

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: NETIO

    NOM_IMAGE: NETIO. SYS

    DEBUG_FLR_IMAGE_TIMESTAMP: 49e0209d

    FAILURE_BUCKET_ID: 0x7f_8_NETIO! CompareSecurityContexts + 47

    BUCKET_ID: 0x7f_8_NETIO! CompareSecurityContexts + 47

    Follow-up: MachineOwner

    Hello

    Results verified BlueScreenView WinDBG / DumpCHK.

    The Bug_Check were the two 7F with the 08 parameter. One of the CAUSES was netio.sys who
    is a Windows component that means something different it led in error. The other CAUSE
    a e1e5132e.sys which is the Intel (r) PRO/1000 adapter.

    Bugcheck 7F, {8, 80050031, 6f8, fffffadf279af77f}
    Probably caused by: e1e5132e.sys (e1e5132e + b77f)
    SYMBOL_NAME: e1e5132e + b77f
    MODULE_NAME: e1e5132e
    Nom_image: e1e5132e.sys
    FAILURE_BUCKET_ID: X64_0x7f_8_e1e5132e + b77f
    BUCKET_ID: X64_0x7f_8_e1e5132e + b77f

    e1e5132e.sys dated 26/03/2010.

    Loaded symbol image file: e1e5132e.sys
    Image path: \SystemRoot\system32\DRIVERS\e1e5132e.sys
    Image name: e1e5132e.sys
    Timestamp: Thu Mar 26 00:49:43 2010 (4BAC6717)

    1. check with BOTH HP Support, their drivers and documentation online and ask the HP
    forums for known issues. After you have installed the latest drivers from HP THEN check with Intel for
    more recent versions.

    Support HP & drivers
    http://welcome.HP.com/country/us/en/support.html

    Contact HP
    http://welcome.HP.com/country/us/en/contact_us.html

    HP forums
    http://h30434.www3.HP.com/PSG/

    For the Intel driver update utility<-- run="" this="" after="" checking="" with="">
    http://www.Intel.com/p/en_US/support/detect?redirector_count=1&

    Intel Download Center
    http://Downloadcenter.Intel.com/

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

    2 check the updates to the BIOS, drivers from the chipset level low and other main device drivers.
    Use the methods in the above troubleshooting utility to update the drivers. Run DriverView - set
    SEE drivers to hide Microsoft - update those without drain on their behalf.

    BiosReleaseDate = 2008-06-16<-- low="" level="" chipset="" drivers="" are="" probably="" also="" this="">
    SystemManufacturer = Hewlett-Packard
    SystemProductName = HP Pavilion dv9700 Notebook PC
    Family = 103C_5335KV
    SystemVersion = Rev 1
    SystemSKU = GP235AV
    BaseBoardManufacturer = Quanta
    -------------------------------

    3 AVG and ZoneAlarm might easily be involved in the issue.

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

    4. don't forget the 08 setting means it is probably more than a cause - a
    or more which can be hardware.

    --------------------------------
    5 use the methods in the troubleshooters above.

    I hope this helps.

    Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle="" -="" mark="" twain="" said="" it="">

  • The update of Windows 10 1511 reboot loop Bootcamp BSOD ACPI. SYS

    It is a copy of my thread to http://answers.microsoft.com/en-us/windows/forum/windows_10-performance/windows-10-update-1511-reboot-loop-bootcamp/8653... as I was asked to post here by the Microsoft Support Engineer.

    Hello

    Friday night, I went to bed with a working machine. I had a late 2013 Mac Pro BootCamp running with a Windows 10 Pro installed, the Build version before 1511.

    On Saturday morning, I woke up to my PC restart itself over and over again. It seems that Windows Update has decided to put a new version of Windows 10 on my machine without my knowledge. I discovered this after restoring an acronis backup (which took a few hours because of the number of incremental backups)

    Occasionally (about 1 in 20 restarts) it would blue screen with an error:

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (ACPI.sys)

    But the rest of the time he would just start, flash a window for a millisecond that says (I think) winlaunch.exe, then restart.

    I tried a lot of things to sort it, including:

    (1) restore from a backup, acronis to Friday morning, running sfc/scannow, and then runs the update

    (2) the creation of a recovery USB, enter the console, change the boot to legacy method, so I can F8, then goes into all security modes and mode of illegal product, but I can find where windows 10 now puts the boot log

    (3) restored from acronis, switched to mac, created a new bootcamp drivers usb, switched to windows and run the option 'fix drivers' before performing the update.

    Ntbtlog.txt is not anywhere on the partition. I ran a dir /s > a.txt then open this a.txt in Notepad and searched him.

    I don't know where to go from here. I can acronis restore of a windows 10 work machine the morning before installing mandatory 1511. I don't know how to delay the update no more, I noted during a restore I had delay on updates that are why it has arisen just now.

    I do not know how to find where this BSOD ACPI.sys will come (even if it happens so rarely) or this that its trying to load just before it crashes (so I can try to delete the driver etc. by the front restored windows to upgrade)

    I guess the widowed causes 10 to do a restore, then the restore fails.

    Overall, I get at the end of my wits with this, to go a completely Windows 10 installation work Friday to more than two wasted days, restore backups, try again, rinse and repeat. It's now Monday morning and I am posting this as a ditch last attempt to solve the problem, your help would be appreciated.

    If you need more information please let me know the location of the files, etc, or their names and I will do my best to have copies available for you.

    I will now restore the backup again, uninstall loading of drivers, and then try the update of windows for the 4th or 5th time.

    Thanks in advance,

    Julian

    Woo Hoo, I've solved the problem!

    I uninstalled the drivers of graphics from AMD (with AMD Driver Cleaner) and Arcronis True Image Home 2013 at the same time, then let Windows Update run its course. Now I have a machine with Windows Version 1511 10!

    It took me 4 days of downtime...

    I hope this helps someone else.

Maybe you are looking for