I am getting a BSOD error that happens about every 40 minutes.
I have a custom built computer
Asus p5q se
windows 7 professional downloaded from student discount digital river website
8gb kingston ddr ram (can't remember exact name)
1x400gb 1x80gb 2x320gb hard drives
nvidia 8400gs video card
no sound card
mushkin 600 watt power supply
intel c2d e8400
Easy mdfsysnt.sys (MDFSYSNT.SYS (which is a drive for HSF/HSF+/Journaled formatted drives, only one conclusion; macdrive ) is causing these virtually identical crashes. I would remove it.
The other major problem is asacpi.sys (yours 2005) a huge cause of BSOD's
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).
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\Windows_NT6_BSOD_jcgriff2\021911-48095-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Machine Name: Kernel base = 0xfffff800`02a4b000 PsLoadedModuleList = 0xfffff800`02c88e50 Debug session time: Sat Feb 19 20:16:58.434 2011 (GMT-5) System Uptime: 0 days 1:40:29.104 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list .................. Unable to load image \SystemRoot\System32\Drivers\MDFSYSNT.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for MDFSYSNT.sys *** ERROR: Module load completed but symbols could not be loaded for MDFSYSNT.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff80002ad088b, fffff88009858478, fffff88009857ce0} Probably caused by : MDFSYSNT.sys ( MDFSYSNT+706a ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff80002ad088b, The address that the exception occurred at Arg3: fffff88009858478, Exception Record Address Arg4: fffff88009857ce0, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!IoIsOperationSynchronous+b fffff800`02ad088b f6425002 test byte ptr [rdx+50h],2 EXCEPTION_RECORD: fffff88009858478 -- (.exr 0xfffff88009858478) ExceptionAddress: fffff80002ad088b (nt!IoIsOperationSynchronous+0x000000000000000b) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000050 Attempt to read from address 0000000000000050 CONTEXT: fffff88009857ce0 -- (.cxr 0xfffff88009857ce0) rax=fffffa800a135d48 rbx=0000000000000002 rcx=fffffa800a135840 rdx=0000000000000000 rsi=fffffa8009888040 rdi=fffffa800a135840 rip=fffff80002ad088b rsp=fffff880098586b8 rbp=fffffa8009888190 r8=fffffa8009888190 r9=000000000000001b r10=fffffa80074837c0 r11=fffffa8009989c80 r12=fffffa800a135840 r13=fffffa800a135d48 r14=0000000000000001 r15=fffff880098587f0 iopl=0 nv up ei ng nz ac pe cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010293 nt!IoIsOperationSynchronous+0xb: fffff800`02ad088b f6425002 test byte ptr [rdx+50h],2 ds:002b:00000000`00000050=?? Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000050 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf30e0 0000000000000050 FOLLOWUP_IP: MDFSYSNT+706a fffff880`0184306a ?? ??? BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from fffff8800184306a to fffff80002ad088b STACK_TEXT: fffff880`098586b8 fffff880`0184306a : fffff880`00961000 fffffa80`00000030 fffffa80`07491be0 fffffa80`093b7010 : nt!IoIsOperationSynchronous+0xb fffff880`098586c0 fffff880`00961000 : fffffa80`00000030 fffffa80`07491be0 fffffa80`093b7010 fffffa80`074e3250 : MDFSYSNT+0x706a fffff880`098586c8 fffffa80`00000030 : fffffa80`07491be0 fffffa80`093b7010 fffffa80`074e3250 00000000`00000000 : 0xfffff880`00961000 fffff880`098586d0 fffffa80`07491be0 : fffffa80`093b7010 fffffa80`074e3250 00000000`00000000 00000000`00000000 : 0xfffffa80`00000030 fffff880`098586d8 fffffa80`093b7010 : fffffa80`074e3250 00000000`00000000 00000000`00000000 fffffa80`09fbe040 : 0xfffffa80`07491be0 fffff880`098586e0 fffffa80`074e3250 : 00000000`00000000 00000000`00000000 fffffa80`09fbe040 fffffa80`0a135840 : 0xfffffa80`093b7010 fffff880`098586e8 00000000`00000000 : 00000000`00000000 fffffa80`09fbe040 fffffa80`0a135840 fffff880`0184342f : 0xfffffa80`074e3250 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: MDFSYSNT+706a FOLLOWUP_NAME: MachineOwner MODULE_NAME: MDFSYSNT IMAGE_NAME: MDFSYSNT.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a3fef22 STACK_COMMAND: .cxr 0xfffff88009857ce0 ; kb FAILURE_BUCKET_ID: X64_0x7E_MDFSYSNT+706a BUCKET_ID: X64_0x7E_MDFSYSNT+706a Followup: MachineOwner --------- 0: kd> lmvm MDFSYSNT start end module name fffff880`0183c000 fffff880`0189b000 MDFSYSNT T (no symbols) Loaded symbol image file: MDFSYSNT.sys Image path: \SystemRoot\System32\Drivers\MDFSYSNT.sys Image name: MDFSYSNT.sys Timestamp: Mon Jun 22 16:52:50 2009 (4A3FEF22) CheckSum: 00056063 ImageSize: 0005F000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Quote