Question Random system BSOD Toshiba P75-A7200

[admirsal]

Hi all together, I'm having a strange issue with my Toshiba P75-A7200. The Laptop is getting BSOD most of the time when it is not doing anything. It is still mostly with the default spec's besides that i Upgrade it with a additional 850 EVO 500gb and 8gb ram. The problems also appeared before the upgrade.

Strange is that BSOD's did not appear a while ago but since 2-3 weeks maybe once a week it depends how often i use it. Earyer reinstall, memtest, virus and malware scans never found anything wrong that a could connect with the BSOD's.

I've managed to get a minibump file, maybe someone knows more about the Error codes provided so thank's a lot in advance!

Minidump:
Microsoft (R) Windows Debugger Version 10.0.18303.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\011319-5406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`38e96000 PsLoadedModuleList = 0xfffff800`39244150
Debug session time: Sun Jan 13 20:08:45.391 2019 (UTC + 2:00)
System Uptime: 1 days 23:40:32.140
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
.........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`390400a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff909`d24615e0=000000000000000a
5: 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: 0000000100005910, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80038ed6133, address which referenced memory

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.17134.523 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: TOSHIBA

SYSTEM_PRODUCT_NAME: Satellite P75-A

SYSTEM_SKU: PSPLNU

SYSTEM_VERSION: PSPLNU-00H004

BIOS_VENDOR: Insyde Corp.

BIOS_VERSION: 1.60

BIOS_DATE: 12/04/2014

BASEBOARD_MANUFACTURER: Type2 - Board Vendor Name1

BASEBOARD_PRODUCT: Type2 - Board Product Name1

BASEBOARD_VERSION: Type2 - Board Version

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

DUMP_TYPE: 2

BUGCHECK_P1: 100005910

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff80038ed6133

