BSOD

[Onimusha113]

So i have benn haveing BSOD like very random times sometimes it works like for 2 days withouth a single blue screen and other days there are like 2 evry hour.So please help me and post all possible solutions thath pop into ur minds im despreate here.
Im using Windows 7 enterprise 64-bit fully updated and original.

 

[CarlTR6]

Wow! that is a lot of dump files. This could take a while.

In the mean time, please fill out your system information. Go to your User CP at the top of the page, look in the left column and click on Edit system specs. Filling in your specs will help us help you.

You can make this easier by downloading Speccy.

 

[CarlTR6]

I looked at your six most recent dumps, all from today. These dumps indicate hardware problems. Two of the dumps are showing stop error code 101, two show error D1, and two show error code 1E.

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Usual causes: Device driver


STOP 0x00000101: CLOCK_WATCHDOG_TIMEOUT



Usual causes: Device driver, BIOS bug, hardware defect

Let's start with addressing the 101 error code. Please read the following threads and post back with any questions you have.

http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

http://www.sevenforums.com/crashes-...lock-interrupt-bsod-101-error.html#post356791

Follow usasma's advice in that first thread.

I found the following obsolete drivers on your system.

nvm62x64.sys Fri Oct 17 17:01:06 2008 (48F8FD12)
nvstor.sys Wed May 20 02:45:37 2009 (4A13A711)

Both of these are Nvidia chipset drivers. nvm62x64.sys is an Ethernet (network adapter) driver and nvstor.sys is a NVidia storage driver. I would also make sure you have the latest video drivers.

We need your system specs to help you with finding these drivers.

 

[Onimusha113]

amm done updating sepcs and curently doing all the otjer things u mentioned

 

[zigzag3143]

amm done updating sepcs and curently doing all the otjer things u mentioned

Just a few suggestions

1-3 gigs ram for 64 bit enterprise is too little
2-your network driver and RAID driver are often the the cause of BSOD's
3-If you are overclocking STOP

Ken

 

[CarlTR6]

Thank you for filling in your specs. That helps us.

Go to the NVidia site to update those drivers.

 

[Onimusha113]

Updating drivers now i have runed the graphic test and there were no problems
oh and ill add another 1gb ram atleast(even if my pc didnt use up all of the 3 gb ram no matter what i was doing)
Im not overclocking

 

[Onimusha113]

Amm slight problem it seems thath i cant find the drivers for my chipset at least not for windows 7 the newest version i can find is this : NVIDIA DRIVERS 15.23 WHQL i think its the right model eecuse i havent the slightest idea how they come up with the model numbers and so on if this is it then please say so if not can u help me find the right drivers here are the specs:
- Motherboard
Manufacturer Gigabyte Technology Co., Ltd.
Model M52S-S3P
Chipset Vendor NVIDIA
Chipset Model MCP61
Chipset Revision A3
Southbridge Vendor NVIDIA
Southbridge Model MCP61
Southbridge Revision A2

 

[ttran]

Motherboard - GIGABYTE
??:sarc:

 

[Onimusha113]

Thx but there is still no chipset driver for windows 7
P.S. I have noticed thath the blue screens appear more often when im using utorrent and browsing the net at the same time or doing anything else

 

[ttran]

What anti-virus are you using? Do you use Peerblock, which is chosen by many users who use P2P downloader such as Utorrent...I've seen Peerblock cause BSOD

 

[Onimusha113]

no im using avast but still shuld i update the drivers for windows Vista 64

 

[ttran]

If it is the only one avaible, go ahead and run it as compatibility mode
To do that, right click-->Properties-->Choose run in vista mode

Also, I want to consider what Ken suggested, I didn't know if you've ever looked at that and considered:

1-3 gigs ram for 64 bit enterprise is too little
2-your network driver and RAID driver are often the the cause of BSOD's
3-If you are overclocking STOP

I have to admit that your BSODs' cause are mostly there to consider

 

[CarlTR6]

Do as Ken and ttran have suggested.

It appears that your mobo uses an NVidia chipset. I would ask Gigabyte using the link ttran gave you at tech support (create a support ticket) about Windows 7 drivers.

 

[Onimusha113]

Just reporting in that the BSOD have stopped i have updated the chipset with the windows vista version and seems to be working all other tests were good no crashes and have been trying to make a BSOD but it seems thath it is fixed

I thank you all for the help!

 

[ttran]

Great! I like that when someone report their BSODs issue have gone..NICE

 

[CarlTR6]

Just reporting in that the BSOD have stopped i have updated the chipset with the windows vista version and seems to be working all other tests were good no crashes and have been trying to make a BSOD but it seems thath it is fixed

