
Quote: Originally Posted by
frisco27
I turned on my computer and I had this blue screen problem in just a second then my PC reboots. After I logged in, there was a dialog box containing this info:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: d1
BCP1: 5A67D72F
BCP2: 00000002
BCP3: 00000001
BCP4: 89BC3E41
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\041911-39374-01.dmp
C:\Users\Haus of Frisco\AppData\Local\Temp\WER-154518-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
I'm bothering that the problem will happen again. Thanks for the help...
These were both caused by your ATAPI IDE Miniport
Driver. Part of the OS. To verify and repair yours run a system file check
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW
Read here for more information
SFC /SCANNOW Command - System File Checker
Let us know the results from the report at the end.
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\041911-39374-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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x8384b000 PsLoadedModuleList = 0x83995850
Debug session time: Mon Apr 18 22:06:09.393 2011 (GMT-4)
System Uptime: 0 days 0:02:33.173
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {5a67d72f, 2, 1, 89bc3e41}
Probably caused by : ataport.SYS ( ataport!IdeLogCrbEnd+15 )
Followup: MachineOwner
---------
0: 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: 5a67d72f, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 89bc3e41, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 839b5718
Unable to read MiSystemVaType memory at 839951a0
5a67d72f
CURRENT_IRQL: 2
FAULTING_IP:
ataport!IdeLogCrbEnd+15
89bc3e41 885621 mov byte ptr [esi+21h],dl
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: svchost.exe
TRAP_FRAME: 8078ae08 -- (.trap 0xffffffff8078ae08)
ErrCode = 00000002
eax=85eabf98 ebx=86b759c0 ecx=85eabd10 edx=00000005 esi=5a67d70e edi=00000000
eip=89bc3e41 esp=8078ae7c ebp=8078ae80 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
ataport!IdeLogCrbEnd+0x15:
89bc3e41 885621 mov byte ptr [esi+21h],dl ds:0023:5a67d72f=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 89bc3e41 to 8388c5cb
STACK_TEXT:
8078ae08 89bc3e41 badb0d00 00000005 59879813 nt!KiTrap0E+0x2cf
8078ae80 89bcc214 85eabd10 85eabd10 85ead0e0 ataport!IdeLogCrbEnd+0x15
8078aef4 89bcc677 85ead0e0 85eabd10 85ead09c ataport!IdeProcessCompletedRequests+0x40
8078af48 838c31b5 85ead09c 85ead028 00000000 ataport!IdePortCompletionDpc+0xab
8078afa4 838c3018 83976d20 88015678 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 838c27dc 8c399440 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 8c399440 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
WARNING: Frame IP not in any known module. Following frames may be wrong.
838c27dc 00000000 0000001a 00d6850f bb830000 0x8c399440
STACK_COMMAND: kb
FOLLOWUP_IP:
ataport!IdeLogCrbEnd+15
89bc3e41 885621 mov byte ptr [esi+21h],dl
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: ataport!IdeLogCrbEnd+15
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ataport
IMAGE_NAME: ataport.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce788e8
FAILURE_BUCKET_ID: 0xD1_ataport!IdeLogCrbEnd+15
BUCKET_ID: 0xD1_ataport!IdeLogCrbEnd+15
Followup: MachineOwner
---------