[WorseAdvice]

This is my first post, I did read through the rules but it's not about my own computer. This is why I can't upload the SysnativeBSODCollector pack. I received the dump file from a friends pc and was wondering if you guys could help figure it out before I head over there again(It's a long drive)

BSOD started after he upgraded to windows 10 I believe(Which instantly rings a bell of possible driver issues), but I'm not experienced with reading and viewing BSOD crash dumps.

I've added the dump to the attachment.

It is caused by address: ntoskrnl.exe+142760

Now I will run Driver verifier obviously but if someone has any other or more specific solutions that would be great!

 

[Aus_Karlos]

Welcome to TSF,

For future reference it would be ideal to post the users computer specs aswell, plus if possible more than 1 dump file as this dump is incomplete.
But from what you have provided the fact that the PC was upgraded to Windows 10 can suggest driver issues. In this case it seems to be a Logitech mouse driver.
I would uninstall the Logitech program that uses SetPoint.exe and go to the Logitic website to see if theres an update for Windows 10.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {22, 2, 0, fffff8020fcac6c8}

Probably caused by : memory_corruption ( nt!MiComputeImagePteIndex+28 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 0000000000000022, 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: fffff8020fcac6c8, address which referenced memory

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


DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

BUGCHECK_P1: 22

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8020fcac6c8

READ_ADDRESS: fffff8020ff82520: Unable to get MiVisibleState
 0000000000000022 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiComputeImagePteIndex+28
fffff802`0fcac6c8 f6472202        test    byte ptr [rdi+22h],2

CPU_COUNT: 4

CPU_MHZ: b6e

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 25

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  SetPoint.exe

ANALYSIS_VERSION: 10.0.10240.9 x86fre

TRAP_FRAME:  ffffd001c7378830 -- (.trap 0xffffd001c7378830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=8000000000000000 rbx=0000000000000000 rcx=fffffa8000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8020fcac6c8 rsp=ffffd001c73789c0 rbp=ffffe001635e5010
 r8=000000000000000a  r9=ffffe00164bc4e50 r10=00000000ffffffff
r11=ffffc001b4a306c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiComputeImagePteIndex+0x28:
fffff802`0fcac6c8 f6472202        test    byte ptr [rdi+22h],2 ds:00000000`00000022=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8020fd512e9 to fffff8020fd46760

STACK_TEXT:  
ffffd001`c73786e8 fffff802`0fd512e9 : 00000000`0000000a 00000000`00000022 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd001`c73786f0 fffff802`0fd4fac7 : ffffc001`00000000 fffff802`0ff00bc0 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd001`c7378830 fffff802`0fcac6c8 : fffff6e0`00da5180 fffff6e0`00da5180 fffff802`0ff00bc0 00000000`00000000 : nt!KiPageFault+0x247
ffffd001`c73789c0 fffff802`0fcac021 : fffffa80`00000000 ffffe001`64bc4e50 000005c0`fffffb30 ffffe001`00000000 : nt!MiComputeImagePteIndex+0x28
ffffd001`c73789f0 fffff802`0fcaba06 : 00000000`00000000 ffffd001`c7378a70 ffffe001`5d7b4580 ffffe001`64bc4e50 : nt!MiReferenceInPageFile+0xb9
ffffd001`c7378a30 fffff802`0fc3d37f : 00000000`c0033333 ffffe001`5d7b4580 ffffd001`c7378c40 00000000`00000000 : nt!MiIssueHardFault+0x66
ffffd001`c7378ad0 fffff802`0fd4f9bc : ffffe001`5d646080 ffffe001`5d646080 00000000`00000008 ffffd001`c7378cc0 : nt!MmAccessFault+0x82f
ffffd001`c7378c40 00007ffa`de875fdd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c
00000000`04abe0b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`de875fdd


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiComputeImagePteIndex+28
fffff802`0fcac6c8 f6472202        test    byte ptr [rdi+22h],2

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiComputeImagePteIndex+28

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  565189c8

IMAGE_VERSION:  10.0.10586.17

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  28

FAILURE_BUCKET_ID:  AV_nt!MiComputeImagePteIndex

BUCKET_ID:  AV_nt!MiComputeImagePteIndex

PRIMARY_PROBLEM_CLASS:  AV_nt!MiComputeImagePteIndex

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_nt!micomputeimagepteindex

FAILURE_ID_HASH:  {a0d28476-1d35-9b7d-0f27-453c7137ca78}

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

 

[WorseAdvice]

Welcome to TSF,

For future reference it would be ideal to post the users computer specs aswell, plus if possible more than 1 dump file as this dump is incomplete.
But from what you have provided the fact that the PC was upgraded to Windows 10 can suggest driver issues. In this case it seems to be a Logitech mouse driver.
I would uninstall the Logitech program that uses SetPoint.exe and go to the Logitic website to see if theres an update for Windows 10.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {22, 2, 0, fffff8020fcac6c8}

Probably caused by : memory_corruption ( nt!MiComputeImagePteIndex+28 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 0000000000000022, 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: fffff8020fcac6c8, address which referenced memory

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


DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

BUGCHECK_P1: 22

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8020fcac6c8

READ_ADDRESS: fffff8020ff82520: Unable to get MiVisibleState
 0000000000000022 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiComputeImagePteIndex+28
fffff802`0fcac6c8 f6472202        test    byte ptr [rdi+22h],2

CPU_COUNT: 4

CPU_MHZ: b6e

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 25

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  SetPoint.exe

ANALYSIS_VERSION: 10.0.10240.9 x86fre

TRAP_FRAME:  ffffd001c7378830 -- (.trap 0xffffd001c7378830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=8000000000000000 rbx=0000000000000000 rcx=fffffa8000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8020fcac6c8 rsp=ffffd001c73789c0 rbp=ffffe001635e5010
 r8=000000000000000a  r9=ffffe00164bc4e50 r10=00000000ffffffff
r11=ffffc001b4a306c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiComputeImagePteIndex+0x28:
fffff802`0fcac6c8 f6472202        test    byte ptr [rdi+22h],2 ds:00000000`00000022=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8020fd512e9 to fffff8020fd46760

STACK_TEXT:  
ffffd001`c73786e8 fffff802`0fd512e9 : 00000000`0000000a 00000000`00000022 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd001`c73786f0 fffff802`0fd4fac7 : ffffc001`00000000 fffff802`0ff00bc0 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd001`c7378830 fffff802`0fcac6c8 : fffff6e0`00da5180 fffff6e0`00da5180 fffff802`0ff00bc0 00000000`00000000 : nt!KiPageFault+0x247
ffffd001`c73789c0 fffff802`0fcac021 : fffffa80`00000000 ffffe001`64bc4e50 000005c0`fffffb30 ffffe001`00000000 : nt!MiComputeImagePteIndex+0x28
ffffd001`c73789f0 fffff802`0fcaba06 : 00000000`00000000 ffffd001`c7378a70 ffffe001`5d7b4580 ffffe001`64bc4e50 : nt!MiReferenceInPageFile+0xb9
ffffd001`c7378a30 fffff802`0fc3d37f : 00000000`c0033333 ffffe001`5d7b4580 ffffd001`c7378c40 00000000`00000000 : nt!MiIssueHardFault+0x66
ffffd001`c7378ad0 fffff802`0fd4f9bc : ffffe001`5d646080 ffffe001`5d646080 00000000`00000008 ffffd001`c7378cc0 : nt!MmAccessFault+0x82f
ffffd001`c7378c40 00007ffa`de875fdd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c
00000000`04abe0b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`de875fdd


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiComputeImagePteIndex+28
fffff802`0fcac6c8 f6472202        test    byte ptr [rdi+22h],2

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiComputeImagePteIndex+28

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  565189c8

IMAGE_VERSION:  10.0.10586.17

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  28

FAILURE_BUCKET_ID:  AV_nt!MiComputeImagePteIndex

BUCKET_ID:  AV_nt!MiComputeImagePteIndex

PRIMARY_PROBLEM_CLASS:  AV_nt!MiComputeImagePteIndex

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_nt!micomputeimagepteindex

FAILURE_ID_HASH:  {a0d28476-1d35-9b7d-0f27-453c7137ca78}

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

Okay I'll try that as well.
And I'm sorry for being incomplete. The user isn't really techy and all I know is he has a prebuild medion pc. Windows 10 64bits.
I believe he uses a Logitech mouse indeed.

Just wondering since I saw this in the BluescreenView if this is somewhat related to it as well?(Graphics card?)

 

[Aus_Karlos]

ntosknl.exe is short for Windows NT System Kernel, its a low-level driver that manages some of Windows basic systems like Memory Management all other 3rd-party drivers communicate to this driver.

 

[WorseAdvice]

ntosknl.exe is short for Windows NT System Kernel, its a low-level driver that manages some of Windows basic systems like Memory Management all other 3rd-party drivers communicate to this driver.

I meant the bottom 2
VGA Boot Driver
followed up by Platform Specific Hardware Error Driver.

Thought maybe that could also be something really lookout for and or needs to be fixed.

 

[Aus_Karlos]

VGA Boot driver is what is used to display the Windows boot screen until Windows gets to the Welcome screen.
PSHED.dll is there to actually generate Hardware errors.

 

[WorseAdvice]

VGA Boot driver is what is used to display the Windows boot screen until Windows gets to the Welcome screen.
PSHED.dll is there to actually generate Hardware errors.

Ah okay. So BluescreenView doesn't really tell you anything significant?