New
#1
BSOD - ntkrnlmp.exe
Thank you all in advance...
So a little background. I built this computer a month or two ago. Everything was fine, games like Supreme Commander were running great, but I wanted to change up my partitions and hard drives (go figure). I moved both of my drives off the 6Mb/s SATA connections because Linux didn't have the drivers yet to support it. I also plugged in a multi-usb port I had and then shared a drive between my windows and linux environment.
So when I got everything back running I started experiencing blue screens. The first thing I did was run the driver verifier as spelled out here. All that yeilded me was a DRIVER_VERIFIER_IOMANAGER_VIOLATION on dadder.sys. So I removed that. Still got blue screens. Using WhoCrashed and WinDbg I saw that I was getting a VIDEO_TDR_TIMEOUT_DETECTED for atikmpag.sys with a description inditing a multiport driver. So I removed the multiport usb. Fixed that. So since then I've also run memtest86 and everything checked out kosher.
So that was a few days ago. Now the crashes are solely (and happening often) because of ntoskrnl.exe. All of the dumps look the same outside of time of occurrence, so I'll just post the latest one. Coincidently it occurred when I was initially trying to post my issue here about an hour ago. I've scoured the interwebs for the last few days with little success, so I decided to reach out to the experts. Heeeeeeelp :)
HTML Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\070810-22620-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv symbols*http://msdl.microsoft.com/download/symbols;srv*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.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02a1a000 PsLoadedModuleList = 0xfffff800`02c57e50 Debug session time: Thu Jul 8 22:12:18.892 2010 (UTC - 4:00) System Uptime: 0 days 0:56:37.312 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 80050031, 6f8, fffff80002a52e58} Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000006f8 Arg4: fffff80002a52e58 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002a89b69 to fffff80002a8a600 STACK_TEXT: fffff880`009f0ce8 fffff800`02a89b69 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx fffff880`009f0cf0 fffff800`02a88032 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`009f0e30 fffff800`02a52e58 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 fffff880`038e3f30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiDoubleFaultAbort+b2 fffff800`02a88032 90 nop SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiDoubleFaultAbort+b2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb FAILURE_BUCKET_ID: X64_0x7f_8_VRFK_nt!KiDoubleFaultAbort+b2 BUCKET_ID: X64_0x7f_8_VRFK_nt!KiDoubleFaultAbort+b2 Followup: MachineOwner --------- 1: kd> lmvm nt start end module name fffff800`02a1a000 fffff800`02ff6000 nt (pdb symbols) C:\Program Files\Debugging Tools for Windows (x64)\sym\ntkrnlmp.pdb\7E9A3CAB626845DE8E10816E3080A3B72\ntkrnlmp.pdb Loaded symbol image file: ntkrnlmp.exe Mapped memory image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4B88CFEB5dc000\ntoskrnl.exe Image path: ntkrnlmp.exe Image name: ntkrnlmp.exe Timestamp: Sat Feb 27 02:55:23 2010 (4B88CFEB) CheckSum: 00545094 ImageSize: 005DC000 File version: 6.1.7600.16539 Product version: 6.1.7600.16539 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 1.0 App File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: ntkrnlmp.exe OriginalFilename: ntkrnlmp.exe ProductVersion: 6.1.7600.16539 FileVersion: 6.1.7600.16539 (win7_gdr.100226-1909) FileDescription: NT Kernel & System LegalCopyright: © Microsoft Corporation. All rights reserved.
Quote