Solved BSOD and USB hang 0x9F

[YoYo155]

I've been getting hangs when trying to shutdown/restart (from the start menu)
as well the USB peripherals hang / unload / eject.

Just recently after putting up with it for a while I've got a couple of bsod's (that are the same). Now I'm using the default driver from MS because my MB doesn't have "it's own", but realy concern is could this be a case of a victim BSOD analysis and being caused by something else?

(.dmp included) Thanks for your help!.

 

[Vir Gnarus]

Your motherboard doesn't even have its own drivers available on a website? I see it's an MSI mobo, I'm pretty sure they would have drivers.

Anyways, the BIOS itself is woefully outdated, being from 2007, which is pre-Windows 7. You'll want this updated as well as chipset drivers. USB drivers can also be installed if present in needed, but be careful since a lot of them are labeled as drivers but are actually some gimmick software that can often harbor bugs.

Daemon Tools is also present and dated back from Jan 2012. Keep it updated or resort to another emulation solution since it's known for causing BSODs if not continuously kept updated.

Other motherboard drivers like for your network appear outdated as well. Probably best to just update everything present for your mobo. Do not install utilities, software, or anything else offered by the motherboard manufacturer that is not specifically required to make a component of the motherboard function.

Anyways, for specific analysis, this single crash was caused because the system was attempting to remove a USB HID device (typically a keyboard or some other similar input device) from the OS, which is done during a device eject or a system power down. It got hung because something said it couldn't support the attempted remove device request.

Therefore, I think there's a problem with some input device connected to the system. If you have one of those keyboards with extra functions (like a gaming keyboard), check the manufacturer website for any possible driver/firmware updates for it. Do the same for the mouse as well if possible. If you're actually using a laptop or with just a regular keyboard/mouse, this may be conducive of a motherboard failure, which often the USB ports are the first to go. Try plugging into other USB ports as a workaround, otherwise it just means you need to replace the mobo/PC.

That's all I can get from this single crashdump. After performing all the recommendations, if your system still crashes, turn on Driver Verifier and let it crash some more, then send us those crashdumps.

 

[YoYo155]

Your motherboard doesn't even have its own drivers available on a website? I see it's an MSI mobo, I'm pretty sure they would have drivers.

Anyways, the BIOS itself is woefully outdated, being from 2007, which is pre-Windows 7. You'll want this updated as well as chipset drivers. USB drivers can also be installed if present in needed, but be careful since a lot of them are labeled as drivers but are actually some gimmick software that can often harbor bugs.

Daemon Tools is also present and dated back from Jan 2012. Keep it updated or resort to another emulation solution since it's known for causing BSODs if not continuously kept updated.

Other motherboard drivers like for your network appear outdated as well. Probably best to just update everything present for your mobo. Do not install utilities, software, or anything else offered by the motherboard manufacturer that is not specifically required to make a component of the motherboard function.

Anyways, for specific analysis, this single crash was caused because the system was attempting to remove a USB HID device (typically a keyboard or some other similar input device) from the OS, which is done during a device eject or a system power down. It got hung because something said it couldn't support the attempted remove device request.

Therefore, I think there's a problem with some input device connected to the system. If you have one of those keyboards with extra functions (like a gaming keyboard), check the manufacturer website for any possible driver/firmware updates for it. Do the same for the mouse as well if possible. If you're actually using a laptop or with just a regular keyboard/mouse, this may be conducive of a motherboard failure, which often the USB ports are the first to go. Try plugging into other USB ports as a workaround, otherwise it just means you need to replace the mobo/PC.

That's all I can get from this single crashdump. After performing all the recommendations, if your system still crashes, turn on Driver Verifier and let it crash some more, then send us those crashdumps.

Oh wow all that info from a single dump file! :shock:

It's what I suspected really, thank you!
I will try and find all of the latest drivers / updates for well everything .
I tried to analyze the *.dmp file using WinDbg I didn't see all of that in there how did you do it!?

 

[Vir Gnarus]

