Question Help! Memory management - Blue screen of death - ntoskrnl.exe - Gaming laptop

[supremekaiqc]

Hi all i got a predator helios 300 PH315-51
i need a solution for my blue screen of death if someone got an idea i already installed all the lastest bios and softwares. uninstalled antiviruses. i did the memtestx86 and did the windows memory testing on windows10 and it found no problem and my pc is pretty new so im not sure if its the ram anyway.

my computer is only 1 years old but like 3months in it started doing the blue screens and i didnt claim warranty big fail.

i also did sfc scan ad chkdsk everythign went ok

Crash Dump Analysis
Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Fri 2019-12-06 16:19:16 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\120619-11921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1A (0x61948, 0x1000200, 0x1, 0x1000200)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


On Fri 2019-12-06 16:19:16 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x6BF42)
Bugcheck code: 0x1A (0x61948, 0x1000200, 0x1, 0x1000200)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


On Thu 2019-12-05 19:50:58 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\120519-10343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x13F321)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8076693F321, 0xFFFFC08A5D1699C8, 0xFFFF82803C8DF930)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


On Mon 2019-10-14 14:59:30 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101419-10218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0x1A (0x41790, 0xFFFF908003470CD0, 0x0, 0x1)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred. A page table page has been corrupted.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


On Thu 2019-09-26 16:49:01 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\092619-11218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C10A0)
Bugcheck code: 0x1A (0x41792, 0xFFFFD5003A73CC98, 0x1004100000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Colif]

Can you go to C:\WINDOWS\Minidump
copy the minidump files to another folder
upload copies from new folder to a file sharing website and show link here

as usual, who crashed blames windows. Ntoskrnl & ntkrnlmp are both parts of the windows kernel and while they are what crashed, they are normally not the cause. One of ntoskrnl's jobs is memory management, but it also sits between drivers and hardware so it could be any of those still

I can't guarantee when dump files will be read as some of the people who normally do are away this week.

 

[supremekaiqc]

Sorry I would need a specific website where I could upload the minidump files because i dont know any.

so i got a new blue screen with this message this time

Crash Dump Analysis

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Fri 2019-12-27 10:15:54 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\122719-9843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x13F321)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8055053F321, 0xFFFFF484C2D699C8, 0xFFFFCF80AD718930)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 2019-12-27 10:15:54 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x6864)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8055053F321, 0xFFFFF484C2D699C8, 0xFFFFCF80AD718930)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Colif]

I would use Google drive or Microsoft Onedrive. Onedrive is built into Win 10 so could try that. Just need to share link here - https://www.dummies.com/computers/operating-systems/windows-10/how-to-share-a-onedrive-link/

 

[supremekaiqc]

minidump onedrive link https://1drv.ms/u/s!AjrBAQJVJgQT8CsUFNf_iy3SE1So?e=fQZbxt

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://frowsierbridge.htmlpasta.com/

Spoiler

File information:	122819-13937-01.dmp (Dec 28 2019 - 19:19:19)
Bugcheck:	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:	memory_corruption (Process: System)
Uptime:	1 Day(s), 2 Hour(s), 46 Min(s), and 08 Sec(s)

File information:	122719-9843-01.dmp (Dec 27 2019 - 10:15:54)
Bugcheck:	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:	memory_corruption (Process: chrome.exe)
Uptime:	1 Day(s), 0 Hour(s), 31 Min(s), and 37 Sec(s)

File information:	120619-11921-01.dmp (Dec 6 2019 - 16:19:16)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: SpatialAudioLicenseSrv.exe)
Uptime:	0 Day(s), 19 Hour(s), 21 Min(s), and 58 Sec(s)

File information:	120519-10343-01.dmp (Dec 5 2019 - 19:50:58)
Bugcheck:	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:	memory_corruption (Process: RAVBg64.exe)
Uptime:	0 Day(s), 1 Hour(s), 54 Min(s), and 34 Sec(s)

File information:	101419-10218-01.dmp (Oct 14 2019 - 13:59:30)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: chrome.exe)
Uptime:	1 Day(s), 0 Hour(s), 30 Min(s), and 48 Sec(s)

File information:	092619-11218-01.dmp (Sep 26 2019 - 15:49:01)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: svchost.exe)
Uptime:	4 Day(s), 23 Hour(s), 20 Min(s), and 05 Sec(s)

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

BIOS info was not included in the 1st dump file. This can sometimes mean an outdated BIOS is being used.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

Happy new year!

 

[supremekaiqc]

Bios is up to date its

Date:
2019/05/14
Version:
1.26


Downloaded from acer website

 

[Colif]

May 05 2013

ScpVBus.sys

Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus driver

can cause BSOD. I think there is a newer version from 2015 but it can also cause BSOD.

Jun 14 2017

RTKVHD64.sys

Realtek Audio System driver

RAVBg64.exe is part of the realtek sound drivers, as its possible the crash above it mentioning SpatialAudioLicenseSrv.exe could also be sound driver related. Here is where you find the latest driver - https://www.tenforums.com/sound-audio/135259-latest-realtek-hd-audio-driver-version-2-a.html

 

[supremekaiqc]

May 05 2013

ScpVBus.sys

Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus driver

can cause BSOD. I think there is a newer version from 2015 but it can also cause BSOD.

Jun 14 2017

RTKVHD64.sys

Realtek Audio System driver

RAVBg64.exe is part of the realtek sound drivers, as its possible the crash above it mentioning SpatialAudioLicenseSrv.exe could also be sound driver related. Here is where you find the latest driver - https://www.tenforums.com/sound-audio/135259-latest-realtek-hd-audio-driver-version-2-a.html

hi on the link u sent for the audio drivers it redirect me to microsoft store and when i try download it says error and it doesnt download or install