I thank you all for the help!

Good news and you are very welcome. Thank you for reporting your solution. Happy computing.

 

[Onimusha113]

I have some bad news they have started again here are the dumps

 

[CarlTR6]

The very last dump pointed to nvmf6264.sys as the cause. The next to last one gave an error code of 124. This is a hardware error code. Read the link below and start going down the check list.

[2-Int] Stop 0x124 - what it means and what to try

The earliest dump in your list showed and error code of 101. Read the links below regarding error code 101.

http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

http://www.sevenforums.com/crashes-debugging/35427-win-7-clock-interrupt-bsod-101-error.html#post356791

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Usual causes: Device driver


STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

STOP 0x00000101: CLOCK_WATCHDOG_TIMEOUT

Usual causes: Device driver, BIOS bug, hardware defect

As you can see, these are all hardware/hardware related errors.

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Onimusha.zip\070610-23228-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c57000 PsLoadedModuleList = 0xfffff800`02e94e50
Debug session time: Tue Jul  6 08:35:57.916 2010 (GMT-4)
System Uptime: 0 days 0:08:35.789
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff88002f19ef0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\nvmf6264.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
Probably caused by : nvmf6264.sys ( nvmf6264+4d58 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88002f19ef0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
+6257952f01f5da98
fffff880`02f19ef0 08aef10280f8    or      byte ptr [rsi-77FFD0Fh],ch

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eff0e0
 0000000000000000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002f1ae08 -- (.exr 0xfffff88002f1ae08)