WRITE_ADDRESS: fffff800392e3388: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
0000000100005910

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiTimerWaitTest+1d3
fffff800`38ed6133 f0490fbaac241059000000 lock bts qword ptr [r12+5910h],0

CPU_COUNT: 8

CPU_MHZ: 95a

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 24'00000000 (cache) 24'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_SESSION_HOST: ADMIRPC

ANALYSIS_SESSION_TIME: 01-13-2019 20:30:00.0967

ANALYSIS_VERSION: 10.0.18303.1000 amd64fre

TRAP_FRAME: fffff909d2461720 -- (.trap 0xfffff909d2461720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000004 rbx=0000000000000000 rcx=0000000000000000
rdx=ffffb2005b080180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80038ed6133 rsp=fffff909d24618b0 rbp=ffffd9818f18d080
r8=fffff909d2461b18 r9=000000000000002f r10=0000000000000102
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiTimerWaitTest+0x1d3:
fffff800`38ed6133 f0490fbaac241059000000 lock bts qword ptr [r12+5910h],0 ds:00000000`00005910=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80039050c69 to fffff800390400a0

STACK_TEXT:
fffff909`d24615d8 fffff800`39050c69 : 00000000`0000000a 00000001`00005910 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff909`d24615e0 fffff800`3904d8e5 : ffffd981`8f8b71f0 00000000`00000000 0000005d`71e25933 00000000`000000cc : nt!KiBugCheckDispatch+0x69
fffff909`d2461720 fffff800`38ed6133 : ffffd981`94580300 00000000`00000002 ffffd981`919b1c20 ffffd981`928e3700 : nt!KiPageFault+0x425
fffff909`d24618b0 fffff800`38ed5cc5 : fffff909`d2461b10 0000018f`00000000 fffff909`d2461b18 00000000`00000000 : nt!KiTimerWaitTest+0x1d3
fffff909`d2461960 fffff800`38ed4ca7 : 00000000`0000000e fffff800`38f2285a 00000000`0023ae29 00000000`00000019 : nt!KiProcessExpiredTimerList+0xb5
fffff909`d2461a50 fffff800`390437da : 00000000`00000000 ffffb200`5b080180 00000000`00000000 ffffb200`5b090200 : nt!KiRetireDpcList+0x4c7
fffff909`d2461c60 00000000`00000000 : fffff909`d2462000 fffff909`d245c000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff80038ed60f8 - nt!KiTimerWaitTest+198
[ c8:d8 ]
1 error : !nt (fffff80038ed60f8)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BIT

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_ONE_BIT

TARGET_TIME: 2019-01-13T18:08:45.000Z

OSBUILD: 17134

OSSERVICEPACK: 523

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2019-01-01 08:44:13

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.17134.523

ANALYSIS_SESSION_ELAPSED_TIME: 2aae

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:memory_corruption_one_bit

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: memory_corruption

 

[Colif]

can you go to C:\Windows\Minidump
copy the minidump file from here to a new folder
from new folder, upload the minidump to a file sharing web site and show the link here, We should be able to get more info out of the minidump for you.

IRQ errors are generally drivers, did you go here after install and make sure you have latest drivers? https://support.toshiba.com/support/driversResults?freeText=1200005515&osId=26

 

[admirsal]

can you go to C:\Windows\Minidump
copy the minidump file from here to a new folder
from new folder, upload the minidump to a file sharing web site and show the link here, We should be able to get more info out of the minidump for you.

IRQ errors are generally drivers, did you go here after install and make sure you have latest drivers? https://support.toshiba.com/support/driversResults?freeText=1200005515&osId=26

Hi Colif,i have not copyed the minidump file to another location for backup. So the original file is not anymore at the c:\windows\minidump location

I didn't install Drivers form the toshiba site a long time ago. Isn't it better to let M$ do it's thing with the automatic updates?

 

[gardenman]

Hi, Colif is currently having weather problems and it may be a day or so before he can reply.

Usually the drivers that Windows Update provides are a bit older. Sometimes they are better, sometimes they aren't. Whenever possible, I would try to download the drivers directly from your PC's website (Toshiba) or the PC part website (NVIDIA).

What I would do is try the drivers from Toshiba to see if that helps. Write down which drivers you are updating. If it helps, great! If it makes things worse, you can always go into Device Manager and choose "Roll Back" on the Properties to return to the previous driver for each one that you have updated.

In the dump info you provided above, it didn't point out a specific driver.

Be sure to disable any disk cleaning utilities for a few days. They usually delete dump files and log files. If you have another BSOD, go ahead and copy that dump file to a safe place such as your desktop so it won't be deleted.

 

[admirsal]

Hi gardenman, thanks for the info i will try that. In the link below is the dump file i just left the laptop on over the night and it got at some point a BSOD again!

https://drive.google.com/open?id=1Mpyc2t-MeIPsDDZ_zx9qzhL4odgZxNGM

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://pste.eu/p/Cvmp.html

File: 011819-5203-01.dmp (Jan 17 2019 - 19:35:41)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: afd.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 26 Min(s), and 17 Sec(s)

Comment: 2 or more types of RAM are installed.

The overclocking driver "IOCBios2.sys" was found on your system. (Intel Extreme Tuning Utility)

I can't help you with this. Colif or someone else will post with more information soon. Please wait for more answers. Good luck.

Edit: The new dump file: https://pste.eu/p/mkrN.html
File: 011819-5500-01.dmp (Jan 18 2019 - 13:16:39)
BugCheck: [UNEXPECTED_KERNEL_MODE_TRAP_M (1000007F)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 10 Min(s), and 50 Sec(s)

 

[admirsal]

Got Today another BSOD whyle i was working. I've uploaded it also in the same GDrive location.

 

[Colif]

Did you check each stick by itself when you ran memtest? are the 2x4gb sticks removable?

I only ask as different error codes each time can mean its ram that is cause

is there anything on device called Toshiba Application & Driver installer? - https://support.toshiba.com/support/viewContentDetail?contentId=4009330 as I would suggest using that to update drivers

if there are newer LAN drivers, it may help as

Afd.sys (Windows Ancillary Function Driver) is a driver for Winsock, which is a program necessary to connect the computer to the Internet.

http://www.tech-faq.com/afd-sys.html

your lan drivers are from 2013, and if this is device, you should have intel drivers now, and yet your dump file shows Atheros drivers.

If that is wrong model, you can get latest atheros drivers from here: https://www.killernetworking.com/killersupport/category/other-downloads

 

[admirsal]

No, I've checked the default 2x4gb sticks together. Is it better to test every ram stick separately?

Don't have anything installed from Toshiba I like it simple. The Toshiba Application & Driver Installer tool is not available for my Device.

I changed my wifi card, the Intel one was dropping very frequently the connection.

Il will also try to update all of my drivers and report if the situation got any better but I am experiencing even more BSOD's these days.

 

[admirsal]

So I have tested all 3 RAM stick with memtest and updated all drivers RAm tests finished without any Errors. Any suggestions on how to maybe provoke the BSOD for testing purposes?

 

[Colif]

Before running this,

1) search for “Create a restore point” and create a restore point

2) Create a bootable USB of Win 10 installer to use as a boot drive. download the Windows 10 media creation tool and use it to make a win 10 installer on USB

try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, upload the minidump file and we see what it shows us.

Steps 1 & 2 are just precautions as sometimes driver verifer can put you in a boot loop. If this happen, follow these steps to get out of it

change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose system restore and roll system back to restore point created in step 1. PC should boot normally.

 

[admirsal]

Colif, I tried what you sad and now can not boot in win besides safe mode. Restore and startup repair does not work getting error (Img in the link). Any other suggestions? Minidump folder is empty.

https://drive.google.com/folderview?id=1Mpyc2t-MeIPsDDZ_zx9qzhL4odgZxNGM

 

[Colif]

I have to go to work now or I would look right away, I will answer again later once i have more time

 

[Colif]

does system restore give that error for any date you choose?

safe mode works? thats better than nothing... we might still be able to fix

see this about disabling driver verifer - https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html#Part3

unfortunately, sometimes even system restore doesn't fix the problems driver verifer can cause. It is why I don't suggest it for everyone.

 

[admirsal]

does system restore give that error for any date you choose?

safe mode works? thats better than nothing... we might still be able to fix

see this about disabling driver verifer - https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html#Part3

unfortunately, sometimes even system restore doesn't fix the problems driver verifer can cause. It is why I don't suggest it for everyone.

Disabling the driver verifier with the instructions you sent me does also not work.

And yes with every available restore point I'm getting errors I thinkhink they are all the same..

Any other suggestions I could try?

 

[admirsal]

Disabling the driver verifier with the instructions you sent me does also not work.

And yes with every available restore point I'm getting errors I thinkhink they are all the same..

Any other suggestions I could try?

I was wrong 😁, in the boot recovery options with the CMD command did not work to disable the driver check. I had to boot into the safemode and there to run the CMD command to disable the driver check.

 

[Colif]

Are you still getting errors?

did driver verifer cause a BSOD while it was running? apart from the boot loop?

I can ask another user to look at this, he may have a better idea of what is wrong

@axe0axe0 can you look at this for me?

 

[admirsal]

Are you still getting errors?

did driver verifer cause a BSOD while it was running? apart from the boot loop?

I can ask another user to look at this, he may have a better idea of what is wrong

@axe0axe0 can you look at this for me?

Was working a couple of hours and haven't got any errors/bsod. With the driver verifier also didn't get any bsod just the boot loop. If there is another solution the check the installed drivers that would be great.