also scpvbus.sys how do i uninstall that lol?

 

[Colif]

the top post on that link talks about the Audio control app, not the actual driver itself. If you want to use it, you need another driver as per link in base of that post
https://www.tenforums.com/sound-aud...o-console-requires-realtek-hd-uad-driver.html

The 2nd post under the info one includes the old normal drivers you are after.

I assumed scarlet crush was the PS3 drivers you were using. I think this shows how to remove it - https://github.com/nefarius/ScpToolkit/releases

 

[supremekaiqc]

the top post on that link talks about the Audio control app, not the actual driver itself. If you want to use it, you need another driver as per link in base of that post
https://www.tenforums.com/sound-aud...o-console-requires-realtek-hd-uad-driver.html

The 2nd post under the info one includes the old normal drivers you are after.

I assumed scarlet crush was the PS3 drivers you were using. I think this shows how to remove it - https://github.com/nefarius/ScpToolkit/releases

ok idk whats the scarlet crush ps3 drivers, but i do have something called inputmapper i use to use playstation controllers, it also was installed around last year i think when i started getting bsod so maybe you found my problem ! ill keep you posted if i get another bsod ill uninstall it and install the sound drivers

 

[Colif]

Input mapper users scarlet crush.

 

[supremekaiqc]

Hi we are January 18 and to this day I got two bsod but the first time it was the 6th but it didn't save a dump file so I had to wait till the next. https://1drv.ms/u/s!AjrBAQJVJgQT8CtrwOx872ZV7PG8?e=prKpia

check the file made jan 2020 18 please help me if you can!

I unisntalled input mapper and deleted ScpVBus.sys in windows/drivers but I still got the blue screen

 

[gardenman]

It's much easier if you create a new folder each time with only the new file(s) in it, but I figured out which file this time. Results: https://defencelessspaceship.htmlpasta.com/

File information:	011820-10718-01.dmp (Jan 18 2020 - 09:41:37)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: backgroundTaskHost.exe)
Uptime:	1 Day(s), 2 Hour(s), 47 Min(s), and 45 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[supremekaiqc]

I think my pc might be unfixable

 

[Colif]

So the file that crashed is part of windows update.

It looks like a driver, the PC had been doing actions in page tables (which are on ram) and its last action was towards I/.O. Input/Output actions are sent to drivers. Problem is I can't tell which one. the process was started by windows and only failed when whatever it called didn't answer.

Try running driver verifer - its the 2nd post in this thread - https://forums.tomshardware.com/thr...nclude-in-blue-screen-of-death-posts.3468965/ - its part oof windows designed to test drivers. It will cause a BSOD if it finds a bad driver. Show us the dump files.

 

[supremekaiqc]

Ok here is the driver verifier dump https://1drv.ms/u/s!AjrBAQJVJgQT8DTHgEAkaqnTE4a4?e=AyWyMY

 

[supremekaiqc]

Bluescreen view says its caused by driver LGBusEnum.sys which is something for logitech so i uninstalled logitech gaming virtual bus enumerator in device manager. That should fix my problem?

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://cumbersomeaustralian.htmlpasta.com/

File information:	011920-11953-01.dmp (Jan 19 2020 - 10:13:21)
Bugcheck:	DRIVER_VERIFIER_DETECTED_VIOLATION (C4)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 08 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

Edit: Laughs at web address that "pasta" gave me: "cumbersome australian".

 

[Colif]

Bluescreen view says its caused by driver LGBusEnum.sys which is something for logitech so i uninstalled logitech gaming virtual bus enumerator in device manager. That should fix my problem?

If you stop getting errors, Yep. That was only logitech driver on PC which is odd as Logitech Gaming Software has about 3 parts normally. If you use Logitech keyboard, this has replaced it - https://www.logitechg.com/en-au/innovation/g-hub.html

Edit: Laughs at web address that "pasta" gave me: "cumbersome australian".

Am I that bad?

 

[supremekaiqc]

Yo one week later, I got two more bsod with no dump file made what should I do Driver Verifier Again? i uninstalled logitech gaming software already

on was faulty hardware corrupted page and the other said kernel something didnt have time to read.

what should I do?

 

[supremekaiqc]

Ok so now I ran another Driver verifier and it says the problem is like apple but it makes no sense

On Sat 2020-02-01 07:12:55 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020120-9359-01.dmp
This was probably caused by the following module: usbaapl64.sys (0xFFFFF807F4FC10F3)
Bugcheck code: 0xC4 (0x2000, 0xFFFFF807F4FC10F3, 0x0, 0x78756D75)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\drivers\usbaapl64.sys
product: Apple Mobile Device USB Driver
company: Apple, Inc.
description: Apple Mobile Device USB Driver
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: usbaapl64.sys (Apple Mobile Device USB Driver, Apple, Inc.).
Google query: usbaapl64.sys Apple, Inc. DRIVER_VERIFIER_DETECTED_VIOLATION

 

[supremekaiqc]

Ok so I updated the driver of my Apple Mobile Device USB Driver in device manager. Should it fix my problem or should I do Driver verifier again?

when i check file path: C:\WINDOWS\system32\drivers\usbaapl64.sys it says the date is from 2015 should I delete it from system32 manually like right click delete? idk what to do lol, waiting on answers

 

[supremekaiqc]

Hi nobody replied but I ran driver verifier again and then it said the problem was my elgato sound capture driver... just to say driver verifier told me now 3 driver errors its like every damn time imma use it its going to tell me a different program.. so now i updated my elgato drivers and what next?

 

[Colif]

Between a heatwave on weekend and a Bushfire potentially attacking my city, I have been otherwise occupied in the last few days and away from my PC. I would have answered if I could.

If you updated drivers, are you still crashing? If not, wait and see if it was fix.