Windows 10: I keep getting BSOD and run the minidump and it generate this

oading unloaded module list.............For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff806`42c16ae0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffb8c`450a7270=000000000000000a6: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ****************************************

:)

 

Minidumps not generated after a bluescreen in Win8.1

Lenovo Flex 2-14, windows 8.1 64bit, 4GB RAM, 8SSD-500HDD. All software setup from factory.

The laptop freezes randomly without any pattern and BSOD.

The bluescreen says kernel_data_inpage_error and collecting more info is stuck at 0%. It never progresses and I have to hard power down the laptop. After reboot, there are no minidumps generated(minidump is enabled in adv. settings). Sometime the BSOD also gives another additional info in braces (ntoskernal.sys, volmgr.sys, and few other). occurs at least once every one/two day. Any reason why Minidump is not generated?

Sometimes the laptop also restarts for no reason and shows up the windows boot manager which does not lists the HDD. Is it that HDD is not detected and is it related to the above problem?

The HDD is GPT partioned with UEFI boot enabled. After a lot of factory resets, and even after upgrading to win10, had the BSOD issues.

Someone suggested to change the boot option to legacy. Now I have factory image restored (win8.1) in GPT HDD with leagcy first boot option. I have used the the laptop for a couple of days and the BSOD did not occur till now. Is this a right solution?

Is this a hardware problem because This BSOD occurred in the middle of HDD partitioning after rebooting in AOEMI partition assistant and once while upgrading to win10.(loose cable maybe, but its a brand new laptop and the issue occurred even before putting on any new software) or caused by the boot options?

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.

 

BSOD Driver_Power_State_Failure minidump

Every so often I get BSODs due to Driver Power State Failure. I've tried the conventional wisdom of reinstalling corrupt drivers in Safe Mode w/ Networking, but to no avail. I saved a minidump of the most recent crash, but I had problems trying to analyze it in WinDBG (something about incorrect symbol paths... at that point it was too technical for me to comprehend). Could someone please analyze this minidump and advise how to prevent future BSODs?
Many thanks

Running Windows 10 Home 1803 (build 17134) on Asus Q302LA, SMBIOS version 2.7