BSOD playing Heavy Modded Skyrim SE bugcheck 0x0000000a

Hello - I just got a BSOD stop code and I want to know why.

Something you should know. I heavily customized my Windows 10 Pro install with NTLite and removed All Win10 Apps and Defender and injected system drivers.

I also use Qualcomm Atheros Wireless. I think maybe this was caused from my Qualcomm Atheros Wireless Drivers because sometimes my Wifi can be weird about connecting to Networks like not connecting at all or showing "ghost networks".

Should I use the Wireless driver from my Laptop's driver page or can I grab a later version from Qualcomm?

My Skyrim Mod List for people interested. Be funny if a Mod was causing this. Unlikely tho I think.
GitHub - Wh1t3Rose/SkyrimSE-LaptopEdition: This project is was created for laptop players to get the best modded experience possible while maintaining good FPS.

Thanks!

Edit 1: Sorry I am using Qualcomm Atheros Drivers. Not Intel. I got confused with my other laptop. Sorry!

Hello Wh1t3Rose :)

Welcome to Ten Forums

I looked at the files you captured but unfortunately there were no BSOD mini-dumps created.

The eventlog shows the following:

Code:

2018-04-13T18:53:06.878		Dump file creation failed due to error during dump creation.
2018-04-13T18:53:10.482		The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
2018-04-13T18:53:59.122		Unable to produce a minidump file from the full dump file.
2018-04-13T18:53:59.122		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0xffff86046cb31204, 0x0000000000000002, 0x0000000000000001, 0xfffff8020b3fce99). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.

Make sure your system is set up as shown below, I think it probably is but it would be worth checking. By not having the system automatically restart you should get longer to see the BSOD and take a picture of it.
Attachment 184724

Also you could try using the beta10 log collector at the end of the BSOD posting instructions - this sometimes captures more information that can be helpful.

philc43 said:

Hello Wh1t3Rose :)

Welcome to Ten Forums

I looked at the files you captured but unfortunately there were no BSOD mini-dumps created.

The eventlog shows the following:

Code:

2018-04-13T18:53:06.878        Dump file creation failed due to error during dump creation.
2018-04-13T18:53:10.482        The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
2018-04-13T18:53:59.122        Unable to produce a minidump file from the full dump file.
2018-04-13T18:53:59.122        The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0xffff86046cb31204, 0x0000000000000002, 0x0000000000000001, 0xfffff8020b3fce99). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.

Make sure your system is set up as shown below, I think it probably is but it would be worth checking. By not having the system automatically restart you should get longer to see the BSOD and take a picture of it.
Attachment 184724

Also you could try using the beta10 log collector at the end of the BSOD posting instructions - this sometimes captures more information that can be helpful.

You know what. I think this was just caused by bad UV settings I had in XTU and was just unaware. I think this would explain why BSOD logs weren't created perhaps? I checked my settings and they were correct.

I have fixed my UV and if I don't have any BSODs by tomorrow I am going to mark this as solved. Sorry again. I thought my UV settings were stable but I guess that what I get for reported BSOD issues while undervolted! Should have been obvious!

Thanks!