!analyze -v usually only skims the surface, though it's always a good starting point when opening a crashdump in Windbg. After that, one needs to know where to go and what commands Windbg offers to get there. I saw that it was a held up IRP (I/O for a device) so I used !irp Arg4 1 where Arg4 is the 4th argument in the bugcheck (the blocked IRP) and 1 means to output extra details. I saw it was caused by the Windows-provided USBHID driver (USB HID, or USB Human Interface Device) being held up (shows up pending), and most likely because the IoStatus was c00000bb, which if you run that through !error it'll say that error means the requested operation isn't supported. Looking at !irp in the Windbg help manual shows up a table of major and minor IRP codes, which in this case is 16 (power IRP) for major, and 2 (remove device) for minor. Lastly I just dumped a list of loaded modules (drivers) with timestamps to check for any older drivers, and used !sysinfo machineid for the BIOS version and mobo manufacturer. Output for all of this is below:

0: kd> [COLOR=Blue]!analyze -v[/COLOR]
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 871c2030, Physical Device Object of the stack
Arg3: 82f45ae0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: [COLOR=Green]85a5fe28[/COLOR], The blocked IRP

Debugging Details:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: USBHUB!_DEVICE_EXTENSION_PDO                  ***
***                                                                   ***
*************************************************************************
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c04da

MODULE_NAME: usbhub

FAULTING_MODULE: 99e39000 usbhub

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
82f45a94 82ee4637 0000009f 00000003 871c2030 nt!KeBugCheckEx+0x1e
82f45b00 82ee46b0 82f45ba0 00000000 82f52380 nt!PopCheckIrpWatchdog+0x1f5
82f45b38 82e96799 82f606e0 00000000 cdad6cdf nt!PopCheckForIdleness+0x73
82f45b7c 82e9673d 82f48d20 82f45ca8 00000001 nt!KiProcessTimerDpcTable+0x50
82f45c68 82e965fa 82f48d20 82f45ca8 00000000 nt!KiProcessExpiredTimerList+0x101
82f45cdc 82e9478e 00097bf2 87b11580 82f52380 nt!KiTimerExpiration+0x25c
82f45d20 82e945b8 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82f45d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_3_hidusb_IMAGE_usbhub.sys

BUCKET_ID:  0x9F_3_hidusb_IMAGE_usbhub.sys

Followup: MachineOwner
---------

0: kd>[COLOR=Blue] !irp [/COLOR][COLOR=Green]85a5fe28 [/COLOR][COLOR=Blue]1[/COLOR]
Irp is active with 7 stacks 6 is current (= 0x85a5ff4c)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
Flags = 00000000
ThreadListEntry.Flink = 85a5fe38
ThreadListEntry.Blink = 85a5fe38
IoStatus.Status = [COLOR=Red]c00000bb[/COLOR]
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000   
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = 85a5fe68
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = 85d5b0f0
Tail.Overlay.ListEntry.Blink = 82f60178
Tail.Overlay.CurrentStackLocation = 85a5ff4c
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ [COLOR=Sienna]16, 2[/COLOR]]   0 e1 87492980 00000000 00000000-00000000    [COLOR=Sienna]pending[/COLOR]
           [COLOR=Sienna]\Driver\HidUsb (IopUnloadSafeCompletion)[/COLOR]
            Args: 00012200 00000001 00000003 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-85bcc920    

            Args: 00000000 00000000 00000000 00000000

0: kd>[COLOR=Blue] !error [/COLOR][COLOR=Red]c00000bb[/COLOR]
[COLOR=Red]Error code: (NTSTATUS) 0xc00000bb (3221225659) - The request is not supported.[/COLOR]

