Pi_server.exe crash dump. Pitool v1.0.1.254

Can’t post to Pitool.

Pitool v1.0.1.254

Remains of the pi_overlay.exe error event (don’t have the crash dump saved for some reason):

Faulting application name: pi_overlay.exe, version: 0.0.0.0, time stamp: 0x5e1316f9
Faulting module name: pi_overlay.exe, version: 0.0.0.0, time stamp: 0x5e1316f9
Exception code: 0xc0000005
Fault offset: 0x000000000001dce4
Faulting process id: 0x41b8
Faulting application start time: 0x01d5eb4beda00594
Faulting application path: C:\Program Files\Pimax\Runtime\pi_overlay.exe
Faulting module path: C:\Program Files\Pimax\Runtime\pi_overlay.exe
Report Id: 1b7ff838-5d08-4e63-b464-85415204daae
Faulting package full name: 
Faulting package-relative application ID: 

Problem signature:
P1: pi_overlay.exe
P2: 0.0.0.0
P3: 5e1316f9
P4: pi_overlay.exe
P5: 0.0.0.0
P6: 5e1316f9
P7: c0000005
P8: 000000000001dce4
P9: 
P10: 

pvr_svr_20-02-24-22-54-20.dmp:

0:084> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** WARNING: Unable to verify checksum for pi_server.exe

KEY_VALUES_STRING: 1

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 507277

    Key  : Timeline.Process.Start.DeltaSec
    Value: 3759


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

Timeline: !analyze.Start
    Name: <blank>
    Time: 2020-02-24T21:37:50.969Z
    Diff: 2610969 mSec

Timeline: Dump.Current
    Name: <blank>
    Time: 2020-02-24T20:54:20.0Z
    Diff: 0 mSec

Timeline: Process.Start
    Name: <blank>
    Time: 2020-02-24T19:51:41.0Z
    Diff: 3759000 mSec

Timeline: OS.Boot
    Name: <blank>
    Time: 2020-02-18T23:59:43.0Z
    Diff: 507277000 mSec


DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT:  (.ecxr)
rax=000001c7b179c060 rbx=0000000000000000 rcx=82c4efc651a20000
rdx=00007ff68f0474e8 rsi=0000000000000000 rdi=0000000000000000
rip=00007ffea4b2ced1 rsp=0000002e454ffb30 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
r11=000002c9cf8b85d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
ntdll!RtlUserThreadStart+0x21:
00007ffe`a4b2ced1 eb20            jmp     ntdll!RtlUserThreadStart+0x43 (00007ffe`a4b2cef3)
Resetting default scope

