HELP!! BSOD BOOT ERROR Network media Not Present

Hi.

I have had my PCS laptop for 2 years and today I got a BSOD whilst surfing out of nowhere. Not had one before. Now I just get a boot error when turning on.
'Network Media Not Found' followed by this error 'EFI PXE 0 for IPv4 (D4-93-90-1A-5F-9E) boot failed . Defualt boot device missing

In my boot manager my only options are EFI PXE 0 for IPv6
And EFI PXE 0 for IPv4
Both do nothing.

In setup manager it SATA port 1 not present?

Does anyone know what to do? I'm stuck and have no idea how to fix this? Very concerned.

Here is my system specs
Chassis & Display
Lafité Pro Series: 15.6" Matte Full HD 60Hz 72% NTSC LED Widescreen (1920x1080)
Processor (CPU)
Intel® Core™ i7 12 Core Processor 1260P (2.1GHz, 4.7GHz Turbo)
Memory (RAM)
64GB PCS PRO SODIMM DDR4 2666MHz (2 x 32GB)
Graphics Card
Integrated Intel® Iris® Xe Graphics
1st M.2 SSD Drive
2TB SOLIDIGM P41+ GEN 4 M.2 NVMe PCIe SSD (up to 4125MB/sR, 3325MB/sW)
2nd M.2 SSD Drive
2TB SOLIDIGM P41+ GEN 4 M.2 NVMe PCIe SSD (up to 4125MB/sR, 3325MB/sW)
Memory Card Reader
Integrated Micro-SD Memory Card Reader
AC Adaptor
1 x 90W AC Adaptor
Power Cable
1 x 1.5 Metre Cloverleaf UK Power Cable
Battery
Lafité Pro Series Integrated 73WH Lithium Ion Battery
Sound Card
2 Channel High Definition Audio + MIC/Headphone Jack
Bluetooth & Wireless
GIGABIT LAN & KILLER™ Wi-Fi 6E AX1675 M.2 GAMING + BLUETOOTH 5.3
USB/Thunderbolt Options
1 x THUNDERBOLT 4 + 1 x USB 3.2 (TYPE C) + 1 x USB 3.2 + 1 x USB 2.0
Keyboard Language
LAFITÉ PRO 15 SERIES BACKLIT UK KEYBOARD
Operating System
Windows 11 Home 64 Bit - inc. Single Licence [KUK-00003]
 

Attachments

  • 20241102_212737.jpg
    20241102_212737.jpg
    705.7 KB · Views: 18
  • 20241102_212915.jpg
    20241102_212915.jpg
    754.2 KB · Views: 13
Thanks for the reply. And clearing that up. I don't think I was issued with a windows disk? I belive it came with the install already done. I still have the product key. Can I download and install on a USB pen?
 
Okay so after taking the system apart to check loose connections, and not finding any, the system has now booted. It gave me the same errors but after mutiple boot cycles it has now booted and everything seems okay.

FIrst thing I did was look at Event Viewer for any diagnostics on the BSOD. There were various Criticals logged both around crash and during startup post crash. Around the crash was this:

A fatal error occurred while creating a TLS client credential. The internal error state is 10013.
The SSPI client process is Integrator (PID: 544).

There were various interal state and PID variations but all related to TLS clinet credential errors

After booting up I have noticed the following criticals logged:
The GameInput Service service terminated with the following error:
The compound file GameInput Service was produced with a newer version of storage.

I've uninstalled Microsoft Gaming Services to help with that.

More TLS Critcal warnings:
A fatal error occurred while creating a TLS client credential. The internal error state is 10013.
The SSPI client process is OfficeClickToRun (PID: 4812).

ALso have these Warnings (not criticals):
The description for Event ID 6062 from source Netwtw14 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\NDMP3
Killer(R) Wi-Fi 6E AX1675x 160MHz Wireless Network Adapter (210NGW)

The message resource is present but the message was not found in the message table


and

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscCloudBackupProvider

and APPID
Unavailable

to the user Nostromo\chris SID (S-1-5-21-2612480724-3768864445-575692886-1005) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.


I dont see anything there to explain why my drives were not booting or showing up in Bios. Im scared to restart the system now incase it happens again. As I said it seemed to simply boot out of random luck given it went through the 'Network Media Not Present' cycle numerous times before suddenly working? Perhaps it really is loose connections on the motherboard. Or failing ports?
 

SpyderTracks

We love you Ukraine
Okay so after taking the system apart to check loose connections, and not finding any, the system has now booted. It gave me the same errors but after mutiple boot cycles it has now booted and everything seems okay.

FIrst thing I did was look at Event Viewer for any diagnostics on the BSOD. There were various Criticals logged both around crash and during startup post crash. Around the crash was this:

