BSOD ntoskrnl.exe

I just don't want you or anyone else to get banned for violating forum rules.

Thank you for posting the information about the Adobe products.
It has been validated and we can provide help.
There were 2 BSOD mini dump files and the debugging did not display a definitive misbehaving driver.
They were bugcheck 109 and D1.
Problems with RAM were ruled out by an 8 pass Memtest86+.
Please elaborate on the hardware changes that were made and what hardware tests were performed.
On the Dell website there are diagnostic tests. Please run the full tests and report results into the thread.

zbook said:

Thank you for posting the information about the Adobe products.
It has been validated and we can provide help.
There were 2 BSOD mini dump files and the debugging did not display a definitive misbehaving driver.
They were bugcheck 109 and D1.
Problems with RAM were ruled out by an 8 pass Memtest86+.
Please elaborate on the hardware changes that were made and what hardware tests were performed.
On the Dell website there are diagnostic tests. Please run the full tests and report results into the thread.

Will do. Here's an "out-there" question. Can an anti-virus program cause the bugcheck 109 and D1 errors? My Surface Pro 4 just suffered a BSOD and it happened directly after Kaspersky did an application update. I have disabled Kaspersky on my Desktop and SP4 to diagnose if it can be contributing to the BSODs.

AV products are one of the most common causes of misbehaving software drivers.
It is often best to uninstall AV products during troubleshooting and then reinstall them after 2 weeks of a stable computer environment. Then if you get an immediate BSOD you know that you will need a different AV product. If there are no BSOD then you can continue using the AV product.
The uninstall and reinstall provides fresh drivers.
Kaspersky Anti-Virus Remover - Download

I removed Kaspersky using the tool posted in the thread. Had another BSOD today, a memory management error.

1) Please elaborate on the hardware changes that were made and what hardware tests were performed.
2) On the Dell website there are diagnostic tests. Please run the full tests and report results into the thread.
3) After the above steps see post #12.
4) Create a brand new restore point.
5) Turn on Windows driver verifier.

zbook said:

1) Please elaborate on the hardware changes that were made and what hardware tests were performed.

Not sure what hardware change you are referring to. Dell replaced the motherboard via depot service about 2 months ago. That's the only hardware change I can think of.

zbook said:

2) On the Dell website there are diagnostic tests. Please run the full tests and report results into the thread.

Do you have a link to the diagnostic test files? A search turned up nothing.

zbook said:

4) Create a brand new restore point.

On recommendation, I turned off system restore and was told never to use it.

zbook said:

5) Turn on Windows driver verifier.

Post 12 stated to turn Windows Driver Verifier off. I should turn it back on now?

Please set up system restore so that it available (3rd method to turn off ) when using windows driver verifier.
There was information posted on September 25, 2017 in post #12 on how to use windows driver verifier.
For the Dell diagnostics run the full tests:
Support for Alienware 17 R3 | Diagnostics | Dell US

zbook said:

Please set up system restore so that it available (3rd method to turn off ) when using windows driver verifier.
There was information posted on September 25, 2017 in post #12 on how to use windows driver verifier.
For the Dell diagnostics run the full tests:
Support for Alienware 17 R3 | Diagnostics | Dell US

Thank you for the reply. I ran the quick test and full test. No issues present. I have not ran Fumark on my GPU (was waiting for the heatsink to be replaced before I did so), but I did disable the Sound Blaster Audio Service and see if that stabilized things. It did not, but I quickly realized I have a USB Sound Blaster card I was not accounting for. Disabling it (by unplugging), I've not had a BSOD in several days. I will run the driver verifier if another BSOD occurs.