e-son, den August 29, 2009, 09:23, skrev:
Ok... släng gärna in en färsk analys nu när bios och chipset är uppdaterat, så hoppas vi att Stenis får syn på den...! 
Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*C:\Users\Thor\WindowsDebuggingTools*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0x82852000 PsLoadedModuleList = 0x82969c70
Debug session time: Sat Aug 29 09:54:22.545 2009 (GMT+2)
System Uptime: 0 days 0:05:30.279
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffdd00c). Type ".hh dbgerr001" for details
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {0, 0, 0, 0}
Page 7d127 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 7ffdd00c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffdd00c). Type ".hh dbgerr001" for details
Probably caused by : usbscan.sys ( usbscan!USTransfer+54d )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
Page 7d127 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 7ffdd00c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffdd00c). Type ".hh dbgerr001" for details
BUGCHECK_STR: 0x7f_0
TRAP_FRAME: a357db6c -- (.trap 0xffffffffa357db6c)
ErrCode = 00000000
eax=00000004 ebx=af2d45b8 ecx=8a5fa4d0 edx=00000000 esi=859f7008 edi=00000002
eip=9d61cd67 esp=a357dbe0 ebp=a357dc18 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
usbscan!USTransfer+0x54d:
9d61cd67 f775ec div eax,dword ptr [ebp-14h] ss:0010:a357dc04=00000000
Resetting default scope
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 1
LAST_CONTROL_TRANSFER: from 82ad0836 to 8291fadf
STACK_TEXT:
a357db0c 82ad0836 0000007f ff7e58f0 9d61cd67 nt!KeBugCheck+0x14
a357db60 8289da08 a357db6c a357dc18 9d61cd67 nt!Ki386CheckDivideByZeroTrap+0x44
a357db60 9d61cd67 a357db6c a357dc18 9d61cd67 nt!KiTrap00+0x88
a357dc18 9d61d146 8a5fa4d0 af255e28 00000002 usbscan!USTransfer+0x54d
a357dc4c 9d61aa98 8a5fa4d0 00000078 8ad3fa78 usbscan!USWrite+0x98
a357dc6c 82896976 8a5fa4d0 af255e28 af255e28 usbscan!USDispatchIO+0xe4
a357dc84 82a986a1 00000004 af255e28 af255f4c nt!IofCallDriver+0x63
a357dca4 82a655a0 8a5fa4d0 8ad3fa78 00000001 nt!IopSynchronousServiceTail+0x1d9
a357dd38 8289cc7a 8a5fa4d0 000002f0 00000000 nt!NtWriteFile+0x6fc
a357dd38 770d5e74 8a5fa4d0 000002f0 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0220f6c0 00000000 00000000 00000000 00000000 0x770d5e74
STACK_COMMAND: kb
FOLLOWUP_IP:
usbscan!USTransfer+54d
9d61cd67 f775ec div eax,dword ptr [ebp-14h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: usbscan!USTransfer+54d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbscan
IMAGE_NAME: usbscan.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47919531
FAILURE_BUCKET_ID: 0x7f_0_usbscan!USTransfer+54d
BUCKET_ID: 0x7f_0_usbscan!USTransfer+54d
Followup: MachineOwner
---------
3: kd> lmvm usbscan
start end module name
9d615000 9d622000 usbscan (pdb symbols) c:\users\thor\windowsdebuggingtools\usbscan.pdb\AF4CFC41681441DF957308B70F43DA671\usbscan.pdb
Loaded symbol image file: usbscan.sys
Image path: \SystemRoot\system32\DRIVERS\usbscan.sys
Image name: usbscan.sys
Timestamp: Sat Jan 19 07:14:09 2008 (47919531)
CheckSum: 00010380
ImageSize: 0000D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Det verkar som om det är drivrutinen till skannern som krånglar.