ExceptionAddress: fffff8800185c831 (tcpip!IppReceiveHeaderBatch+0x00000000000000d1)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002f1aeb0 -- (.trap 0xfffff88002f1aeb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800196cfc8 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800185c831 rsp=fffff88002f1b040 rbp=fffff8800196c9a0
 r8=0000000000000000  r9=0000000000000001 r10=fffff88002f1b288
r11=fffff88002f1b118 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
tcpip!IppReceiveHeaderBatch+0xd1:
fffff880`0185c831 488b4b08        mov     rcx,qword ptr [rbx+8] ds:ccc3:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d59b1b to fffff80002cc7600

STACK_TEXT:  
fffff880`02f19e38 fffff800`02d59b1b : 00000000`0000001e ffffffff`c0000005 fffff880`02f19ef0 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f19e40 fffff800`02d1a770 : fffffa80`0354bd30 fffff880`041b2e6a fffffa80`00000000 fffffa80`03ce41a0 : nt!KipFatalFilter+0x1b
fffff880`02f19e80 fffff800`02cf5bdc : 00000001`00000002 fffff880`017226a1 00000000`00000003 fffff880`02f1a250 : nt! ?? ::FNODOBFM::`string'+0x95d
fffff880`02f19ec0 fffff800`02ced2ed : fffff800`02e0f4c4 fffff880`02f1b450 00000000`00000000 fffff800`02c57000 : nt!_C_specific_handler+0x8c
fffff880`02f19f30 fffff800`02cf4950 : fffff800`02e0f4c4 fffff880`02f19fa8 fffff880`02f1ae08 fffff800`02c57000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f19f60 fffff800`02d018df : fffff880`02f1ae08 fffff880`02f1a670 fffff880`00000000 00000000`00000011 : nt!RtlDispatchException+0x410
fffff880`02f1a640 fffff800`02cc6c42 : fffff880`02f1ae08 02000000`00000000 fffff880`02f1aeb0 fffffa80`045ce160 : nt!KiDispatchException+0x16f
fffff880`02f1acd0 fffff800`02cc554a : fffffa80`03168f58 fffff880`041b3a6e fffffa80`03165820 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02f1aeb0 fffff880`0185c831 : fffff880`0196c9a0 fffffa80`045ce160 00000000`00000011 fffff880`02f1b090 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f1b040 fffff880`0185b821 : 00000000`00000002 fffffa80`03187000 fffff880`0196c9a0 00000000`04495b01 : tcpip!IppReceiveHeaderBatch+0xd1
fffff880`02f1b120 fffff880`0185a272 : fffffa80`03e10390 00000000`00000000 fffffa80`04495b01 fffff880`00000001 : tcpip!IpFlcReceivePackets+0x651
fffff880`02f1b320 fffff880`018736ba : fffffa80`04495bb0 fffff880`02f1b450 fffffa80`04495bb0 00000000`017d0000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`02f1b400 fffff800`02cd6d4a : fffffa80`045ce030 fffff880`02f16000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff880`02f1b450 fffff880`018730e2 : fffff880`018735e0 fffff880`02f1b560 00000000`00000202 fffff800`02ccc0fa : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`02f1b530 fffff880`017220eb : fffffa80`04495470 00000000`00000000 fffffa80`03ce41a0 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`02f1b5a0 fffff880`016ebfc6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`02f1b610 fffff880`01665ef1 : fffffa80`03ce41a0 00000000`00000002 00000000`00000001 fffff880`041c3f19 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff880`02f1ba90 fffff880`041b0d58 : fffffa80`045ce030 fffff880`02f1bc10 fffffa80`03e72538 00000000`00000001 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1
fffff880`02f1bae0 fffffa80`045ce030 : fffff880`02f1bc10 fffffa80`03e72538 00000000`00000001 fffff880`00000001 : nvmf6264+0x4d58
fffff880`02f1bae8 fffff880`02f1bc10 : fffffa80`03e72538 00000000`00000001 fffff880`00000001 fffff880`02f1bb80 : 0xfffffa80`045ce030
fffff880`02f1baf0 fffffa80`03e72538 : 00000000`00000001 fffff880`00000001 fffff880`02f1bb80 00000000`00000004 : 0xfffff880`02f1bc10
fffff880`02f1baf8 00000000`00000001 : fffff880`00000001 fffff880`02f1bb80 00000000`00000004 fffffa80`040108a0 : 0xfffffa80`03e72538
fffff880`02f1bb00 fffff880`00000001 : fffff880`02f1bb80 00000000`00000004 fffffa80`040108a0 00000000`00000001 : 0x1
fffff880`02f1bb08 fffff880`02f1bb80 : 00000000`00000004 fffffa80`040108a0 00000000`00000001 fffff880`041d6010 : 0xfffff880`00000001
fffff880`02f1bb10 00000000`00000004 : fffffa80`040108a0 00000000`00000001 fffff880`041d6010 fffff880`041ebe40 : 0xfffff880`02f1bb80
fffff880`02f1bb18 fffffa80`040108a0 : 00000000`00000001 fffff880`041d6010 fffff880`041ebe40 00000000`00000000 : 0x4
fffff880`02f1bb20 00000000`00000001 : fffff880`041d6010 fffff880`041ebe40 00000000`00000000 00000000`20020041 : 0xfffffa80`040108a0
fffff880`02f1bb28 fffff880`041d6010 : fffff880`041ebe40 00000000`00000000 00000000`20020041 00000000`00020000 : 0x1
fffff880`02f1bb30 fffff880`041ebe40 : 00000000`00000000 00000000`20020041 00000000`00020000 00000002`00020000 : nvmf6264+0x2a010
fffff880`02f1bb38 00000000`00000000 : 00000000`20020041 00000000`00020000 00000002`00020000 00000000`00000004 : nvmf6264+0x3fe40


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvmf6264+4d58
fffff880`041b0d58 ??              ???

SYMBOL_STACK_INDEX:  12

SYMBOL_NAME:  nvmf6264+4d58

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvmf6264

IMAGE_NAME:  nvmf6264.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b9058a7

FAILURE_BUCKET_ID:  X64_0x1E_nvmf6264+4d58

BUCKET_ID:  X64_0x1E_nvmf6264+4d58

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

1: kd> lmtsmn
start             end                 module name
fffff880`00e16000 fffff880`00e6d000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`03a00000 fffff880`03a8a000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`02de4000 fffff880`02dfa000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`03c49000 fffff880`03c60000   amdk8    amdk8.sys    Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`010c5000 fffff880`010d0000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`0441a000 fffff880`04423000   aswFsBlk aswFsBlk.SYS Mon Jun 28 16:32:34 2010 (4C2906E2)
fffff880`04400000 fffff880`0441a000   aswMonFlt aswMonFlt.sys Mon Jun 28 16:32:58 2010 (4C2906FA)
fffff880`03a8a000 fffff880`03a94000   aswRdr   aswRdr.SYS   Mon Jun 28 16:33:15 2010 (4C29070B)
fffff880`03ab4000 fffff880`03b22000   aswSnx   aswSnx.SYS   Mon Jun 28 16:39:47 2010 (4C290893)
fffff880`03c00000 fffff880`03c23000   aswSP    aswSP.SYS    Mon Jun 28 16:37:34 2010 (4C29080E)
fffff880`03bd7000 fffff880`03be7000   aswTdi   aswTdi.SYS   Mon Jun 28 16:37:54 2010 (4C290822)
fffff880`00f77000 fffff880`00f80000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00f80000 fffff880`00faa000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`044dd000 fffff880`044ff000   AtiHdmi  AtiHdmi.sys  Tue Mar 09 05:08:38 2010 (4B961E26)
fffff880`0489b000 fffff880`04f45000   atikmdag atikmdag.sys Tue Apr 06 21:47:17 2010 (4BBBE425)
fffff880`04000000 fffff880`04036000   atikmpag atikmpag.sys Tue Apr 06 21:23:30 2010 (4BBBDE92)
fffff880`03b2b000 fffff880`03b32000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`03dde000 fffff880`03def000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`035a7000 fffff880`035c5000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`006a0000 fffff960`006c7000   cdd      cdd.dll      unavailable (00000000)
fffff880`0118e000 fffff880`011b8000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00c8e000 fffff880`00d4e000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01416000 fffff880`01446000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c30000 fffff880`00c8e000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`014a4000 fffff880`01517000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`02dd4000 fffff880`02de4000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`044ff000 fffff880`0450d000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`03d3d000 fffff880`03dc0000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`03dc0000 fffff880`03dde000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`03d2e000 fffff880`03d3d000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01400000 fffff880`01416000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0486f000 fffff880`04891000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`0450d000 fffff880`04517000   dump_diskdump dump_diskdump.sys Mon Jul 13 20:01:00 2009 (4A5BCABC)
fffff880`04556000 fffff880`04569000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`04517000 fffff880`04556000   dump_nvstor64 dump_nvstor64.sys Fri Apr 09 05:22:41 2010 (4BBEF1E1)
fffff880`045c3000 fffff880`045cf000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`02c9a000 fffff880`02d8e000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`02d8e000 fffff880`02dd4000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`03c60000 fffff880`03c6d000   fdc      fdc.sys      Mon Jul 13 20:00:54 2009 (4A5BCAB6)
fffff880`0111c000 fffff880`01130000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`04fd5000 fffff880`04fe0000   flpydisk flpydisk.sys Mon Jul 13 20:00:54 2009 (4A5BCAB6)
fffff880`010d0000 fffff880`0111c000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`01528000 fffff880`01532000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`015b8000 fffff880`015f2000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01600000 fffff880`0164a000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02c0e000 fffff800`02c57000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`04188000 fffff880`041ac000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`04036000 fffff880`04092000   HdAudio  HdAudio.sys  Mon Jul 13 20:06:59 2009 (4A5BCC23)
fffff880`04594000 fffff880`045ad000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`045ad000 fffff880`045b5080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`04586000 fffff880`04594000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`034df000 fffff880`035a7000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`017f3000 fffff880`017fc000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`040e9000 fffff880`04107000   i8042prt i8042prt.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`04107000 fffff880`04116000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff800`00bc7000 fffff800`00bd1000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`04f80000 fffff880`04fc3000   ks       ks.sys       Mon Jul 13 20:00:31 2009 (4A5BCA9F)
fffff880`013d5000 fffff880`013ef000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`017b6000 fffff880`017e1000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`02dfa000 fffff880`02dff200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`04444000 fffff880`04459000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`045dd000 fffff880`04600000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c0f000 fffff880`00c1c000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`045cf000 fffff880`045dd000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`04f71000 fffff880`04f80000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`045b6000 fffff880`045c3000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00f5d000 fffff880`00f77000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`035c5000 fffff880`035dd000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`03400000 fffff880`0342d000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`0342d000 fffff880`0347b000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`0347b000 fffff880`0349e000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`03b90000 fffff880`03b9b000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e76000 fffff880`00e80000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01130000 fffff880`0118e000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`03d23000 fffff880`03d2e000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`017e1000 fffff880`017f3000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01664000 fffff880`01756000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`02c24000 fffff880`02c30000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`02c30000 fffff880`02c5f000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0485a000 fffff880`0486f000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`03a9d000 fffff880`03aac000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`011b8000 fffff880`011fd000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01756000 fffff880`017b6000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`03b9b000 fffff880`03bac000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`03d17000 fffff880`03d23000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02c57000 fffff800`03233000   nt       ntkrnlmp.exe Sat Feb 27 02:55:23 2010 (4B88CFEB)
fffff880`01232000 fffff880`013d5000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`03b22000 fffff880`03b2b000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`041ac000 fffff880`041ffa80   nvmf6264 nvmf6264.sys Thu Mar 04 20:04:39 2010 (4B9058A7)
fffff880`00faa000 fffff880`00fd5000   nvstor   nvstor.sys   Wed May 20 02:45:37 2009 (4A13A711)
fffff880`01086000 fffff880`010c5000   nvstor64 nvstor64.sys Fri Apr 09 05:22:41 2010 (4BBEF1E1)
fffff880`00fd5000 fffff880`00ffb000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`03c79000 fffff880`03c96000   parport  parport.sys  Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`00ec0000 fffff880`00ed5000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00e80000 fffff880`00eb3000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00f46000 fffff880`00f4d000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00f4d000 fffff880`00f5d000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`01517000 fffff880`01528000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`062b1000 fffff880`06357000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`04092000 fffff880`040cf000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00c1c000 fffff880`00c30000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`02c00000 fffff880`02c24000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`02c5f000 fffff880`02c7a000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`04f45000 fffff880`04f66000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`02c7a000 fffff880`02c94000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`03cc6000 fffff880`03d17000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`04f66000 fffff880`04f71000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`03b75000 fffff880`03b7e000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`03b7e000 fffff880`03b87000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`03b87000 fffff880`03b90000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`0157e000 fffff880`015b8000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`04459000 fffff880`04471000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`03cac000 fffff880`03cc6000   SCDEmu   SCDEmu.SYS   Mon Apr 12 04:52:25 2010 (4BC2DF49)
fffff880`06357000 fffff880`06362000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`03c6d000 fffff880`03c79000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`01213000 fffff880`01230000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`0165a000 fffff880`01662000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`06525000 fffff880`06596000   spsys    spsys.sys    Mon May 11 13:20:58 2009 (4A085E7A)
fffff880`0645c000 fffff880`064f4000   srv      srv.sys      Tue Dec 08 03:32:55 2009 (4B1E0F37)
fffff880`06200000 fffff880`06269000   srv2     srv2.sys     Mon Jul 13 19:25:02 2009 (4A5BC24E)
fffff880`06362000 fffff880`0638f000   srvnet   srvnet.sys   Tue Dec 08 03:32:26 2009 (4B1E0F1A)
fffff880`01024000 fffff880`01086000   storport storport.sys Mon Jul 13 20:01:18 2009 (4A5BCACE)
fffff880`02c94000 fffff880`02c95480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01801000 fffff880`019fe000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`0638f000 fffff880`063a1000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`03bca000 fffff880`03bd7000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`03bac000 fffff880`03bca000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`03be7000 fffff880`03bfb000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00470000 fffff960`0047a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`03c23000 fffff880`03c49000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`04fc3000 fffff880`04fd5000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`04584000 fffff880`04585f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`04177000 fffff880`04188000   usbehci  usbehci.sys  Sat Oct 24 00:27:33 2009 (4AE28235)
fffff880`04800000 fffff880`0485a000   usbhub   usbhub.sys   Sat Oct 24 00:28:24 2009 (4AE28268)
fffff880`04116000 fffff880`04121000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04121000 fffff880`04177000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`04569000 fffff880`04584000   USBSTOR  USBSTOR.SYS  Mon Jul 13 20:06:34 2009 (4A5BCC0A)
fffff880`00eb3000 fffff880`00ec0000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`03b32000 fffff880`03b40000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`03b40000 fffff880`03b65000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`0164a000 fffff880`0165a000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00ed5000 fffff880`00eea000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00eea000 fffff880`00f46000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01532000 fffff880`0157e000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`01000000 fffff880`0101b000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`03b65000 fffff880`03b75000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00d4e000 fffff880`00df2000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00c00000 fffff880`00c0f000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`03a94000 fffff880`03a9d000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00050000 fffff960`0035f000   win32k   win32k.sys   unavailable (00000000)
fffff880`00e6d000 fffff880`00e76000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`04423000 fffff880`04444000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)
fffff880`064f4000 fffff880`06525000   WUDFRd   WUDFRd.sys   Mon Jul 13 20:06:06 2009 (4A5BCBEE)

Unloaded modules:
fffff880`01446000 fffff880`01454000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01454000 fffff880`0145e000   dump_storpor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0145e000 fffff880`0149d000   dump_nvstor6
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01200000 fffff880`01213000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8003b6e038, b6000000, 181}

