Well I have messed around with this a fair bit now, and Finally went back and reloaded windoews 7 now. I have since had 2 failures, both with only the BSOD flashing very quickly and then the system restarts. I have attached both of the .dmp files for review. And just for the record, I am not overclocking. The system on now running with the OS and AVG. nothing else has been installed. Any help is appreciated.
the two dmps were caused by hardware. specifically ataport.sys, and halmacpi.dll
I would
re-install ataport
run a system file check
(type cmd in search>right click and run as admin>sfc /scannow)
Let us know the results
Ken
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\021610-29000-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8284f000 PsLoadedModuleList = 0x82997810
Debug session time: Wed Feb 17 02:01:03.270 2010 (GMT-5)
System Uptime: 0 days 1:16:39.002
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {20, 2, 0, 8835df38}
Probably caused by : ataport.SYS ( ataport!IdeLogCrbActive+16 )
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: 00000020, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8835df38, address which referenced memory
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'avgldx86' and 'spsys.sys' overlap
READ_ADDRESS: GetPointerFromAddress: unable to read from 829b7718
Unable to read MiSystemVaType memory at 82997160
00000020
CURRENT_IRQL: 2
FAULTING_IP:
ataport!IdeLogCrbActive+16
8835df38 807b2001 cmp byte ptr [ebx+20h],1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: 8a527a3c -- (.trap 0xffffffff8a527a3c)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=85b946c8 edx=85b94320 esi=8a527af4 edi=85b94320
eip=8835df38 esp=8a527ab0 ebp=8a527abc iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
ataport!IdeLogCrbActive+0x16:
8835df38 807b2001 cmp byte ptr [ebx+20h],1 ds:0023:00000020=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 8835df38 to 828957eb
STACK_TEXT:
8a527a3c 8835df38 badb0d00 85b94320 866a6820 nt!KiTrap0E+0x2cf
8a527abc 883660e8 85525d10 85525d10 8483a0e0 ataport!IdeLogCrbActive+0x16
8a527ae0 88366051 85525d10 85525d10 8483a0e0 ataport!IdeStartIoCallBack+0x5c
8a527af4 88364a12 8483a0e0 85525d10 851739c0 ataport!IdeDispatchChannelRequest+0x69
8a527b0c 88364de3 8483a0e0 85525d10 85d9b618 ataport!IdeStartChannelRequest+0x42
8a527b30 88365fa8 001739c0 00525d10 85b94320 ataport!IdeStartDeviceRequest+0x15d
8a527b50 8836246b 00000103 85b94320 8a527b78 ataport!IdePortPdoDispatch+0x9a
8a527b60 8288b4bc 85173908 85b94320 ffe84005 ataport!IdePortDispatch+0x1d
8a527b78 882373b8 ffe84005 8a527b98 8823dc08 nt!IofCallDriver+0x63
8a527b84 8823dc08 85541918 85b94320 85b943b4 ACPI!ACPIDispatchForwardIrp+0x2a
8a527b98 88237642 85541918 85b94320 00000025 ACPI!ACPIIrpDispatchDeviceControl+0xa4
8a527bc8 8288b4bc 85541918 847e83c0 85d9b460 ACPI!ACPIDispatchIrp+0x198
8a527be0 82f9949c 7a4872a8 8a527c6c 00000000 nt!IofCallDriver+0x63
8a527c24 82fa4ffe 00d9b460 8a527c6c 8a527c50 Wdf01000!FxIoTarget::SubmitSync+0x198
8a527c48 8860e9b0 00000020 85d9b460 85b78d50 Wdf01000!imp_WdfRequestSend+0x178
8a527c7c 8860e55b 85b60ab8 8281b7a0 85b60ab8 cdrom!RequestSendMcnRequest+0x4a
8a527cb0 8860ea37 85b60ab8 7b4bf5d8 85b785a8 cdrom!RequestProcessSerializedIoctl+0x37c
8a527cc4 82fb9042 7a487a50 85b56e00 85b785a8 cdrom!IoctlWorkItemRoutine+0x4b
8a527ce0 82fb90aa 85b604f0 8a527d00 82a6f7b5 Wdf01000!FxWorkItem::WorkItemHandler+0xad
8a527cec 82a6f7b5 85b604f0 85b785a8 848474c0 Wdf01000!FxWorkItem::WorkItemThunk+0x19
8a527d00 828bcf2b 85b56e00 00000000 848474c0 nt!IopProcessWorkItem+0x23
8a527d50 82a5d66d 00000001 a9aca9af 00000000 nt!ExpWorkerThread+0x10d
8a527d90 8290f0d9 828bce1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
ataport!IdeLogCrbActive+16
8835df38 807b2001 cmp byte ptr [ebx+20h],1
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: ataport!IdeLogCrbActive+16
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ataport
IMAGE_NAME: ataport.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf16
FAILURE_BUCKET_ID: 0xD1_ataport!IdeLogCrbActive+16
BUCKET_ID: 0xD1_ataport!IdeLogCrbActive+16
Followup: MachineOwner
---------
Code:
021610-29000-01.dmp 2/16/2010 11:02:12 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 0x00000020 0x00000002 0x00000000 0x8835df38 ataport.SYS ataport.SYS+1f38 32-bit
021710-22838-01.dmp 2/17/2010 11:08:20 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0x0000008c 0x00000002 0x00000001 0x82aa7d28 halmacpi.dll halmacpi.dll+3479 32-bit
Quote