BSOD with multiple causes & no bootable drive

[hell3on5wheels7]

I'm getting some blue screens quite frequently—1-3 times a day—on my Alienware 17r4 laptop; with two causes: critical process died, and kernal data inpage error.

Most of the time, the error window stays at 0%, never creating a dmp file, until I give up and restart. During those restarts I am usually met with a black screen and white text saying "checking media presence". From there it goes into diagnostics that ends with a loud beep, informing me that a bootable drive could not be found. Another restart brings me back to the black screen with white text, but this time it boots and brings me to my desktop.

As I said, it usually fails to create a dmp file, but I just got another blue screen for critical process died that successfully took a dmp, linked here: https://drive.google.com/open?id=1y1E8xi1_VvfkoZ2OAotiXVbT4Kb5hCG_

Things I've tried:
chkdsk, sfc, and DISM. Chkdsk reports no errors. Sfc reported errors it could not fix, but DISM was able to. Sfc reports no more errors.

Flashed to newest BIOS version.

Multiple GPU drivers. My current driver is not the latest anymore, but it was when I was testing this approach.

Multiple hardware diagnostics, with Dell's Support Assist tool, and the computer's built-in diagnostics tool found using F12 on boot.

I have not tried memtest yet, because I have 32 gb of ram. I want to use it, but college and YouTube keep me in constant need of my computer.

Dell phone technicians were an absolute waste of time. I'm hoping someone here can help.

 

[Ralston18]

Look in Reliability History and Event Viewer. What error codes and warnings do you find therein?

 

[hell3on5wheels7]

Look in Reliability History and Event Viewer. What error codes and warnings do you find therein?

Reliability monitor:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ef (0xffffa6811934c080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 0c6e8dad-7e63-4327-93db-9f6c0a0e1d8a.

Event viewer:
- EventData

BugcheckCode 239
BugcheckParameter1 0xffffa6811934c080
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 0
CsEntryScenarioInstanceId 0
BugcheckInfoFromEFI true
CheckpointStatus 0

 

[hell3on5wheels7]

I also got these bugchecks from other dates in reliability monitor:
The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff802c0cf0378, 0x0000000000000000)

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffff8b023493f4a0
Parameter 2: fffff807fc1307f8
Parameter 3: 0
Parameter 4: 0
OS version: 10_0_17134
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.17134.2.0.0.768.101
Locale ID: 1033

 

[Ralston18]

What are your system specs? Hardware, software....?

 

[johnbl]

I would focus on updateing the intel tuning driver, it is much older than your cpu
and most likely will not work correctly with your updated bios
BIOS Release Date 09/10/2018

I would remove it: use autoruns, locate the driver and uncheck the entry.
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
I would suspect it is running a generic service host. you can go into services and see if there is entry.


I am not sure about your old backup program, they could also run as a generic service host.
they tend to work until there is some type of error.

you might look for a update to the software and run crystaldiskinfo.exe to see if your drive is having errors.
-------------
some program running as a generic service host (svchost.exe) caused the bugcheck

Intel extreme tuning BIOS interface driver
\SystemRoot\System32\drivers\XtuAcpiDriver.sys Thu Feb 26 04:51:57 2015
: http://downloadcenter.intel.com/

cpu:
Processor Version Intel(R) Core(TM) i7-7820HK CPU @ 2.90GHz
Processor Voltage 89h - 0.9V
External Clock 100MHz
Max Speed 8300MHz
Current Speed 2800MHz

old drivers:
Aomei BackUpper driver
C:\Windows\system32\ammntdrv.sys Tue Dec 25 00:46:37 2012
C:\Windows\system32\amwrtdrv.sys Tue Dec 25 00:46:38 2012

 

[hell3on5wheels7]

What are your system specs? Hardware, software....?

I added my DXDIAG info to my Drive folder: https://drive.google.com/open?id=1y1E8xi1_VvfkoZ2OAotiXVbT4Kb5hCG_

 

[hell3on5wheels7]

I would focus on updateing the intel tuning driver, it is much older than your cpu
and most likely will not work correctly with your updated bios
BIOS Release Date 09/10/2018

I would remove it: use autoruns, locate the driver and uncheck the entry.
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
I would suspect it is running a generic service host. you can go into services and see if there is entry.


I am not sure about your old backup program, they could also run as a generic service host.
they tend to work until there is some type of error.

you might look for a update to the software and run crystaldiskinfo.exe to see if your drive is having errors.
-------------
some program running as a generic service host (svchost.exe) caused the bugcheck