A fatal error occurred while creating a TLS client credential. The internal error state is 10013.
The SSPI client process is Integrator (PID: 544).

There were various interal state and PID variations but all related to TLS clinet credential errors

After booting up I have noticed the following criticals logged:
The GameInput Service service terminated with the following error:
The compound file GameInput Service was produced with a newer version of storage.

I've uninstalled Microsoft Gaming Services to help with that.

More TLS Critcal warnings:
A fatal error occurred while creating a TLS client credential. The internal error state is 10013.
The SSPI client process is OfficeClickToRun (PID: 4812).

ALso have these Warnings (not criticals):
The description for Event ID 6062 from source Netwtw14 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\NDMP3
Killer(R) Wi-Fi 6E AX1675x 160MHz Wireless Network Adapter (210NGW)

The message resource is present but the message was not found in the message table


and

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscCloudBackupProvider

and APPID
Unavailable

to the user Nostromo\chris SID (S-1-5-21-2612480724-3768864445-575692886-1005) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.


I dont see anything there to explain why my drives were not booting or showing up in Bios. Im scared to restart the system now incase it happens again. As I said it seemed to simply boot out of random luck given it went through the 'Network Media Not Present' cycle numerous times before suddenly working? Perhaps it really is loose connections on the motherboard. Or failing ports?
Whilst the system is still on, can you follow the process listed here by @Scott in the last post to gather the SysNative Logs, then hopefully @ubuysa will be able to take a look when he's next on, he's a wizard with this kind of thing

 
Thank you SpyderTracks I can report that this morning having put the system into HIbernate overnight, I was greeted with the same failed boot sequence however after one cycle and pressing F10 to enter Bios, the system booted correctly. I have downloaded Sysnative and run the diagnostic. a few steps were skipped after taking too long to generate the files. Dont know if that is something to be concerned with. I have uploaded the .zip results below. Any help would be extremely welcome as it seems whatever caused this is still not fixed.
 
Last edited:
Hmm unless im missing something, I do not seem to able to attach the .zip to this post as .zip isnt a recognised file format, yet the readme says to attach the .zip this way? I am supposed to upload to Sysnative's own forum I guess? I will do that there.
 
Last edited:

SpyderTracks

We love you Ukraine
Hmm unless im missing something, I do not seem to able to attach the .zip to this post as .zip isnt a recognised file format, yet the readme says to attach the .zip this way?
You can’t attach it to the forum, need to upload it to cloud storage, make it public and post a link
 
Last edited:

ubuysa

The BSOD Doctor
Please make the Dropbox file public so that I don't have to request access.

One important question: @SpyderTracks asked whether you can boot the Windows installation media?

You'll need another PC/laptop or a friend's PC/laptop to make a bootable USB drive containing the Windows installation files. You do that by downloading the Windows media creation tool from https://www.microsoft.com/en-gb/software-download/windows11. Select the 'Create Windows Installation Media' option and when the tool has downloaded plug in an 8GB minimum size USB drive and run the downloaded media creation tool.

Once you have a USB drive with Windows install media on it, plug that drive into your PC and boot from the USB drive. You may need to enter the BIOS setup to change the boot drive order to do that. ONce it's booted choose the 'Repair my computer' option.

What we want to know is a) does the Windows installation system boot and b) does it crash or BSOD running that installation system?
 
Apologies I thought I had made that public. I have updated not so it should be accessilbe to all with the link:

As for running windows repair I can do this now.
 
Please make the Dropbox file public so that I don't have to request access.

One important question: @SpyderTracks asked whether you can boot the Windows installation media?

You'll need another PC/laptop or a friend's PC/laptop to make a bootable USB drive containing the Windows installation files. You do that by downloading the Windows media creation tool from https://www.microsoft.com/en-gb/software-download/windows11. Select the 'Create Windows Installation Media' option and when the tool has downloaded plug in an 8GB minimum size USB drive and run the downloaded media creation tool.

Once you have a USB drive with Windows install media on it, plug that drive into your PC and boot from the USB drive. You may need to enter the BIOS setup to change the boot drive order to do that. ONce it's booted choose the 'Repair my computer' option.

What we want to know is a) does the Windows installation system boot and b) does it crash or BSOD running that installation system?
I have made a setup installation disk on a flash drive.

however just so we're on the same page, I can now boot my laptop to windows. Though there is still boot fail warnings from the BIOS it will boot to windows after a few cycles. So I wouldn't need an additional laptop or computer to make a bootable windows disk. Ergo do I need to run this step, or can we get the same info from a diagnostic run from windows? I would rather not power-cycle my system unless it is needed at the moment.
 
Top