Blue Screen of Death (BSOD) Posting Instructions

Code:

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

Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_bsodinfo[1].zip\Windows_NT6_BSOD_jcgriff2\Mini012411-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
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0x82406000 PsLoadedModuleList = 0x8251dc70
Debug session time: Mon Jan 24 19:43:00.383 2011 (GMT-5)
System Uptime: 0 days 0:00:24.133
Loading Kernel Symbols
........................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, 80153000, 0, 0}
Probably caused by : ntkrpamp.exe ( nt!KeContextFromKframes+24 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
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: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80153000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------

BUGCHECK_STR:  0x7f_8
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
EXCEPTION_RECORD:  8b7f1488 -- (.exr 0xffffffff8b7f1488)
ExceptionAddress: 0242dce9
   ExceptionCode: 10000004
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000008
   Parameter[1]: 0242dce9
TRAP_FRAME:  8b7f1fdc -- (.trap 0xffffffff8b7f1fdc)
Unable to read trap frame at 8b7f1fdc
LAST_CONTROL_TRANSFER:  from 8242d839 to 82444701
STACK_TEXT:  
8b7f10a4 8242d839 8b7f14dc 00000000 8b7f1184 nt!KeContextFromKframes+0x24
8b7f146c 8245183a 8b7f1488 00000000 8b7f14dc nt!KiDispatchException+0x7a
8b7f14d4 824517ee 8b7f1570 0242dce9 badb0d00 nt!CommonDispatchException+0x4a
8b7f154c 824af482 8b7f1a08 8b7f3db0 8b7f1704 nt!Kei386EoiHelper+0x186
8b7f1570 824af454 8b7f1a08 8b7f3db0 8b7f1704 nt!ExecuteHandler2+0x26
8b7f1628 8242d92f 8b7f1a08 8b7f1704 ab2af68c nt!ExecuteHandler+0x24
8b7f19ec 8245183a 8b7f1a08 00000000 8b7f1a5c nt!KiDispatchException+0x170
8b7f1a54 824517ee 8b7f1af0 0242dce9 badb0d00 nt!CommonDispatchException+0x4a
8b7f1acc 824af482 8b7f1f88 8b7f3db0 8b7f1c84 nt!Kei386EoiHelper+0x186
8b7f1af0 824af454 8b7f1f88 8b7f3db0 8b7f1c84 nt!ExecuteHandler2+0x26
8b7f1ba8 8242d92f 8b7f1f88 8b7f1c84 ab2af00c nt!ExecuteHandler+0x24
8b7f1f6c 8245183a 8b7f1f88 00000000 8b7f1fdc nt!KiDispatchException+0x170
8b7f1fd4 824517ee 8b7f2070 0242dce9 badb0d00 nt!CommonDispatchException+0x4a
8b7f1fdc 0242dce9 badb0d00 824af496 00000000 nt!Kei386EoiHelper+0x186
WARNING: Frame IP not in any known module. Following frames may be wrong.
8b7f1fe0 badb0d00 824af496 00000000 00000000 0x242dce9
8b7f1fe4 824af496 00000000 00000000 00000000 0xbadb0d00
8b7f1fe8 00000000 00000000 00000000 00000000 nt!ExecuteHandler2+0x3a

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KeContextFromKframes+24
82444701 ff1560714082    call    dword ptr [nt!_imp__KeGetCurrentIrql (82407160)]
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!KeContextFromKframes+24
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4c0e557c
FAILURE_BUCKET_ID:  0x7f_8_nt!KeContextFromKframes+24
BUCKET_ID:  0x7f_8_nt!KeContextFromKframes+24
Followup: MachineOwner
---------
0: kd> lmtsmn
start    end        module name
8ab93000 8aba0080   1394BUS  1394BUS.SYS  Sat Jan 19 00:53:27 2008 (47919057)
82b34000 82b7a000   acpi     acpi.sys     Sat Apr 11 00:19:03 2009 (49E01A37)
8ab1c000 8ab2c000   amdk8    amdk8.sys    Sat Jan 19 00:27:20 2008 (47918A38)
8a67d000 8a685000   atapi    atapi.sys    Sat Apr 11 00:39:09 2009 (49E01EED)
8a685000 8a6a3000   ataport  ataport.SYS  Sat Apr 11 00:39:10 2009 (49E01EEE)
8ef06000 8ef43000   atikmpag atikmpag.sys Thu Nov 25 21:16:27 2010 (4CEF187B)
8061c000 80624000   BOOTVID  BOOTVID.dll  Sat Jan 19 02:27:15 2008 (4791A653)
80665000 80745000   CI       CI.dll       Sat Apr 11 02:25:22 2009 (49E037D2)
8ada2000 8adc3000   CLASSPNP CLASSPNP.SYS Sat Apr 11 00:39:05 2009 (49E01EE9)
80624000 80665000   CLFS     CLFS.SYS     Sat Apr 11 00:13:51 2009 (49E018FF)
8adcc000 8add9000   crashdmp crashdmp.sys Sat Apr 11 00:39:12 2009 (49E01EF0)
8adc3000 8adcc000   crcdisk  crcdisk.sys  Thu Nov 02 04:52:27 2006 (4549B1CB)
8ad91000 8ada2000   disk     disk.sys     Sat Apr 11 00:39:14 2009 (49E01EF2)
8add9000 8ade3000   dump_diskdump dump_diskdump.sys Sat Apr 11 00:39:11 2009 (49E01EEF)
8ade3000 8ae00000   dump_nvstor32 dump_nvstor32.sys Mon Jul 02 20:35:28 2007 (468999D0)
8ad6a000 8ad91000   ecache   ecache.sys   Sat Apr 11 00:40:12 2009 (49E01F2C)
8a740000 8a750000   fileinfo fileinfo.sys Sat Jan 19 00:34:27 2008 (47918BE3)
8a70e000 8a740000   fltmgr   fltmgr.sys   Sat Apr 11 00:13:59 2009 (49E01907)
8aaf6000 8ab11000   fwpkclnt fwpkclnt.sys Sat Apr 11 00:45:42 2009 (49E02076)
827bf000 827f2000   hal      halmacpi.dll Sat Apr 11 00:13:13 2009 (49E018D9)
8a971000 8a9fe000   HDAudBus HDAudBus.sys Sat Apr 11 00:42:41 2009 (49E01FC1)
80604000 8060b000   kdcom    kdcom.dll    Sat Apr 11 02:25:29 2009 (49E037D9)
8a759000 8a7ca000   ksecdd   ksecdd.sys   Mon Jun 15 08:48:53 2009 (4A364335)
8a66d000 8a67d000   mountmgr mountmgr.sys Sat Jan 19 00:49:13 2008 (47918F59)
82b7a000 82b82000   msisadrv msisadrv.sys Sat Jan 19 00:32:51 2008 (47918B83)
8a90b000 8a936000   msrpc    msrpc.sys    Sat Apr 11 00:37:32 2009 (49E01E8C)
8ad5b000 8ad6a000   mup      mup.sys      Sat Apr 11 00:14:12 2009 (49E01914)
8a800000 8a90b000   ndis     ndis.sys     Sat Apr 11 00:45:52 2009 (49E02080)
8a936000 8a971000   NETIO    NETIO.SYS    Sat Apr 11 00:46:21 2009 (49E0209D)
82406000 827bf000   nt       ntkrpamp.exe Tue Jun 08 10:36:44 2010 (4C0E557C)
8ac0a000 8ad1a000   Ntfs     Ntfs.sys     Sat Apr 11 00:14:34 2009 (49E0192A)
8ee06000 8ef05600   nvmfdx32 nvmfdx32.sys Fri Aug 01 14:37:49 2008 (489357FD)
8a701000 8a70e000   nvstor   nvstor.sys   Wed Jun 06 16:34:41 2007 (46671A61)
8a6a3000 8a6c0000   nvstor32 nvstor32.sys Mon Jul 02 20:35:28 2007 (468999D0)
8ab83000 8ab92300   ohci1394 ohci1394.sys Sat Apr 11 00:43:04 2009 (49E01FD8)
82ba9000 82bb8000   partmgr  partmgr.sys  Sat Apr 11 00:39:19 2009 (49E01EF7)
82b82000 82ba9000   pci      pci.sys      Sat Apr 11 00:19:16 2009 (49E01A44)
8a658000 8a65f000   pciide   pciide.sys   Sat Apr 11 00:39:10 2009 (49E01EEE)
8a65f000 8a66d000   PCIIDEX  PCIIDEX.SYS  Sat Apr 11 00:39:09 2009 (49E01EED)
8060b000 8061c000   PSHED    PSHED.dll    Sat Apr 11 02:25:32 2009 (49E037DC)
8a750000 8a758dc0   PxHelp20 PxHelp20.sys Wed Oct 17 14:24:26 2007 (4716535A)
82b0e000 82b34000   SCSIPORT SCSIPORT.SYS Sat Jan 19 00:49:44 2008 (47918F78)
8ad53000 8ad5b000   spldr    spldr.sys    Thu Jun 21 20:29:17 2007 (467B17DD)
82a05000 82b05000   sptd     sptd.sys     Wed Mar 05 19:32:57 2008 (47CF3BB9)
8a6c0000 8a701000   storport storport.sys Sat Apr 11 00:39:19 2009 (49E01EF7)
8aa0c000 8aaf6000   tcpip    tcpip.sys    Wed Jun 16 09:45:41 2010 (4C18D585)
8ac00000 8ac09000   tunmp    tunmp.sys    Sat Jan 19 00:55:40 2008 (479190DC)
8ab11000 8ab1c000   tunnel   tunnel.sys   Thu Feb 18 06:28:13 2010 (4B7D244D)
8ab74000 8ab83000   usbehci  usbehci.sys  Sat Apr 11 00:42:52 2009 (49E01FCC)
8ab2c000 8ab36000   usbohci  usbohci.sys  Sat Apr 11 00:42:52 2009 (49E01FCC)
8ab36000 8ab74000   USBPORT  USBPORT.SYS  Sat Apr 11 00:42:55 2009 (49E01FCF)
82bb8000 82bc7000   volmgr   volmgr.sys   Sat Jan 19 00:49:51 2008 (47918F7F)
8a60e000 8a658000   volmgrx  volmgrx.sys  Sat Apr 11 00:39:25 2009 (49E01EFD)
8ad1a000 8ad53000   volsnap  volsnap.sys  Sat Apr 11 00:39:37 2009 (49E01F09)
80745000 807c1000   Wdf01000 Wdf01000.sys Sat Jan 19 00:52:21 2008 (47919015)
807c1000 807ce000   WDFLDR   WDFLDR.SYS   Sat Jan 19 00:52:19 2008 (47919013)
82b05000 82b0e000   WMILIB   WMILIB.SYS   Sat Jan 19 00:53:08 2008 (47919044

Outdated drivers- Update these drivers

Code:

 crcdisk.sys  Thu Nov 02 04:52:27 2006
PxHelp20.sys Wed Oct 17 14:24:26 2007
amdk8.sys    Sat Jan 19 00:27:20 2008

You have given me two reports, one dated today. Neither one gave too much information, but based on those reports these are my suggestions.

The reports that you have submitted reveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receive the more clues are made available improving our chances of finding a solution to your problem. Each remedy suggested must be performed regardless of placement in this report or other variables. You may have to experience several more BSODs until the final answer is discovered.

If overclocking restore normal settings

SFC /scannow
System Files - SFC Command


Scan with your Anti Virus

Update outdated listed drivers. If I have inadvertently listed any Microsoft Drivers, they can be ignored.

How to Find Drivers
search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone - will help you search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
and here
http://www.edbott.com/weblog/the-vista-master-driver-list/
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/
You can also locate information about your driver using this information
http://www.sevenforums.com/tutorials/96442-device-manager-finding-unknown-devices.html


Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done:
http://www.duplexsecure.com/en/faq

After performing all of the above, post back with any new BSOD reports, or indicate that the attempted repairs were successful.
If any links do not work, if clicked, please copy and paste to browser address bar.
It is very important to remember that the dump reports only give clues as to the problem and although it is very easy to analyze only one or two, usually more are needed. If you experience additional BSOD after installing a current version of the driver in question, be sure to post so that we can use the additional information to assist you in preventing the BSOD's

Thats a Microsoft Driver, forget about that one.
Just make sure that your automatic update is turned on. If you get updates etc, its on.
Then just make sure that number 8 is on.
Windows Update Settings - Change - Windows 7 Forums

Yes, SPTD is known for causing BSOD's get rid of it.

You do nothing, run the driver sweeper 24 hours. Bad drivers will BSOD. Just give me the report after the 24 hours.