• We've upgraded our forums. Please post any issues/requests in this thread.

ATITool64.sys causes BSOD while Booting Windows

WarSlash

New Member
Joined
May 17, 2008
Messages
1 (0.00/day)
Likes
0
#1
Hey guys,

I got a BSOD "PAGE_FAULT_IN_NONPAGED_AREA", caused by ATITools' Driver, while the machine was booting Windows Vista x64. I made a Debugger-Log for you. I hope you can fix the bugs in the driver file for the near future!

Today was the first time, when I got this error!

Machine specs:
Windows Vista x64 SP1 with last patches via Windows Update
C2D E6600@2,66 GHz
Asus P5W DH Deluxe 2004 BIOS@ FSB 333
2x 2048 GEIL DDR-2 @ 667 MHz
Leadtek 8800 GTX with Geforce-Driver 175.16

Used Version of ATITool: 0.27 Beta 4

I have to say that the system is overclocked, but it was verified to be stable. So this cannot be the reason for this bluescreen. And last but not least this is a beta release! ;)

Code:
Microsoft (R) Windows Debugger  Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\WarSlash\Desktop\Mini051708-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff800`0240e000 PsLoadedModuleList = 0xfffff800`025d3db0
Debug session time: Sat May 17 18:46:52.724 2008 (GMT+2)
System Uptime: 0 days 0:00:07.489
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88000724000, 0, fffffa600271e192, 0}

Unable to load image \SystemRoot\system32\DRIVERS\ATITool64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ATITool64.sys
*** ERROR: Module load completed but symbols could not be loaded for ATITool64.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ATITool64.sys ( ATITool64+6192 )

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

0: kd> .sympath SRV*c:\ temp*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\ temp*http://msdl.microsoft.com/download/symbols
0: kd> .reload /f
Loading Kernel Symbols
...Unable to load image \SystemRoot\system32\mcupdate_GenuineIntel.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mcupdate_GenuineIntel.dll
*** ERROR: Module load completed but symbols could not be loaded for mcupdate_GenuineIntel.dll
......Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
............Unable to load image \SystemRoot\SysWOW64\drivers\hotcore3.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for hotcore3.sys
*** ERROR: Module load completed but symbols could not be loaded for hotcore3.sys
..Unable to load image \SystemRoot\system32\DRIVERS\iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
..............*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
........Unable to load image \SystemRoot\System32\Drivers\dump_iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dump_iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_iaStor.sys
..Unable to load image \SystemRoot\system32\DRIVERS\ATITool64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ATITool64.sys
*** ERROR: Module load completed but symbols could not be loaded for ATITool64.sys

Loading User Symbols
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88000724000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffffa600271e192, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002637080
 fffff88000724000 

FAULTING_IP: 
ATITool64+6192
fffffa60`0271e192 ??              ???

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffffa60019f4bd0 -- (.trap 0xfffffa60019f4bd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88000724000 rbx=fffff8800063aae0 rcx=fffffa600271e0fb
rdx=0000000000000046 rsi=0000000000000000 rdi=000000000000000a
rip=fffffa600271e192 rsp=fffffa60019f4d60 rbp=0000000000000010
 r8=0000000000000000  r9=fffffa60019f52f0 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
ATITool64+0x6192:
fffffa60`0271e192 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002472371 to fffff80002463390

STACK_TEXT:  
fffffa60`019f4ad8 fffff800`02472371 : 00000000`00000050 fffff880`00724000 00000000`00000000 fffffa60`019f4bd0 : nt!KeBugCheckEx
fffffa60`019f4ae0 fffff800`02461f19 : 00000000`00000000 fffff800`69634d43 00000000`00000000 fffff880`00723ff0 : nt!MmAccessFault+0x1371
fffffa60`019f4bd0 fffffa60`0271e192 : fffff880`0063aab0 fffff880`0063aab0 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x119
fffffa60`019f4d60 fffff880`0063aab0 : fffff880`0063aab0 00000000`00000000 00000000`00000001 fffffa80`03ca9080 : ATITool64+0x6192
fffffa60`019f4d68 fffff880`0063aab0 : 00000000`00000000 00000000`00000001 fffffa80`03ca9080 fffff800`0246afa9 : 0xfffff880`0063aab0
fffffa60`019f4d70 00000000`00000000 : 00000000`00000001 fffffa80`03ca9080 fffff800`0246afa9 00000007`00000010 : 0xfffff880`0063aab0
fffffa60`019f4d78 00000000`00000001 : fffffa80`03ca9080 fffff800`0246afa9 00000007`00000010 ffffffff`00000000 : 0x0
fffffa60`019f4d80 fffffa80`03ca9080 : fffff800`0246afa9 00000007`00000010 ffffffff`00000000 00000000`00000000 : 0x1
fffffa60`019f4d88 fffff800`0246afa9 : 00000007`00000010 ffffffff`00000000 00000000`00000000 fffffa60`019f52f0 : 0xfffffa80`03ca9080
fffffa60`019f4d90 fffff800`026e1c5e : 00000000`00000000 fffffa80`03ca9080 fffffa80`03cab040 00000000`00000000 : nt!ObfDereferenceObject+0x219
fffffa60`019f4e20 fffff800`026e1e04 : fffff880`00001df0 fffff880`00001d00 00000000`00000000 00000000`00000028 : nt!ObpCloseHandleTableEntry+0xce
fffffa60`019f4ec0 fffff800`02462e33 : fffffa80`03cb5bb0 fffffa60`019f4f90 ffffffff`80000044 00000000`00000000 : nt!ObpCloseHandle+0x94
fffffa60`019f4f10 fffff800`02799c73 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpCallCallBacks+0x3a3


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ATITool64+6192
fffffa60`0271e192 ??              ???

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_0x50_ATITool64+6192

BUCKET_ID:  X64_0x50_ATITool64+6192

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

0: kd> lmvm ATITool64
start             end                 module name
fffffa60`02718000 fffffa60`02726000   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 18:42:26 2007 (46B9F272)
    CheckSum:         0001540C
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e0 0409.04b0 0409.04e0