0: kd> [COLOR=Blue]lmsm t[/COLOR]
start    end        module name
8babd000 8bb05000   ACPI      Sat Nov 20 03:37:52 2010 (4CE788E0)
93627000 93681000   afd       Sun Apr 24 22:18:00 2011 (4DB4D9D8)
97ba6000 97bb8000   AgileVpn  Mon Jul 13 19:55:00 2009 (4A5BC954)
8ba23000 8ba2c000   amdxata   Fri Mar 19 12:19:01 2010 (4BA3A3F5)
a019d000 a01a6000   asyncmac  Mon Jul 13 19:54:46 2009 (4A5BC946)
8bbe2000 8bbeb000   atapi     Mon Jul 13 19:11:15 2009 (4A5BBF13)
8ba00000 8ba23000   ataport   Sat Nov 20 03:38:00 2010 (4CE788E8)
9b000000 9b04d000   ATMFD     unavailable (00000000)
9095b000 90962000   Beep      Mon Jul 13 19:45:00 2009 (4A5BC6FC)
937a7000 937b5000   blbdrive  Mon Jul 13 19:23:04 2009 (4A5BC1D8)
8b8c7000 8b8cf000   BOOTVID   Mon Jul 13 21:04:34 2009 (4A5BD9A2)
828a8000 828c1000   bowser    Tue Feb 22 23:47:32 2011 (4D649164)
9b3a0000 9b3be000   cdd       unavailable (00000000)
90865000 90884000   cdrom     Sat Nov 20 03:38:09 2010 (4CE788F1)
8b911000 8b9bc000   CI        Sat Nov 20 07:05:17 2010 (4CE7B97D)
8bf96000 8bfbb000   CLASSPNP  Mon Jul 13 19:11:20 2009 (4A5BBF18)
8b8cf000 8b911000   CLFS      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8bd6f000 8bdcc000   cng       Fri Jun 01 22:46:38 2012 (4FC97E8E)
97b99000 97ba6000   CompositeBus  Sat Nov 20 04:50:21 2010 (4CE799DD)
99ec0000 99ecd000   crashdmp  Mon Jul 13 19:45:50 2009 (4A5BC72E)
9378f000 937a7000   dfsc      Sat Nov 20 03:42:32 2010 (4CE789F8)
93783000 9378f000   discache  Mon Jul 13 19:24:04 2009 (4A5BC214)
8c000000 8c011000   disk      Mon Jul 13 19:11:28 2009 (4A5BBF20)
97b17000 97b30000   drmk      Mon Jul 13 20:36:05 2009 (4A5BD2F5)
90825000 90865000   dtsoftbus01  Fri Jan 13 08:45:57 2012 (4F103595)
99ed8000 99ee1000   dump_atapi  Mon Jul 13 19:11:15 2009 (4A5BBF13)
99ecd000 99ed8000   dump_dumpata  Mon Jul 13 19:11:16 2009 (4A5BBF14)
99ee1000 99ef2000   dump_dumpfve  Mon Jul 13 19:12:47 2009 (4A5BBF6F)
99eb6000 99ec0000   Dxapi     Mon Jul 13 19:25:25 2009 (4A5BC265)
954b2000 95569000   dxgkrnl   Sat Nov 20 04:08:14 2010 (4CE78FFE)
95569000 955a2000   dxgmms1   Wed Feb 02 22:45:05 2011 (4D4A24C1)
90884000 90954000   eamonm    Wed Mar 07 09:32:23 2012 (4F577177)
90962000 90982000   ehdrv     Wed Mar 07 09:33:36 2012 (4F5771C0)
9377a000 93783000   EIO       Tue Jul 21 22:34:52 2009 (4A667ACC)
82964000 8297f000   epfwwfpr  Wed Mar 07 09:27:53 2012 (4F577069)
8bbeb000 8bbfc000   fileinfo  Mon Jul 13 19:21:51 2009 (4A5BC18F)
8b9bc000 8b9f0000   fltmgr    Mon Jul 13 19:11:13 2009 (4A5BBF11)
8bdda000 8bde3000   Fs_Rec    Wed Feb 29 22:21:26 2012 (4F4EEB36)
8bf64000 8bf96000   fvevol    Sat Nov 20 03:40:22 2010 (4CE78976)
8c160000 8c191000   fwpkclnt  Wed Aug 22 10:50:50 2012 (5034F1CA)
97b93000 97b98300   GEARAspiWDM  Thu May 03 15:55:59 2012 (4FA2E2CF)
83230000 83267000   hal       Sat Nov 20 03:37:38 2010 (4CE788D2)
955a2000 955c1000   HDAudBus  Sat Nov 20 04:59:28 2010 (4CE79C00)
99efd000 99f10000   HIDCLASS  Sat Nov 20 04:59:37 2010 (4CE79C09)
99f10000 99f16480   HIDPARSE  Mon Jul 13 19:50:59 2009 (4A5BC863)
99ef2000 99efd000   hidusb    Sat Nov 20 04:59:38 2010 (4CE79C0A)
82823000 828a8000   HTTP      Sat Nov 20 03:40:17 2010 (4CE78971)
8c1e8000 8c1f0000   hwpolicy  Sat Nov 20 03:37:35 2010 (4CE788CF)
97b6e000 97b86000   i8042prt  Mon Jul 13 19:11:23 2009 (4A5BBF1B)
8bbb7000 8bbbe000   intelide  Mon Jul 13 19:11:19 2009 (4A5BBF17)
937d6000 937e8000   intelppm  Mon Jul 13 19:11:03 2009 (4A5BBF07)
a0190000 a019d000   IOMap     Thu Mar 04 05:49:57 2010 (4B8F9055)
97b86000 97b93000   kbdclass  Mon Jul 13 19:11:15 2009 (4A5BBF13)
80ba1000 80ba9000   kdcom     Mon Jul 13 21:08:58 2009 (4A5BDAAA)
97b30000 97b64000   ks        Sat Nov 20 04:50:17 2010 (4CE799D9)
8bd5c000 8bd6f000   ksecdd    Fri Jun 01 22:25:35 2012 (4FC9799F)
8bf12000 8bf37000   ksecpkg   Fri Jun 01 22:47:40 2012 (4FC97ECC)
99f62000 99f72000   lltdio    Mon Jul 13 19:53:18 2009 (4A5BC8EE)
99f2f000 99f4a000   luafv     Mon Jul 13 19:15:44 2009 (4A5BC020)
99f4a000 99f4da00   mbam      Mon Aug 20 12:49:43 2012 (50326AA7)
8b831000 8b8b6000   mcupdate_GenuineIntel  Sat Nov 20 07:00:54 2010 (4CE7B876)
99f24000 99f2f000   monitor   Mon Jul 13 19:25:58 2009 (4A5BC286)
94a17000 94a24000   mouclass  Mon Jul 13 19:11:15 2009 (4A5BBF13)
99f19000 99f24000   mouhid    Mon Jul 13 19:45:08 2009 (4A5BC704)
8bbcc000 8bbe2000   mountmgr  Sat Nov 20 03:38:09 2010 (4CE788F1)
828c1000 828d3000   mpsdrv    Mon Jul 13 19:52:52 2009 (4A5BC8D4)
828d3000 828f6000   mrxsmb    Tue Apr 26 22:17:20 2011 (4DB77CB0)
828f6000 82931000   mrxsmb10  Fri Jul 08 22:29:57 2011 (4E17BD25)
82931000 8294c000   mrxsmb20  Tue Apr 26 22:17:26 2011 (4DB77CB6)
909d4000 909df000   Msfs      Mon Jul 13 19:11:26 2009 (4A5BBF1E)
8bb0e000 8bb16000   msisadrv  Mon Jul 13 19:11:09 2009 (4A5BBF0D)
8bd31000 8bd5c000   msrpc     Mon Jul 13 19:11:59 2009 (4A5BBF3F)
93770000 9377a000   mssmbios  Mon Jul 13 19:19:25 2009 (4A5BC0FD)
8c1d8000 8c1e8000   mup       Mon Jul 13 19:14:14 2009 (4A5BBFC6)
8be1d000 8bed4000   ndis      Wed Aug 22 10:51:06 2012 (5034F1DA)
97bd0000 97bdb000   ndistapi  Mon Jul 13 19:54:24 2009 (4A5BC930)
97bdb000 97bfd000   ndiswan   Sat Nov 20 05:07:48 2010 (4CE79DF4)
99e7d000 99e8e000   NDProxy   Sat Nov 20 05:07:39 2010 (4CE79DEB)
936d9000 936e7000   netbios   Mon Jul 13 19:53:54 2009 (4A5BC912)
93681000 936b3000   netbt     Sat Nov 20 03:39:22 2010 (4CE7893A)
8bed4000 8bf12000   NETIO     Wed Aug 22 10:51:22 2012 (5034F1EA)
909df000 909ed000   Npfs      Mon Jul 13 19:11:31 2009 (4A5BBF23)
93766000 93770000   nsiproxy  Mon Jul 13 19:12:08 2009 (4A5BBF48)
82e1d000 83230000   nt        Thu Aug 30 10:57:07 2012 (503F7F43)
8bc02000 8bd31000   Ntfs      Fri Aug 31 10:51:12 2012 (5040CF60)
90954000 9095b000   Null      Mon Jul 13 19:11:12 2009 (4A5BBF10)
99e8e000 99eb6000   nvhda32v  Tue Jul 03 11:24:41 2012 (4FF30EB9)
94a3e000 954b2000   nvlddmkm  Tue Oct 02 14:15:55 2012 (506B2F5B)
936ba000 936d9000   pacer     Mon Jul 13 19:53:58 2009 (4A5BC916)
8bb4b000 8bb5c000   partmgr   Sat Mar 17 01:03:08 2012 (4F641B0C)
8bb16000 8bb40000   pci       Sat Nov 20 03:37:57 2010 (4CE788E5)
8bbbe000 8bbcc000   PCIIDEX   Mon Jul 13 19:11:15 2009 (4A5BBF13)
8bdcc000 8bdda000   pcw       Mon Jul 13 19:11:10 2009 (4A5BBF0E)
a001f000 a00b6000   peauth    Mon Jul 13 20:35:44 2009 (4A5BD2E0)
97ae8000 97b17000   portcls   Mon Jul 13 19:51:00 2009 (4A5BC864)
8b8b6000 8b8c7000   PSHED     Mon Jul 13 21:09:36 2009 (4A5BDAD0)
97bb8000 97bd0000   rasl2tp   Mon Jul 13 19:54:33 2009 (4A5BC939)
955cc000 955e4000   raspppoe  Mon Jul 13 19:54:53 2009 (4A5BC94D)
955e4000 955fb000   raspptp   Mon Jul 13 19:54:47 2009 (4A5BC947)
94a00000 94a17000   rassstp   Mon Jul 13 19:54:57 2009 (4A5BC951)
93725000 93766000   rdbss     Sat Nov 20 03:42:44 2010 (4CE78A04)
909bc000 909c4000   RDPCDD    Sat Nov 20 05:22:19 2010 (4CE7A15B)
909c4000 909cc000   rdpencdd  Mon Jul 13 20:01:39 2009 (4A5BCAE3)
909cc000 909d4000   rdprefmp  Mon Jul 13 20:01:41 2009 (4A5BCAE5)
8bf37000 8bf64000   rdyboost  Sat Nov 20 04:00:07 2010 (4CE78E17)
99f72000 99f85000   rspndr    Mon Jul 13 19:53:20 2009 (4A5BC8F0)
97a61000 97ae8000   Rt86win7  Tue Jun 12 09:55:44 2012 (4FD74A60)
9c402000 9c7fb200   RTKVAC    Thu Jun 18 15:36:37 2009 (4A3A9745)
a00b6000 a00c0000   secdrv    Wed Sep 13 09:18:32 2006 (45080528)
97b64000 97b6e000   serenum   Mon Jul 13 19:45:27 2009 (4A5BC717)
936e7000 93701000   serial    Mon Jul 13 19:45:33 2009 (4A5BC71D)
8c1d0000 8c1d8000   spldr     Mon May 11 12:13:47 2009 (4A084EBB)
a013e000 a0190000   srv       Thu Apr 28 22:46:30 2011 (4DBA2686)
a00ee000 a013e000   srv2      Thu Apr 28 22:46:13 2011 (4DBA2675)
a00c0000 a00e1000   srvnet    Thu Apr 28 22:46:08 2011 (4DBA2670)
9c7fc000 9c7fd380   swenum    Mon Jul 13 19:45:08 2009 (4A5BC704)
8c014000 8c160000   tcpip     Wed Oct 03 10:38:23 2012 (506C4DDF)
a00e1000 a00ee000   tcpipreg  Wed Oct 03 11:21:37 2012 (506C5801)
90817000 90823000   TDI       Sat Nov 20 03:39:18 2010 (4CE78936)
90800000 90817000   tdx       Sat Nov 20 03:39:17 2010 (4CE78935)
93714000 93725000   termdd    Sat Nov 20 05:21:10 2010 (4CE7A116)
9b370000 9b379000   TSDDD     unavailable (00000000)
937b5000 937d6000   tunnel    Sat Nov 20 05:06:40 2010 (4CE79DB0)
94a24000 94a32000   umbus     Sat Nov 20 05:00:23 2010 (4CE79C37)
99f17000 99f18700   USBD      Thu Mar 24 22:57:53 2011 (4D8C04B1)
97a52000 97a61000   usbehci   Thu Mar 24 22:57:58 2011 (4D8C04B6)
99e39000 99e7d000   usbhub    Thu Mar 24 22:58:34 2011 (4D8C04DA)
97a07000 97a52000   USBPORT   Thu Mar 24 22:58:05 2011 (4D8C04BD)
955c1000 955cc000   usbuhci   Thu Mar 24 22:57:56 2011 (4D8C04B4)
8bb40000 8bb4b000   vdrvroot  Mon Jul 13 19:46:19 2009 (4A5BC74B)
90982000 9098e000   vga       Mon Jul 13 19:25:50 2009 (4A5BC27E)
9098e000 909af000   VIDEOPRT  Mon Jul 13 19:25:49 2009 (4A5BC27D)
8bb5c000 8bb6c000   volmgr    Sat Nov 20 03:38:06 2010 (4CE788EE)
8bb6c000 8bbb7000   volmgrx   Mon Jul 13 19:11:41 2009 (4A5BBF2D)
8c191000 8c1d0000   volsnap   Sat Nov 20 03:38:13 2010 (4CE788F5)
93701000 93714000   wanarp    Sat Nov 20 05:07:45 2010 (4CE79DF1)
909af000 909bc000   watchdog  Mon Jul 13 19:24:10 2009 (4A5BC21A)
8ba2e000 8baaf000   Wdf01000  Wed Jul 25 22:32:33 2012 (5010AC41)
8baaf000 8babd000   WDFLDR    Wed Jul 25 22:36:38 2012 (5010AD36)
936b3000 936ba000   wfplwf    Mon Jul 13 19:53:51 2009 (4A5BC90F)
9b100000 9b351000   win32k    unavailable (00000000)
8bb05000 8bb0e000   WMILIB    Mon Jul 13 19:11:22 2009 (4A5BBF1A)
99f4e000 99f62000   WudfPf    Wed Jul 25 22:33:43 2012 (5010AC87)

