Windows 7: BSOD after driver verifier

BuzzFuzz · 04 Nov 2011

Plz check, thanks for more infos....

It's ntoskrnl.exe
Searching forum and no proper solution.

Startup repair doesn't help - can't fix the problem
sfc /scann... no errors
chkdsk /r ... no errors

Capt.Jack Sparrow · 04 Nov 2011

Quote: Originally Posted by BuzzFuzz

Plz check, thanks for more infos....

It's ntoskrnl.exe
Searching forum and no proper solution.

Startup repair doesn't help - can't fix the problem
sfc /scann... no errors
chkdsk /r ... no errors

Hello there!

Seems like ATITool64.sys is causing to crashes. Please uninstall it and see if the system crashes again. Then turned off Drivers Verifier

Bugcheck:

Code:

DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (d6)
N bytes of memory was allocated and more than N bytes are being referenced.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff980014ab000, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff88003ff6192, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030af100
 fffff980014ab000 

FAULTING_IP: 
ATITool64+6192
fffff880`03ff6192 66833800        cmp     word ptr [rax],0

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD6

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880033c3af0 -- (.trap 0xfffff880033c3af0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff980014ab000 rbx=0000000000000000 rcx=fffff88003ff60fb
rdx=0000000000000046 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003ff6192 rsp=fffff880033c3c80 rbp=0000000000000010
 r8=0000000000000000  r9=fffff880033c4210 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
ATITool64+0x6192:
fffff880`03ff6192 66833800        cmp     word ptr [rax],0 ds:fffff980`014ab000=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e289fc to fffff80002e7cc40

STACK_TEXT:  
fffff880`033c3988 fffff800`02e289fc : 00000000`00000050 fffff980`014ab000 00000000`00000000 fffff880`033c3af0 : nt!KeBugCheckEx
fffff880`033c3990 fffff800`02e7ad6e : 00000000`00000000 fffff980`014ab000 00000000`00000000 fffff980`014aaff0 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`033c3af0 fffff880`03ff6192 : 00000001`0000000b 00000170`00000000 ffff0001`0000000b 00000170`0000000d : nt!KiPageFault+0x16e
fffff880`033c3c80 00000001`0000000b : 00000170`00000000 ffff0001`0000000b 00000170`0000000d fffff880`033c5000 : ATITool64+0x6192
fffff880`033c3c88 00000170`00000000 : ffff0001`0000000b 00000170`0000000d fffff880`033c5000 fffff880`033bf000 : 0x1`0000000b
fffff880`033c3c90 ffff0001`0000000b : 00000170`0000000d fffff880`033c5000 fffff880`033bf000 00000007`00000010 : 0x170`00000000
fffff880`033c3c98 00000170`0000000d : fffff880`033c5000 fffff880`033bf000 00000007`00000010 ffffffff`00000000 : 0xffff0001`0000000b
fffff880`033c3ca0 fffff880`033c5000 : fffff880`033bf000 00000007`00000010 ffffffff`00000000 00000000`00000000 : 0x170`0000000d
fffff880`033c3ca8 fffff880`033bf000 : 00000007`00000010 ffffffff`00000000 00000000`00000000 fffff880`033c4210 : 0xfffff880`033c5000
fffff880`033c3cb0 00000007`00000010 : ffffffff`00000000 00000000`00000000 fffff880`033c4210 fffff880`00000001 : 0xfffff880`033bf000
fffff880`033c3cb8 ffffffff`00000000 : 00000000`00000000 fffff880`033c4210 fffff880`00000001 fffff800`030a6300 : 0x7`00000010
fffff880`033c3cc0 00000000`00000000 : fffff880`033c4210 fffff880`00000001 fffff800`030a6300 00000000`00000000 : 0xffffffff`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ATITool64+6192
fffff880`03ff6192 66833800        cmp     word ptr [rax],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  ATITool64+6192

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ATITool64

IMAGE_NAME:  ATITool64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  46b9f272

FAILURE_BUCKET_ID:  X64_0xD6_VRF_ATITool64+6192

BUCKET_ID:  X64_0xD6_VRF_ATITool64+6192

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

3: kd> lmvm ATITool64
start             end                 module name
fffff880`03ff0000 fffff880`03ffe000   ATITool64 T (no symbols)           
    Loaded symbol image file: ATITool64.sys
    Image path: \SystemRoot\system32\DRIVERS\ATITool64.sys
    Image name: ATITool64.sys
    Timestamp:        Wed Aug 08 22:12:26 2007 (46B9F272)
    CheckSum:         0001540C
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

BuzzFuzz · 04 Nov 2011

Is it possible because of this file comes lag in game?

Capt.Jack Sparrow · 05 Nov 2011

Quote: Originally Posted by BuzzFuzz

Is it possible because of this file comes lag in game?

Not sure. I think the lagging is caused by Driver Verifier.

**cluberti** · 05 Nov 2011

Yes indeed. If you aren't surgical with what to watch, and rather go for a more blanket approach, you will introduce latency. Driver verifier adds some overhead, so that if something crashes, it does catch it - this takes system resources, both memory and CPU cycles.

Windows 7: BSOD after driver verifier

BSOD after driver verifier problems?