I've called a friend to take a look at that. So, while we wait for his reply. Here are the output of your recent dump files.
As you can see, it appears to be caused by dokan.sys. *I have no idea what software it belongs to but,
I would recommend you to uninstall any related software (similar to the sys file name) that you are aware of.
Please do not use any Adobe software while troubleshooting.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {13d448, 2, 1, fffff800022f144f}
*** WARNING: Unable to verify timestamp for dokan.sys
*** ERROR: Module load completed but symbols could not be loaded for dokan.sys
Probably caused by : dokan.sys ( dokan+a4b8 )
Followup: MachineOwner
---------
*******************************************************************************
* *
* 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: 000000000013d448, 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: fffff800022f144f, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002507100
GetUlongFromAddress: unable to read from fffff800025071c0
000000000013d448 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
nt!ExTryAcquireSpinLockExclusiveAtDpcLevel+2f
fffff800`022f144f f00fb111 lock cmpxchg dword ptr [rcx],edx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: lightroom.exe
TRAP_FRAME: fffff8800db66560 -- (.trap 0xfffff8800db66560)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000013d448
rdx=0000000080000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800022f144f rsp=fffff8800db666f0 rbp=000000000013d400
r8=0000000000000000 r9=fffff88001ece180 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!ExTryAcquireSpinLockExclusiveAtDpcLevel+0x2f:
fffff800`022f144f f00fb111 lock cmpxchg dword ptr [rcx],edx ds:00000000`0013d448=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800022d7569 to fffff800022d7fc0
STACK_TEXT:
fffff880`0db66418 fffff800`022d7569 : 00000000`0000000a 00000000`0013d448 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0db66420 fffff800`022d61e0 : 00000000`00000100 fffffa80`12e1b0b0 fffffa80`12e1b060 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`0db66560 fffff800`022f144f : 00000000`00000000 fffff800`0245f580 00000000`0000ff90 fffff800`022f7d6d : nt!KiPageFault+0x260
fffff880`0db666f0 fffff800`02319136 : fffffa80`11565860 00000000`00000000 fffffa80`00000258 00000000`00000801 : nt!ExTryAcquireSpinLockExclusiveAtDpcLevel+0x2f
fffff880`0db66730 fffff800`0231962d : fffffa80`0ce94080 fffff880`0db66920 00000000`00000000 fffff880`0db66810 : nt!MiComputeFlushRange+0xae
fffff880`0db667c0 fffff800`02318d3c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmFlushSection+0x49
fffff880`0db66880 fffff880`0bd874b8 : fffffa80`13335250 fffffa80`00000000 00000000`00000000 fffffa80`0ffb65b0 : nt!CcFlushCache+0x7bc
fffff880`0db66980 fffffa80`13335250 : fffffa80`00000000 00000000`00000000 fffffa80`0ffb65b0 fffffa80`11146260 : dokan+0xa4b8
fffff880`0db66988 fffffa80`00000000 : 00000000`00000000 fffffa80`0ffb65b0 fffffa80`11146260 fffffa80`12e1b168 : 0xfffffa80`13335250
fffff880`0db66990 00000000`00000000 : fffffa80`0ffb65b0 fffffa80`11146260 fffffa80`12e1b168 fffffa80`0f9ec1e0 : 0xfffffa80`00000000
STACK_COMMAND: kb
FOLLOWUP_IP:
dokan+a4b8
fffff880`0bd874b8 ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: dokan+a4b8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dokan
IMAGE_NAME: dokan.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d2b0059
FAILURE_BUCKET_ID: X64_0xA_dokan+a4b8
BUCKET_ID: X64_0xA_dokan+a4b8
Followup: MachineOwner
---------
3: kd> lmvm dokan
start end module name
fffff880`0bd7d000 fffff880`0bd9d000 dokan T (no symbols)
Loaded symbol image file: dokan.sys
Image path: dokan.sys
Image name: dokan.sys
Timestamp: Mon Jan 10 18:49:29 2011 (4D2B0059)
CheckSum: 000244E4
ImageSize: 00020000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Another dump files comes with bug check 100007E which has no usual causes but looks like it's graphics related.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88007423d78, fffff8800945d688, fffff8800945cee0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88007423d78, The address that the exception occurred at
Arg3: fffff8800945d688, Exception Record Address
Arg4: fffff8800945cee0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c
fffff880`07423d78 4939040a cmp qword ptr [r10+rcx],rax
EXCEPTION_RECORD: fffff8800945d688 -- (.exr 0xfffff8800945d688)
ExceptionAddress: fffff88007423d78 (dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+0x000000000000004c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff8800945cee0 -- (.cxr 0xfffff8800945cee0)
rax=00000000000250d9 rbx=fffff8a004a20e50 rcx=f7fff8a00e736b28
rdx=0000000000000004 rsi=0000000000000004 rdi=0000000000000009
rip=fffff88007423d78 rsp=fffff8800945d8c8 rbp=0000000000000000
r8=0000000000000004 r9=0000000000000009 r10=0000000000000020
r11=fffffa800ea4a3c8 r12=0000000000000001 r13=0000000000000000
r14=fffffa800fad1790 r15=00000000000000a3
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+0x4c:
fffff880`07423d78 4939040a cmp qword ptr [r10+rcx],rax ds:002b:f7fff8a0`0e736b48=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800024ba100
GetUlongFromAddress: unable to read from fffff800024ba1c0
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c
fffff880`07423d78 4939040a cmp qword ptr [r10+rcx],rax
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff8800742102a to fffff88007423d78
STACK_TEXT:
fffff880`0945d8c8 fffff880`0742102a : fffff8a0`04a20e50 fffffa80`0dbb1710 fffffa80`0ea49000 fffffa80`0fad1790 : dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+0x4c
fffff880`0945d8d0 fffff880`0741e8af : 00000000`00000000 fffffa80`0f441008 00000000`0000009a fffffa80`0d1f7020 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xda
fffff880`0945d910 fffff880`0743865d : 00000000`00000000 fffff8a0`0df4c660 fffffa80`00000000 fffffa80`0fad1790 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`0945dae0 fffff880`07438398 : fffff880`01e61f40 fffff880`07437d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`0945dcd0 fffff880`07437e96 : 00000000`00000000 fffffa80`0fe95840 00000000`00000080 fffffa80`0deb3410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`0945dd00 fffff800`02521e5a : 00000000`0300f301 fffffa80`0e754b50 fffffa80`0ca1cb30 fffffa80`0e754b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0945dd40 fffff800`0227bd26 : fffff880`01e5d180 fffffa80`0e754b50 fffff880`01e67fc0 00000000`2cddb000 : nt!PspSystemThreadStartup+0x5a
fffff880`0945dd80 00000000`00000000 : fffff880`0945e000 fffff880`09458000 fffff880`0945d680 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
STACK_COMMAND: .cxr 0xfffff8800945cee0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c
Followup: MachineOwner
---------
Perform a fresh installation of your video card drivers. Follow this quote:
Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program:
Drivers:
AMD Driver Autodetect
Please select custom install and de-select "Catalyst Control Manager - CCC" during installation.
Check for an update on your BIOS version:
Code:
Verze systému BIOS/Datum Award Software International, Inc. F8, 25.5.2010
Video Card - Stress Test with Furmark:
Warning
Video Card Stress test with Furmark can damage your GPU if temperatures are not watched.
Monitor your temps during this test with programs like HWMonitor or Speccy:
Then test video memory with this app:
Test for 20 passes at a minimum.
Daemon Tools:
Code:
DAEMON Tools Lite "c:\program files (x86)\daemon tools lite\dtlite.exe" -autorun shrap-PC\shrap HKU\S-1-5-21-102527367-1805033130-1276282498-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Please uninstall DAEMON Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.
Code:
Start Menu\Programs\Avira\AntiVir Desktop Public:Start Menu\Programs\Avira\AntiVir Desktop Public
Not the best security software to have, please remove with its removal tool:
Microsoft Security Essentials.
Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-
Warning
Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.
Run a full scan with both (separately) once downloaded, installed and updated.
Perform a System File Check:
- Click on the start
- Type CMD on Search
- Left click and Run as Administrator
- Type SFC /scannow
Full tutorial here:
Disk Check on your hard drive for file system errors and bad sectors on it:
Reduce items at start-up. Nothing except anti-virus is required plus improves the time for logging in windows.
Let us know the results.