Probably caused by : hardware

Followup: MachineOwner

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Onimusha.zip\070610-21621-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c04000 PsLoadedModuleList = 0xfffff800`02e41e50
Debug session time: Tue Jul  6 08:46:35.061 2010 (GMT-4)
System Uptime: 0 days 0:04:47.934
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff800010c1d48, 6, 8, fffff800010c1d48}

Unable to load image \SystemRoot\system32\DRIVERS\nvstor64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvstor64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor64.sys
Probably caused by : nvstor64.sys ( nvstor64+12639 )

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

1: 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: fffff800010c1d48, memory referenced
Arg2: 0000000000000006, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff800010c1d48, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eac0e0
 fffff800010c1d48 

CURRENT_IRQL:  6

FAULTING_IP: 
+6257952f01aad7b4
fffff800`010c1d48 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002f1b720 -- (.trap 0xfffff88002f1b720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880010ea440 rbx=0000000000000000 rcx=fffffa8002e83008
rdx=fffff880031e1440 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800010c1d48 rsp=fffff88002f1b8b8 rbp=fffff88002f1bb00
 r8=0000000000000440  r9=fffffa8002e83008 r10=fffffa8002e83008
r11=fffff880031e1000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffff800`010c1d48 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c73b69 to fffff80002c74600

FAILED_INSTRUCTION_ADDRESS: 
+6257952f01aad7b4
fffff800`010c1d48 ??              ???

STACK_TEXT:  
fffff880`02f1b5d8 fffff800`02c73b69 : 00000000`0000000a fffff800`010c1d48 00000000`00000006 00000000`00000008 : nt!KeBugCheckEx
fffff880`02f1b5e0 fffff800`02c727e0 : fffff880`02f1bbc0 fffffa80`02e83008 00000000`00000001 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b720 fffff800`010c1d48 : fffff880`010cf639 00000000`00000000 00000000`00000001 fffffa80`02e83200 : nt!KiPageFault+0x260
fffff880`02f1b8b8 fffff880`010cf639 : 00000000`00000000 00000000`00000001 fffffa80`02e83200 00000000`00000002 : 0xfffff800`010c1d48
fffff880`02f1b8c0 00000000`00000000 : 00000000`00000001 fffffa80`02e83200 00000000`00000002 00000040`00000000 : nvstor64+0x12639


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvstor64+12639
fffff880`010cf639 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvstor64+12639

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvstor64

IMAGE_NAME:  nvstor64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bbef1e1

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nvstor64+12639

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nvstor64+12639

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

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Onimusha.zip\070610-17206-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c0a000 PsLoadedModuleList = 0xfffff800`02e47e50
Debug session time: Tue Jul  6 07:10:59.565 2010 (GMT-4)
System Uptime: 2 days 13:25:24.437
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff980409f1512, 2, 1, fffff80002c808fb}

Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXRstor+15 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff980409f1512, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c808fb, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb20e0
 fffff980409f1512 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!SwapContext_PatchXRstor+15
fffff800`02c808fb 66894152        mov     word ptr [rcx+52h],ax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  audiodg.exe

TRAP_FRAME:  fffff88008195e40 -- (.trap 0xfffff88008195e40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000fffa4000 rbx=0000000000000000 rcx=fffff980409f14c0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c808fb rsp=fffff88008195fd0 rbp=fffff88008196db0
 r8=fffffa800301e0e8  r9=0000000000000000 r10=fffffffffffffffd
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!SwapContext_PatchXRstor+0x15:
fffff800`02c808fb 66894152        mov     word ptr [rcx+52h],ax ds:7cc8:fffff980`409f1512=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c79b69 to fffff80002c7a600

STACK_TEXT:  
fffff880`08195cf8 fffff800`02c79b69 : 00000000`0000000a fffff980`409f1512 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`08195d00 fffff800`02c787e0 : fffffa80`045b2bd0 fffff880`009e6180 00000000`00000001 fffffa80`045b2000 : nt!KiBugCheckDispatch+0x69
fffff880`08195e40 fffff800`02c808fb : 43e00000`00000001 00000000`00000000 43f00000`00000000 00001f80`00000000 : nt!KiPageFault+0x260
fffff880`08195fd0 fffff800`02c804da : 00000000`00000000 ffffffff`fffffffd fffff880`009e6180 fffffa80`045b2000 : nt!SwapContext_PatchXRstor+0x15
fffff880`08196010 fffff800`02c81752 : ffffffff`00000000 fffffa80`069d3b60 fffff880`00000000 fffff880`00000008 : nt!KiSwapContext+0x7a
fffff880`08196150 fffff800`02c7dc4b : fffffa80`042621a0 fffff8a0`077f3cf0 00000000`00000000 fffff880`08196301 : nt!KiCommitThreadWait+0x1d2
fffff880`081961e0 fffff800`02f76ecf : fffff880`00000003 fffff880`08196520 00000000`00000001 fffffa80`00000006 : nt!KeWaitForMultipleObjects+0x271
fffff880`08196490 fffff800`02f777d6 : fffffa80`045b2001 fffff880`04a1ca99 fffffa80`00000001 00000000`00000000 : nt!ObpWaitForMultipleObjects+0x294
fffff880`08196960 fffff800`02c79853 : fffffa80`069d3b60 00000000`02ecf7a8 fffff880`08196bc8 00000000`00000000 : nt!NtWaitForMultipleObjects+0xe5
fffff880`08196bb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!SwapContext_PatchXRstor+15
fffff800`02c808fb 66894152        mov     word ptr [rcx+52h],ax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!SwapContext_PatchXRstor+15

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0xA_nt!SwapContext_PatchXRstor+15

BUCKET_ID:  X64_0xA_nt!SwapContext_PatchXRstor+15

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

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Onimusha.zip\070610-15880-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e3de50
Debug session time: Tue Jul  6 07:51:00.897 2010 (GMT-4)
System Uptime: 0 days 0:18:56.770
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, fffff88001888f40}

Unable to load image \SystemRoot\system32\DRIVERS\nvmf6264.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
Probably caused by : NETIO.SYS ( NETIO!NetioDereferenceNetBufferListChain+f3 )

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

1: 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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001888f40, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ea80e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip! ?? ::FNODOBFM::`string'+5704
fffff880`01888f40 488b01          mov     rax,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002a55d40 -- (.trap 0xfffff88002a55d40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004bfe8b0 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8004bfe8b1 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001888f40 rsp=fffff88002a55ed0 rbp=0000000000000000
 r8=fffffa8004bfe8b0  r9=00000000000000d0 r10=fffff880009e6e80
r11=fffffa80042cdd30 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
tcpip! ?? ::FNODOBFM::`string'+0x5704:
fffff880`01888f40 488b01          mov     rax,qword ptr [rcx] ds:07ff:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c6fb69 to fffff80002c70600

STACK_TEXT:  
fffff880`02a55bf8 fffff800`02c6fb69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02a55c00 fffff800`02c6e7e0 : fffffa80`031d18e0 fffffa80`042cdb40 fffffa80`042ce024 fffffa80`031fa168 : nt!KiBugCheckDispatch+0x69
fffff880`02a55d40 fffff880`01888f40 : fffffa80`042cdb40 00000000`00000000 00000000`206c644d 00000000`00000011 : nt!KiPageFault+0x260
fffff880`02a55ed0 fffff880`01782173 : 00000000`00000000 00000000`00000001 00000000`00000001 fffff880`0196d9a0 : tcpip! ?? ::FNODOBFM::`string'+0x5704
fffff880`02a55f20 fffff880`0185db26 : fffffa80`042cdb40 fffffa80`042cdc00 00000000`00000011 fffff880`02a55ff0 : NETIO!NetioDereferenceNetBufferListChain+0xf3
fffff880`02a55fa0 fffff880`0185c821 : fffffa80`045c9860 fffffa80`031c8000 fffff880`0196d9a0 00000000`03de8001 : tcpip!IppReceiveHeaderBatch+0x3c7
fffff880`02a56080 fffff880`0185b272 : fffffa80`04196230 00000000`00000000 fffffa80`03de8001 00000000`00000001 : tcpip!IpFlcReceivePackets+0x651
fffff880`02a56280 fffff880`018746ba : fffffa80`03de8010 fffff880`02a563b0 fffffa80`03de8010 fffff880`02a50000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`02a56360 fffff800`02c7fd4a : fffffa80`042cdb40 fffff880`02a51000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff880`02a563b0 fffff880`018740e2 : fffff880`018745e0 fffff880`02a564c0 00000000`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`02a56490 fffff880`0174c0eb : fffffa80`033898d0 00000000`00000000 fffffa80`03d011a0 fffff880`02a56541 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`02a56500 fffff880`01715fc6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`02a56570 fffff880`0168fef1 : fffffa80`03d011a0 00000000`00000002 00000000`00000001 fffff880`03f3df19 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff880`02a569f0 fffff880`03f2ad58 : fffffa80`042cdb40 fffff880`02a56b70 fffffa80`03e53538 00000000`00000001 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1
fffff880`02a56a40 fffffa80`042cdb40 : fffff880`02a56b70 fffffa80`03e53538 00000000`00000001 fffff880`00000001 : nvmf6264+0x4d58
fffff880`02a56a48 fffff880`02a56b70 : fffffa80`03e53538 00000000`00000001 fffff880`00000001 fffffa80`026e1980 : 0xfffffa80`042cdb40
fffff880`02a56a50 fffffa80`03e53538 : 00000000`00000001 fffff880`00000001 fffffa80`026e1980 00000000`00000004 : 0xfffff880`02a56b70
fffff880`02a56a58 00000000`00000001 : fffff880`00000001 fffffa80`026e1980 00000000`00000004 fffffa80`03fedce0 : 0xfffffa80`03e53538
fffff880`02a56a60 fffff880`00000001 : fffffa80`026e1980 00000000`00000004 fffffa80`03fedce0 00000000`00000001 : 0x1
fffff880`02a56a68 fffffa80`026e1980 : 00000000`00000004 fffffa80`03fedce0 00000000`00000001 fffff880`03f50010 : 0xfffff880`00000001
fffff880`02a56a70 00000000`00000004 : fffffa80`03fedce0 00000000`00000001 fffff880`03f50010 fffff880`03f65e40 : 0xfffffa80`026e1980
fffff880`02a56a78 fffffa80`03fedce0 : 00000000`00000001 fffff880`03f50010 fffff880`03f65e40 00000000`00000000 : 0x4
fffff880`02a56a80 00000000`00000001 : fffff880`03f50010 fffff880`03f65e40 00000000`00000000 00000000`200205c8 : 0xfffffa80`03fedce0
fffff880`02a56a88 fffff880`03f50010 : fffff880`03f65e40 00000000`00000000 00000000`200205c8 00000000`00020000 : 0x1
fffff880`02a56a90 fffff880`03f65e40 : 00000000`00000000 00000000`200205c8 00000000`00020000 00000000`00020000 : nvmf6264+0x2a010
fffff880`02a56a98 00000000`00000000 : 00000000`200205c8 00000000`00020000 00000000`00020000 00000000`00000004 : nvmf6264+0x3fe40


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!NetioDereferenceNetBufferListChain+f3
fffff880`01782173 4c8b742440      mov     r14,qword ptr [rsp+40h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  NETIO!NetioDereferenceNetBufferListChain+f3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc18a

FAILURE_BUCKET_ID:  X64_0xD1_NETIO!NetioDereferenceNetBufferListChain+f3

BUCKET_ID:  X64_0xD1_NETIO!NetioDereferenceNetBufferListChain+f3

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

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Onimusha.zip\070610-15553-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c14000 PsLoadedModuleList = 0xfffff800`02e51e50
Debug session time: Tue Jul  6 07:54:58.598 2010 (GMT-4)
System Uptime: 0 days 0:02:43.486
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {61, 0, fffff880009e6180, 1}

Unable to load image \SystemRoot\system32\DRIVERS\nvstor64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvstor64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor64.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009e6180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff800`00b9bfd8 fffff800`02c32443 : 00000000`00000101 00000000`00000061 00000000`00000000 fffff880`009e6180 : nt!KeBugCheckEx
fffff800`00b9bfe0 fffff800`02c8ccf7 : 00000000`00000000 fffff800`00000001 00000000`00026160 fffff880`04ab5960 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff800`00b9c070 fffff800`031fa895 : fffff800`0321f460 fffff800`00b9c220 fffff800`0321f460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`00b9c170 fffff800`02c80af3 : 00000000`3dc1f8a4 fffff800`00b9c201 fffffa80`02496540 fffffa80`03008c20 : hal!HalpHpetClockInterrupt+0x8d
fffff800`00b9c1a0 fffff800`02c46162 : fffff800`00b9c390 fffff880`01658093 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff800`00b9c330 fffff800`02d351da : fffff800`02dfee80 fffff800`00b9c360 00000000`00000000 fffffa80`03581e00 : nt!KxWaitForSpinLockAndAcquire+0x12
fffff800`00b9c360 fffff880`0103c934 : 00000000`e95477f9 00000000`00000000 fffffa80`0300e001 00000000`00000000 : nt!KeAcquireInterruptSpinLock+0x7a
fffff800`00b9c3b0 fffff880`01048565 : 00000000`00000000 fffffa80`0300e001 00000000`00000000 fffff800`02c90cf0 : storport!RaidAdapterAcquireInterruptLock+0x74
fffff800`00b9c3e0 fffff880`0104928f : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`02e0cc40 : storport!RaidAdapterFindUnit+0x35
fffff800`00b9c410 fffff880`01099c0d : 00000000`00000000 fffff800`02c90bf0 00000000`00000000 00000000`00000000 : storport!StorPortGetLogicalUnit+0x2f
fffff800`00b9c440 00000000`00000000 : fffff800`02c90bf0 00000000`00000000 00000000`00000000 fffffa80`02f96000 : nvstor64+0x4c0d


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

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