I have been continuously having issues with my HP Envy x360 m6 Convertible (Serial # 8CG6293BJL) due to sudden reboots that turned out to be crashes, according to my dump files. I have thoroughly updated my drivers and checked my HARDWARE, but there doesn't seem to be a problem with either of those. I even conducted stress testing and nothing seemed to happen. The laptop is cooled by a USB powered cooling fan, and the temperatures do not seem to go high enough to cause a  thermal issue. The most recent crash happened when running a Game Boy Advance emulator, the video and sound began to freeze and stutter, and then it rebooted. Before, when a game application wasn't open, it would simply turn off without noise. I do not know if this is of any significance to my problem. Anyways, I posted the dump files using BLUESCREENVIEW, and I hope someone can help me. Currently, due to extenuating circumstances and the non compliance of HP despite being under warranty, I cannot do much to test with the hardware at present or send it to HP to be looked at. Thank you in advance.

==================================================
Dump File         : 080717-30984-01.dmp
Crash Time        : 8/7/2017 5:35:25 PM
Bug Check String  :
Bug Check Code    : 0x00000124
Parameter 1       : 00000000`00000000
Parameter 2       : ffff9685`18bd3038
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+72119b
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 10.0.15063.483 (WinBuild.160101.0800)
Processor         : x64
Crash Address     : ntoskrnl.exe+72119b
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\WINDOWS\Minidump\080717-30984-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 15063
Dump File Size    : 262,144
Dump File Time    : 8/7/2017 5:35:46 PM
==================================================

==================================================
Dump File         : 080117-31390-01.dmp
Crash Time        : 8/1/2017 11:08:39 AM
Bug Check String  :
Bug Check Code    : 0x00000124
Parameter 1       : 00000000`00000000
Parameter 2       : ffff9981`c26e0038
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+72119b
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 10.0.15063.483 (WinBuild.160101.0800)
Processor         : x64
Crash Address     : ntoskrnl.exe+72119b
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\WINDOWS\Minidump\080117-31390-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 15063
Dump File Size    : 262,144
Dump File Time    : 8/1/2017 11:09:01 AM
==================================================

==================================================
Dump File         : 072817-24390-01.dmp
Crash Time        : 7/28/2017 6:42:01 PM
Bug Check String  :
Bug Check Code    : 0x00000124
Parameter 1       : 00000000`00000000
Parameter 2       : ffffe60d`a25d9038
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+72119b
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 10.0.15063.483 (WinBuild.160101.0800)
Processor         : x64
Crash Address     : ntoskrnl.exe+72119b
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\WINDOWS\Minidump\072817-24390-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 15063
Dump File Size    : 262,144
Dump File Time    : 7/28/2017 6:42:18 PM
==================================================

purely from a trouble shooting point of view, you have to eliminate a few of the variables.
at the moment it could almost be anything.

first up, from my (limited) experience with game emulators, they can be buggy so the emulator software itself can't be ruled out as the cause.
does it only happen when playing games?

does it happen if just using the laptop for Word, Internet, sort of activities?

can you run it from Safe Mode for a few hours to see if the BSOD happens there as well.
if not, it put more EMPHASIS on drivers being the issue.

also, long shot, you have .483 of Win10, .502 is the latest.No, it happens even when nothing is running actively. It has never happened in Safe Mode. As far as Windows Version is concerned, this occurred because I factory reset the computer after continually getting this problems, both with and without the creator's update. I will update that anyways, however.never happening in Safe Mode would put more of the blame on drivers.
or maybe memory modules.
or in general, software that is running during normal starts compared to software not running when in Safe Mode, like your AV software for example.

what is your AV, and if using one, have you tried not using it and just running Defender for a few days?

if you have clean installed Windows 10, than its native drivers should be OK, did you get any BSOD's straight after the clean install AND before you started loading the PC with your own software and updates?

and on the memory front, if multiple chips, have you tried swapping them over and just running on 1 for a while?I have used Defender and AVG, currently running Defender only. Yes, it has happened when running on base drivers and after updates. Memory wise, I did do a Memtest which came out clear but I can't really take the laptop apart and do memory swaps. Do you ever see the NEW BSOD screen?


Is Kernel Mode Dump File enabled?
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/enabling-a-kernel-mode-dump-fileNo I have never seen that. I have enabled it now, it was not previously enabled. Will I have to wait for another crash to get the right dump logs?Yes.Instead of crashing this time, it froze and the audio was making a weird buzzing noise. It seemed to be stuck on a NOTE. It wouldn't turn off. I forced a hard reboot, and there seems to be no record of what happened in crash logs. It might be worth testing this computer with memtest86 to be sure you dont have a RAM stick with a bad address that is causing the problem. This tool is free to use. https://www.memtest86.com/

Other thing that comes to mind is if the hard drive is acting up it can cause a problem with swap space / page file corruption between what is written to the drive and re-read back to RAM. So test the hard drive with CrystalDiskInfo to make sure no warnings with the health of the drive. This tool is free and will read in the S.M.A.R.T data off the drive which will give you all sorts of info about your hard drive or SSD including an idea as to if its healthy or not. https://osdn.net/projects/crystaldiskinfo/downloads/68126/CrystalDiskInfo7_1_1.zip/I think he should check device manager for any Yellow !!'s...

Sounds like missing/corrupt drivers to me.Check if you have IDT Audio on your machine.  If you do simply uninstall it & then restart your machine