- Joined
- Sep 1, 2011
- Messages
- 1
- Reaction score
- 0
Hi, I've been getting BSODs and I finally decided to get some help. Here are some of the recent .dmps
Attachments
-
54.8 KB Views: 393
This usually happens after the installation of a faulty/corrupt device driver, service, or BIOS. If the BSOD occurs on boot, use the F8 menu to try either Safe mode, or last known good configuration as your option. Check your event viewer for any critical warning or error messages, and you can also try disabling the memory cache for the BIOS. The bugcheck points towards your dokan.sys driver though.*******************************************************************************
* *
* 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: 0000000000000000, 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: fffff800038b086e, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003afa0e0
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!ExDeleteResourceLite+ce
fffff800`038b086e 488908 mov qword ptr [rax],rcx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: LiquesceSvc.ex
TRAP_FRAME: fffff88009952620 -- (.trap 0xfffff88009952620)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa801107fb60 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800038b086e rsp=fffff880099527b0 rbp=fffff88009952c60
r8=0000000000000000 r9=0000000000000000 r10=fffff88003171be0
r11=fffffa801155f9a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!ExDeleteResourceLite+0xce:
fffff800`038b086e 488908 mov qword ptr [rax],rcx ds:f990:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800038c3469 to fffff800038c3f00
STACK_TEXT:
fffff880`099524d8 fffff800`038c3469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`099524e0 fffff800`038c20e0 : 80000000`00000000 fffffa80`1271ce68 cdfe6004`00000000 00000000`0000401b : nt!KiBugCheckDispatch+0x69
fffff880`09952620 fffff800`038b086e : 00000000`000007ff 00000000`00000060 fffffa80`1155f9f0 00000000`00000000 : nt!KiPageFault+0x260
fffff880`099527b0 fffff880`07db4918 : fffffa80`112bcdc0 fffff880`09952c60 fffffa80`112bcdc0 fffffa80`112bcdc0 : nt!ExDeleteResourceLite+0xce
fffff880`09952810 fffffa80`112bcdc0 : fffff880`09952c60 fffffa80`112bcdc0 fffffa80`112bcdc0 fffffa80`111011d0 : dokan+0x3918
fffff880`09952818 fffff880`09952c60 : fffffa80`112bcdc0 fffffa80`112bcdc0 fffffa80`111011d0 fffffa80`00000001 : 0xfffffa80`112bcdc0
fffff880`09952820 fffffa80`112bcdc0 : fffffa80`112bcdc0 fffffa80`111011d0 fffffa80`00000001 fffff880`09952c60 : 0xfffff880`09952c60
fffff880`09952828 fffffa80`112bcdc0 : fffffa80`111011d0 fffffa80`00000001 fffff880`09952c60 fffff880`07db5084 : 0xfffffa80`112bcdc0
fffff880`09952830 fffffa80`111011d0 : fffffa80`00000001 fffff880`09952c60 fffff880`07db5084 fffffa80`1271ccd0 : 0xfffffa80`112bcdc0
fffff880`09952838 fffffa80`00000001 : fffff880`09952c60 fffff880`07db5084 fffffa80`1271ccd0 fffffa80`11101080 : 0xfffffa80`111011d0
fffff880`09952840 fffff880`09952c60 : fffff880`07db5084 fffffa80`1271ccd0 fffffa80`11101080 fffffa80`112bcdc0 : 0xfffffa80`00000001
fffff880`09952848 fffff880`07db5084 : fffffa80`1271ccd0 fffffa80`11101080 fffffa80`112bcdc0 00000000`00000000 : 0xfffff880`09952c60
fffff880`09952850 fffffa80`1271ccd0 : fffffa80`11101080 fffffa80`112bcdc0 00000000`00000000 fffffa80`116a4eb0 : dokan+0x4084
fffff880`09952858 fffffa80`11101080 : fffffa80`112bcdc0 00000000`00000000 fffffa80`116a4eb0 fffffa80`0d74ce10 : 0xfffffa80`1271ccd0
fffff880`09952860 fffffa80`112bcdc0 : 00000000`00000000 fffffa80`116a4eb0 fffffa80`0d74ce10 00000000`c0000034 : 0xfffffa80`11101080
fffff880`09952868 00000000`00000000 : fffffa80`116a4eb0 fffffa80`0d74ce10 00000000`c0000034 fffffa80`0d74cee0 : 0xfffffa80`112bcdc0
STACK_COMMAND: kb
FOLLOWUP_IP:
dokan+3918
fffff880`07db4918 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: dokan+3918
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dokan
IMAGE_NAME: dokan.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d2b0059
FAILURE_BUCKET_ID: X64_0xA_dokan+3918
BUCKET_ID: X64_0xA_dokan+3918
Followup: MachineOwner
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.