I get bluescreens too with my podx3
Well, i'm not a developer just followed basic instructions to read the memory dump
Don't know, there is a problem with the symbols path but hopefully it gives you a hint
#############################################################################
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols ;C:\symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a67000 PsLoadedModuleList = 0xfffff800`02ca4e50
Debug session time: Fri Oct 23 22:27:46.846 2009 (GMT+2)
System Uptime: 0 days 1:45:24.750
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {ffffffffc0000005, fffff88005909e21, fffff88005748998, fffff880057481f0}
*** ERROR: Module load completed but symbols could not be loaded for L6PODX364.sys
Probably caused by : L6PODX364.sys ( L6PODX364+19e21 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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: fffff88005909e21, The address that the exception occurred at
Arg3: fffff88005748998, Exception Record Address
Arg4: fffff880057481f0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
L6PODX364+19e21
fffff880`05909e21 66814b0a0020 or word ptr [rbx+0Ah],2000h
EXCEPTION_RECORD: fffff88005748998 -- (.exr 0xfffff88005748998)
ExceptionAddress: fffff88005909e21 (L6PODX364+0x0000000000019e21)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 000000000000000a
Attempt to write to address 000000000000000a
CONTEXT: fffff880057481f0 -- (.cxr 0xfffff880057481f0)
rax=fffffa8006309010 rbx=0000000000000000 rcx=fffffa80070d93a8
rdx=0000000000000000 rsi=fffffa8006309010 rdi=fffffa80070d90b8
rip=fffff88005909e21 rsp=fffff88005748bd0 rbp=fffff8800544d168
r8=fffffa800643fd00 r9=0000000000000000 r10=ffff000000000000
r11=0000000000000000 r12=fffffa80062d6bd0 r13=fffffa8006318de0
r14=0000000000000000 r15=fffff80000b96080
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010282
L6PODX364+0x19e21:
fffff880`05909e21 66814b0a0020 or word ptr [rbx+0Ah],2000h ds:002b:00000000`0000000a=????
Resetting default scope
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 000000000000000a
WRITE_ADDRESS: 000000000000000a
FOLLOWUP_IP:
L6PODX364+19e21
fffff880`05909e21 66814b0a0020 or word ptr [rbx+0Ah],2000h
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffff880058f310f to fffff88005909e21
STACK_TEXT:
fffff880`05748bd0 fffff880`058f310f : fffffa80`070d90b8 00000000`00000080 fffffa80`052059e0 00000000`00000000 : L6PODX364+0x19e21
fffff880`05748cc0 fffff800`02d7c166 : 00000000`039d673c fffff800`02c51e80 fffffa80`05214630 00000000`00000001 : L6PODX364+0x310f
fffff880`05748d00 fffff800`02ab7486 : fffff800`02c51e80 fffffa80`05214630 fffffa80`0521a680 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`05748d40 00000000`00000000 : fffff880`05749000 fffff880`05743000 fffff880`057488e0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: L6PODX364+19e21
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: L6PODX364
IMAGE_NAME: L6PODX364.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ad8b23d
STACK_COMMAND: .cxr 0xfffff880057481f0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_L6PODX364+19e21
BUCKET_ID: X64_0x7E_L6PODX364+19e21
Followup: MachineOwner
---------
0: kd> lmvm L6PODX364
start end module name
fffff880`058f0000 fffff880`059bbe00 L6PODX364 (no symbols)
Loaded symbol image file: L6PODX364.sys
Image path: \SystemRoot\System32\Drivers\L6PODX364.sys
Image name: L6PODX364.sys
Timestamp: Fri Oct 16 19:49:49 2009 (4AD8B23D)
CheckSum: 000D0274
ImageSize: 000CBE00
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
