Same BSOD errors before and after clean install

Youngstown · 06 Feb 2011

Towards the end of January, I was receiving a BSOD which would not allow me to log in normally. After trying various methods, I bought a new hard drive and performed a clean install (retail).

Several days later from the clean install, I am receiving the same errors I was getting before. I am including the dump files via this posting. Now I am not overclocking and my hardware is as follows:

Windows 7 Ultimate 64bit
AMD Phenom II 805 Quad
8GB DDR3 1333
600 Watt PSU energy efficient
ATI 4770 Video Card
4 SATAII hard drives
LG Blue Burner
Logitech Web Cam
USB Keyboard/Mouse
Full Tower Case (great airflow; cooling)

CPU temps are 23C idle. After the clean install, I was stable for several days. On yesterday, I saw a Windows Defender error and when I clicked on it, The PC rebooted and then loaded a BSOD. The OS has not been stable since. I have ran Malwarebytes and no problems. Even had Defender run again…no errors.

During the clean install, I made sure to install all of the latest drivers and then performed all of the Windows Update(s). I did the Windows Memory test (Full) and the MEMTEST with no errors found within the installed RAM.

Any help would be appreciated.

Thanks!

zigzag3143 · 06 Feb 2011

Youngstown said:

Towards the end of January, I was receiving a BSOD which would not allow me to log in normally. After trying various methods, I bought a new hard drive and performed a clean install (retail).

Several days later from the clean install, I am receiving the same errors I was getting before. I am including the dump files via this posting. Now I am not overclocking and my hardware is as follows:

Windows 7 Ultimate 64bit
AMD Phenom II 805 Quad
8GB DDR3 1333
600 Watt PSU energy efficient
ATI 4770 Video Card
4 SATAII hard drives
LG Blue Burner
Logitech Web Cam
USB Keyboard/Mouse
Full Tower Case (great airflow; cooling)

CPU temps are 23C idle. After the clean install, I was stable for several days. On yesterday, I saw a Windows Defender error and when I clicked on it, The PC rebooted and then loaded a BSOD. The OS has not been stable since. I have ran Malwarebytes and no problems. Even had Defender run again…no errors.

During the clean install, I made sure to install all of the latest drivers and then performed all of the Windows Update(s). I did the Windows Memory test (Full) and the MEMTEST with no errors found within the installed RAM.

Any help would be appreciated.

Thanks!

Two problems

1-asacpi 2005

ASACPI.sys Sun Mar 27 22:30:36 2005

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

2-ataport.sys run a system file check to verify and repair system files