FAULTING_IP: 
pi_server+b40c
00007ff6`8e47b40c cc              int     3

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ff68e47b40c (pi_server+0x000000000000b40c)
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 1
   Parameter[0]: 0000000000000000

BUGCHECK_STR:  BREAKPOINT

DEFAULT_BUCKET_ID:  BREAKPOINT

PROCESS_NAME:  pi_server.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

EXCEPTION_CODE_STR:  80000003

EXCEPTION_PARAMETER1:  0000000000000000

WATSON_BKT_PROCSTAMP:  5e26720b

WATSON_BKT_MODULE:  pi_server.exe

WATSON_BKT_MODSTAMP:  5e26720b

WATSON_BKT_MODOFFSET:  b40c

BUILD_VERSION_STRING:  10.0.18362.329 (WinBuild.160101.0800)

MODLIST_WITH_TSCHKSUM_HASH:  2bc3701bc81fb36a07b90c285a31afff61a5257b

MODLIST_SHA1_HASH:  9918fcab0fdb751f4ec765c9c78097d320793143

NTGLOBALFLAG:  0

PRODUCT_TYPE:  1

SUITE_MASK:  272

DUMP_FLAGS:  8

DUMP_TYPE:  1

ANALYSIS_SESSION_HOST:  DESKTOP-3KOT0TM

ANALYSIS_SESSION_TIME:  02-24-2020 23:37:50.0969

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 00007ffea4b2ced1

THREAD_ATTRIBUTES: 
FAULTING_THREAD:  ffffffff

THREAD_SHA1_HASH_MOD_FUNC:  0b0cefc38e6086cebb12d6063da67f39c688ae78

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  7953233e61575a961f8b5922b52bfde90ae67c05

OS_LOCALE:  ETI

PRIMARY_PROBLEM_CLASS:  BREAKPOINT

PROBLEM_CLASSES: 

    ID:     [0n321]
    Type:   [@APPLICATION_FAULT_STRING]
    Class:  Primary
    Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
            BUCKET_ID
    Name:   Omit
    Data:   Add
            String: [BREAKPOINT]
    PID:    [Unspecified]
    TID:    [Unspecified]
    Frame:  [0]

STACK_TEXT:  
0000002e`454ffb30 00007ffe`a4b2ced1 ntdll!RtlUserThreadStart+0x21


STACK_COMMAND:  .ecxr ; kb ; ** Pseudo Context ** Pseudo ** Value: 1f7fd3ce0b0 ** ; kb

THREAD_SHA1_HASH_MOD:  4d6a592812b1f521b481ecb6f54e3789559d0477

FOLLOWUP_IP: 
ntdll!RtlUserThreadStart+21
00007ffe`a4b2ced1 eb20            jmp     ntdll!RtlUserThreadStart+0x43 (00007ffe`a4b2cef3)

FAULT_INSTR_CODE:  8b4820eb

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ntdll!RtlUserThreadStart+21

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ntdll

IMAGE_NAME:  ntdll.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  64d10ee0

BUCKET_ID:  BREAKPOINT_ntdll!RtlUserThreadStart+21

FAILURE_EXCEPTION_CODE:  80000003

FAILURE_IMAGE_NAME:  ntdll.dll

BUCKET_ID_IMAGE_STR:  ntdll.dll

FAILURE_MODULE_NAME:  ntdll

BUCKET_ID_MODULE_STR:  ntdll

FAILURE_FUNCTION_NAME:  RtlUserThreadStart

BUCKET_ID_FUNCTION_STR:  RtlUserThreadStart

BUCKET_ID_OFFSET:  21

BUCKET_ID_MODTIMEDATESTAMP:  64d10ee0

BUCKET_ID_MODCHECKSUM:  1ef8e0

BUCKET_ID_MODVER_STR:  10.0.18362.657

BUCKET_ID_PREFIX_STR:  BREAKPOINT_

FAILURE_PROBLEM_CLASS:  BREAKPOINT

FAILURE_SYMBOL_NAME:  ntdll.dll!RtlUserThreadStart

FAILURE_BUCKET_ID:  BREAKPOINT_80000003_ntdll.dll!RtlUserThreadStart

TARGET_TIME:  2020-02-24T20:54:20.000Z

OSBUILD:  18362

OSSERVICEPACK:  329

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt SingleUserTS

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.18362.329

ANALYSIS_SESSION_ELAPSED_TIME:  11afb

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:breakpoint_80000003_ntdll.dll!rtluserthreadstart

FAILURE_ID_HASH:  {cf07cb24-563a-ec7c-8445-6d891f3da8b1}

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

@Alex.liu

2 Likes

You need to post in Pitool Sub category.

Moved your post to pitool\Discussion and added Alex.lui to your post.

Could be posted though in Report Bug sub category will the additional info shown there.

1 Like

Thanks. Wasn’t able to post under Pitool or Pitool bug reports.

That’s strange. Can you try a test post in Report bug?

Now in Report Bug you can’t start a new topic. But should be able to reply in one of the defined topics.

Pitool\Discussion you should be able to create topics.

1 Like

Ok, I see. No new topics. Confusion resolved :slight_smile:

Edit: Pitool\Discussion new topic was disabled to me at the time of posting. Now available.
Edit: Just a site usability issue. Category looked like a tag. I was actually under Pitool, not Pitool\Discussion.

2 Likes

Okay cool.

Yeah Parent Categories with White lettering are read only to act as a folder for Sub Categories with Black lettering to have discussions save for certain Sub Categories like Pitool\Release Notes and the Announcement Sub Categories which is kept unclutter for important info.

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.