Unloaded modules:
97a61000 97ae8000   Rt86win7.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00087000
97a61000 97ae8000   Rt86win7.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00087000
8297f000 829e9000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0006A000
8294c000 82964000   parport.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00018000
8c1f0000 8c1fd000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
8bfbb000 8bfc6000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000B000
8bfc6000 8bfcf000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
8bfcf000 8bfe0000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00011000

0: kd> [COLOR=Blue]!sysinfo machineid[/COLOR]
Machine ID Information [From Smbios 2.3, DMIVersion 35, Size=1343]
BiosMajorRelease = 8
BiosMinorRelease = 12
BiosVendor = American Megatrends Inc.
BiosVersion = V3.7
BiosReleaseDate = 09/04/2007
SystemManufacturer = MSI
SystemProductName = MS-7236
SystemFamily = To Be Filled By O.E.M.
SystemVersion = 2.0
SystemSKU = To Be Filled By O.E.M.
BaseBoardManufacturer = MSI
BaseBoardProduct = MS-7236
BaseBoardVersion = 2.0

Btw, the big unqualified/missing symbol error at the beginning for USBHUB!_DEVICE_EXTENSION_PDO is because I don't have private Windows symbols, which are only accessible to those with special MSDN access. They are not provided by the public Microsoft Symbol Server.