SFC /SCANNOW Command - System File Checker

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Minidump\020611-38048-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c0e000 PsLoadedModuleList = 0xfffff800`02e4be50
Debug session time: Sun Feb  6 14:15:11.547 2011 (GMT-5)
System Uptime: 0 days 0:10:31.936
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8800a9d8748, 2, 0, fffff88000e34c50}

Probably caused by : ataport.SYS ( ataport!IdeLogCrbActive+bc )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8800a9d8748, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88000e34c50, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb60e0
 fffff8800a9d8748 

CURRENT_IRQL:  2

FAULTING_IP: 
ataport!IdeLogCrbActive+bc
fffff880`00e34c50 f30f6f4148      movdqu  xmm0,xmmword ptr [rcx+48h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002d8c4b0 -- (.trap 0xfffff88002d8c4b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800adce390 rbx=0000000000000000 rcx=fffff8800a9d8700
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000e34c50 rsp=fffff88002d8c640 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8007435d40
r11=fffff88002d8c770 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
ataport!IdeLogCrbActive+0xbc:
fffff880`00e34c50 f30f6f4148      movdqu  xmm0,xmmword ptr [rcx+48h] ds:ac20:fffff880`0a9d8748=????????????????????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c7dca9 to fffff80002c7e740

STACK_TEXT:  
fffff880`02d8c368 fffff800`02c7dca9 : 00000000`0000000a fffff880`0a9d8748 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02d8c370 fffff800`02c7c920 : 00000000`00000000 fffffa80`07436528 fffffa80`069501a0 fffff880`00e491a0 : nt!KiBugCheckDispatch+0x69
fffff880`02d8c4b0 fffff880`00e34c50 : 00000000`00000001 00000000`00000000 fffffa80`074391b0 00000000`00000001 : nt!KiPageFault+0x260
fffff880`02d8c640 fffff880`00e3ec71 : fffffa80`07bd67d8 fffffa80`069501a0 fffffa80`07bd66f0 00000000`00000000 : ataport!IdeLogCrbActive+0xbc
fffff880`02d8c670 fffff800`031ee9ce : fffffa80`07bd67d8 00000000`00000018 00000000`00000000 00000000`00000001 : ataport!IdeStartIoCallBack+0xc9
fffff880`02d8c7e0 fffff800`031ef13d : fffffa80`0741ec90 fffffa80`06952ea0 fffffa80`06952e00 00000000`00000000 : hal!HalpAllocateAdapterCallback+0x146
fffff880`02d8c880 fffff800`031ee71f : fffffa80`07bd6790 00000000`00000200 fffffa80`06952ea0 fffffa80`0776ec50 : hal!HalAllocateAdapterChannel+0x101
fffff880`02d8c8c0 fffff880`00e010d3 : fffffa80`07bd66f0 fffff880`00e0112c fffffa80`000000a0 fffffa80`06952ea0 : hal!HalBuildScatterGatherList+0x2f3
fffff880`02d8c930 fffff880`00e3eb3b : fffffa80`07bd66f0 fffffa80`074391b0 fffffa80`069501a0 fffffa80`07bd66f0 : PCIIDEX!BmSetup+0x6b
fffff880`02d8c990 fffff880`00e3d7eb : fffffa80`06951500 fffffa80`074391b0 fffffa80`06951500 fffffa80`069501a0 : ataport!IdeDispatchChannelRequest+0xef
fffff880`02d8c9c0 fffff880`00e3d31e : 00000000`00000001 fffffa80`07bd66f0 00000000`00000001 fffffa80`07bd66f0 : ataport!IdeStartChannelRequest+0x113
fffff880`02d8ca40 fffff880`00e3f582 : 00000000`00000000 00000000`00000000 fffffa80`074391b0 fffffa80`087aab80 : ataport!IdeStartNextDeviceRequest+0x18e
fffff880`02d8cae0 fffff880`00e3f0ec : fffffa80`069501a0 00000000`00000000 fffffa80`069501a0 fffffa80`087aab80 : ataport!IdeProcessCompletedRequests+0x26a
fffff880`02d8cc10 fffff800`02c89bfc : fffff880`02d64180 00000000`5c79b36d fffffa80`06950050 fffffa80`06950118 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02d8ccd0 fffff800`02c86eea : fffff880`02d64180 fffff880`02d6efc0 00000000`00000000 fffff880`00e3ef44 : nt!KiRetireDpcList+0x1bc
fffff880`02d8cd80 00000000`00000000 : fffff880`02d8d000 fffff880`02d87000 fffff880`02d8cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ataport!IdeLogCrbActive+bc
fffff880`00e34c50 f30f6f4148      movdqu  xmm0,xmmword ptr [rcx+48h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  ataport!IdeLogCrbActive+bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ataport

IMAGE_NAME:  ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc118

FAILURE_BUCKET_ID:  X64_0xD1_ataport!IdeLogCrbActive+bc

BUCKET_ID:  X64_0xD1_ataport!IdeLogCrbActive+bc

Followup: MachineOwner
---------

Youngstown · 06 Feb 2011

Good call on the ASACPI.SYS file. I updated the file from the ASUS website. I should have put my MB model which is an ASUS M4A785TD-V EVO. Now that file is updated and verified (2009)...the 2005 version is loaded in the LAST KNOWN GOOD…(not good huh?). Again, it is verified plus corrected.

Running SFC.EXE yielded no results at all. WINDOWS RESOURCE PROTECTION DID NOT FIND ANY INTEGRITY VIOLATIONS. I even used VERIFYFILE to insure that the file was scanned and checked for errors.

Just for the heck of it, I ran Malwarebytes to insure nothing is infected. Results were good; nothing malicious found.

BSOD before reaching the desktop fully….loading the latest dump file.

Youngstown · 06 Feb 2011

I am hoping my last post didn't yield that my problem was fixed. I uploaded the DumpFiles after the fixes were applied. Still have BSOD when trying to boot normally.

Youngstown · 07 Feb 2011

I ran a different version of MemTest which is v4.15b. See the attached photo. I have 4 sticks of DDR3 1333 RAM (8GB). The timings are 8-8-8-22 at 1.5V. I have a set of G.Skill RipJaws rated for that speed and I have an additional set of Patriot Enhanced RAM (default is 9-9-9-24). They have existed perfectly for the past year at 8-8-8-22).

Just booting into Windows 7 64bit (RipJaws only)...BSOD after reaching the desktop.