Win 8.1 x64 bluescreen after few seconds

Win 8.1 x64 bluescreen after few seconds

I am having bluescreen after few seconds of running Inspector. I have tested update 8 and update 9 with the same result.

I have fully-patched Windows 8.1 Pro x64.

from memory dump, windbg.exe says:

Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*c:\symbols\MicrosoftPublicSymbols*
Symbol search path is: srv*c:\symbols\MicrosoftPublicSymbols*
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff801`97872000 PsLoadedModuleList = 0xfffff801`97b36990
Debug session time: Sun Dec 15 14:46:39.124 2013 (UTC + 1:00)
System Uptime: 0 days 0:19:47.877
Loading Kernel Symbols
.........Page 1ab7d6 not present in the dump file. Type ".hh dbgerr004" for details
.Page 1ab51a not present in the dump file. Type ".hh dbgerr004" for details
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff6`a1fb7018).  Type ".hh dbgerr001" for details
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck A, {5ffd01340, 2, 0, fffff80197809490}

*** ERROR: Module load completed but symbols could not be loaded for vtss.sys
Probably caused by : vtss.sys ( vtss+10a49 )

Followup: MachineOwner

3: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

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.
Arg1: 00000005ffd01340, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80197809490, address which referenced memory

Debugging Details:

READ_ADDRESS:  00000005ffd01340


fffff801`97809490 8b02            mov     eax,dword ptr [rdx]



PROCESS_NAME:  explorer.exe

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  ffffd000372db790 -- (.trap 0xffffd000372db790)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffffd01328 rbx=0000000000000000 rcx=ffffffffffd073b8
rdx=00000005ffd01340 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80197809490 rsp=ffffd000372db920 rbp=ffffd000208aa180
 r8=0000000000000000  r9=000000000000001f r10=ffffe000056a0b01
r11=0000000000003200 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
fffff801`97809490 8b02            mov     eax,dword ptr [rdx] ds:00000005`ffd01340=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff801979cb7e9 to fffff801979bfca0

ffffd000`372db648 fffff801`979cb7e9 : 00000000`0000000a 00000005`ffd01340 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`372db650 fffff801`979ca03a : 00000000`00000000 ffffe000`02bac880 00000000`00000000 ffffd000`372db790 : nt!KiBugCheckDispatch+0x69
ffffd000`372db790 fffff801`97809490 : 00000000`00000206 fffff801`9791c056 ffffe000`00c44118 ffffe000`01644880 : nt!KiPageFault+0x23a
ffffd000`372db920 fffff800`0322da49 : ffffd000`20780180 ffffe000`02bac880 fffff801`97b60180 00000000`0d148a70 : hal!HalSendSoftwareInterrupt+0x51
ffffd000`372db990 ffffd000`20780180 : ffffe000`02bac880 fffff801`97b60180 00000000`0d148a70 ffffd000`208aa180 : vtss+0x10a49
ffffd000`372db998 ffffe000`02bac880 : fffff801`97b60180 00000000`0d148a70 ffffd000`208aa180 fffff800`0322d951 : 0xffffd000`20780180
ffffd000`372db9a0 fffff801`97b60180 : 00000000`0d148a70 ffffd000`208aa180 fffff800`0322d951 ffffe000`02bac880 : 0xffffe000`02bac880
ffffd000`372db9a8 00000000`0d148a70 : ffffd000`208aa180 fffff800`0322d951 ffffe000`02bac880 00000000`00000000 : nt!KiInitialPCR+0x180
ffffd000`372db9b0 ffffd000`208aa180 : fffff800`0322d951 ffffe000`02bac880 00000000`00000000 fffff800`07fc2499 : 0xd148a70
ffffd000`372db9b8 fffff800`0322d951 : ffffe000`02bac880 00000000`00000000 fffff800`07fc2499 ffffe000`052bd010 : 0xffffd000`208aa180
ffffd000`372db9c0 ffffe000`02bac880 : 00000000`00000000 fffff800`07fc2499 ffffe000`052bd010 00000000`0b070908 : vtss+0x10951
ffffd000`372db9c8 00000000`00000000 : fffff800`07fc2499 ffffe000`052bd010 00000000`0b070908 00000000`00000000 : 0xffffe000`02bac880


fffff800`0322da49 ebd6            jmp     vtss+0x10a21 (fffff800`0322da21)


SYMBOL_NAME:  vtss+10a49

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  vtss.sys



BUCKET_ID:  AV_vtss+10a49


FAILURE_ID_HASH_STRING:  km:av_vtss+10a49

FAILURE_ID_HASH:  {04f30135-904f-63ea-f0cb-23243685f03f}

Followup: MachineOwner


6 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Do you have VTune (Amplifier XE) installed? The flagged module, vtss.sys, is used for some VTune analysis types.

It seems very strange that running Inspector should activate a VTune module?

What kind of Inspector analysis type are you trying to run?


mark-dewing (Intel) wrote:

Do you have VTune (Amplifier XE) installed?



mark-dewing (Intel) wrote:

It seems very strange that running Inspector should activate a VTune module?

What kind of Inspector analysis type are you trying to run?

New Analysis -> Advanced Hotspots -> "Hotspots, call counts, stacks and context switched" ; other settings are at their defaults.

Eh, sorry, it is actually Amplifier, you are right.

Actually this is a common bugcheck.Driver should not reference memory and cause page fault at IRQL equal or greater than 2.

Leave a Comment

Please sign in to add a comment. Not a member? Join today