TBH, this minidump doesn't have all the information I desire, which is why my analysis is pretty broad. Kernel dumps (MEMORY.DMP in Windows directory) are a lot better to work with, though this particular crash doesn't appear all too elusive like some do. Regardless, just perform the recommended suggestions and then we can go from there.

Windbg is a very powerful and robust kernel debugger that has all sorts of items to assist in analyzing both kernel and user mode data. Though without the prior knowledge of Windows OS internal mechanics, programming, etc., then all the options in the world won't help. If you're intrigued about learning more (which, there is plenty to learn) then I recommend you head on over to my article here. It is not a tutorial, as often tutorials can only go so far. Rather, it is a compendium of resources I've collected in my journey in all this to act as a springboard for others to start off and improve. You'll find lists of preferred readings and other miscellaneous items there. Note that the forum it resides on recently changed its URL scheme, so the Table of Content links are bugged, which I plan to fix sometime shortly.

 

[YoYo155]

Simply awesome.

WinDbg is so powerful, I had no idea you could get all that information out of a kernel dump
not even a full memory dump.
Your article is now bookmarked and I will surely take the time to read it.
I am interested in solving issues and BSOD's in particular!

Thank you!

 

[Vir Gnarus]

Well think about it, a kernel dump is all RAM stored on the kernel/driver end. Aside from some extra additional items that are generated during a crash, that's pretty much all that it is. A full memory dump is the entire RAM dumped into a file. Since majority of a system operates on RAM, that's plenty of information to find nearly anything. The paging file is used very sparingly, and even then is managed all in the kernel, which is - you guessed it - in the RAM. Having a full memory is an entire snapshot of a system at a single moment.