Intel extreme tuning BIOS interface driver
\SystemRoot\System32\drivers\XtuAcpiDriver.sys Thu Feb 26 04:51:57 2015
: http://downloadcenter.intel.com/

cpu:
Processor Version Intel(R) Core(TM) i7-7820HK CPU @ 2.90GHz
Processor Voltage 89h - 0.9V
External Clock 100MHz
Max Speed 8300MHz
Current Speed 2800MHz

old drivers:
Aomei BackUpper driver
C:\Windows\system32\ammntdrv.sys Tue Dec 25 00:46:37 2012
C:\Windows\system32\amwrtdrv.sys Tue Dec 25 00:46:38 2012

Thanks for the input. I'm confused on one part, however: "I would remove it: use autoruns, locate the driver and uncheck the entry." What are you talking about here? Is it the XTU driver? This one has me scratching my head. I've had problems with XTU in the past, so I haven't used it since. I definitely did not install it on this OS. Regardless, I unchecked it with Autoruns, but then I decided to just delete it so it would never run, but an error window popped up saying it could not find the specified file. Upon clicking OK, the the xtuacpidriver.sys entry was removed from the list. It is still in my system32 folder, however.

I installed the most recent version of Aomei Backupper, though I might just uninstall it if the BSODs continue.

Also, I could not locate crystaldiskinfo.exe through the start menu or the run command. Is that a 3rd party software?

 

[johnbl]

google for crystaldiskinfo.exe or use any other utility that will read drive smart data.
(3rd party app)

the autoruns will remove the entry that causes the driver to load. it does not remove the driver from your system.
if you have a task scheduled, it might get re installed. some programs run a update in the task scheduler.

the driver was loaded at the time of the minidump. I have no idea what it was doing, just that it was a old version.

I would focus on updateing the intel tuning driver, it is much older than your cpu
and most likely will not work correctly with your updated bios
BIOS Release Date 09/10/2018

I would remove it: use autoruns, locate the driver and uncheck the entry.
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
I would suspect it is running a generic service host. you can go into services and see if there is entry.


I am not sure about your old backup program, they could also run as a generic service host.
they tend to work until there is some type of error.

you might look for a update to the software and run crystaldiskinfo.exe to see if your drive is having errors.
-------------
some program running as a generic service host (svchost.exe) caused the bugcheck

Intel extreme tuning BIOS interface driver
\SystemRoot\System32\drivers\XtuAcpiDriver.sys Thu Feb 26 04:51:57 2015
: http://downloadcenter.intel.com/

cpu:
Processor Version Intel(R) Core(TM) i7-7820HK CPU @ 2.90GHz
Processor Voltage 89h - 0.9V
External Clock 100MHz
Max Speed 8300MHz
Current Speed 2800MHz

old drivers:
Aomei BackUpper driver
C:\Windows\system32\ammntdrv.sys Tue Dec 25 00:46:37 2012
C:\Windows\system32\amwrtdrv.sys Tue Dec 25 00:46:38 2012

Thanks for the input. I'm confused on one part, however: "I would remove it: use autoruns, locate the driver and uncheck the entry." What are you talking about here? Is it the XTU driver? This one has me scratching my head. I've had problems with XTU in the past, so I haven't used it since. I definitely did not install it on this OS. Regardless, I unchecked it with Autoruns, but then I decided to just delete it so it would never run, but an error window popped up saying it could not find the specified file. Upon clicking OK, the the xtuacpidriver.sys entry was removed from the list. It is still in my system32 folder, however.

I installed the most recent version of Aomei Backupper, though I might just uninstall it if the BSODs continue.

Also, I could not locate crystaldiskinfo.exe through the start menu or the run command. Is that a 3rd party software?

 

[hell3on5wheels7]

google for crystaldiskinfo.exe or use any other utility that will read drive smart data.
(3rd party app)

the autoruns will remove the entry that causes the driver to load. it does not remove the driver from your system.
if you have a task scheduled, it might get re installed. some programs run a update in the task scheduler.

the driver was loaded at the time of the minidump. I have no idea what it was doing, just that it was a old version.

I know how the program works; I was just pointing out how odd it was that Autoruns would not let me delete the entry because it said it could not find the file. Yet, I found the file right where it was supposed to be. Deleting the entry would have been more secure than unchecking it, since it would have prevented it from ever being executed, but unchecking it was all it allowed me to do.

I have restarted my computer and do not see it running.

Crystaldiskinfo does not show any errors.