Minidumps only harbor data pertaining to the immediate context of the crash, so if it isn't within short range of what caused the crash, it isn't there, which often is why minidumps are rather 'random' on what data they chose or don't chose to retain, making them unreliable. They are however good for pattern analysis in viewing cause of crash for several crashes and pointing out patterned links between em. With one crashdump, though, it's often not enough. Driver Verifier typically helps this case a lot. While most DV-specific info is not stored in a minidump, the fact that (hopefully) DV triggered a crash at the right time on the right suspect is far better than even a full memory dump without it. So I say, when all else fails, use DV.

 

[YoYo155]

Alright after abit of looking around I think I might have come to the saddening conclusion
that I might not be able to run Win 7 smoothly due to lack of drivers (and or BIOS date).

MSI website - http://www.msi.com/product/mb/945P-Neo3.html#/?div=Driver&os=Vista%2032


Is my fear correct?

 

[Vir Gnarus]

The BIOS is independent of the OS, it's just a matter of whether the application used to actually flash the BIOS update is supported by your current OS. Sometimes Vista works for drivers and the BIOS flash app as long as you're using the correct version (x86 or x64). Though yes, it does look like your motherboard has reached its EOL.

However part of me just doesn't think this is caused by some drivers or BIOS that just got "too old", but of some hardware failure due to age that evidently is bugging things out. As stated before, USB ports on a mobo are commonly the first item to start bugging out when a mobo is starting to fail. Check for leaking or bulging capacitors on the mobo, as that can be a way of telling a mobo that's given out.

 

[YoYo155]

Thanks for all your help!
+rep