F5F Stay Refreshed Hardware Desktop Need assistance with the PC blue screen? Let me know what you're experiencing.

Need assistance with the PC blue screen? Let me know what you're experiencing.

Need assistance with the PC blue screen? Let me know what you're experiencing.

Pages (2): 1 2 Next
L
Lacomas
Junior Member
48
05-20-2024, 01:28 AM
#1
Hey, my pc has been bluescreening every now and then, its like every 1-4weeks it bluescreens once, so its pretty rarely, but it would be nice to be able to fix it still some specs 32gb ram i7 14700k rtx 4070 ti super ================================================== Dump File : 082524-5156-01.dmp Crash Time : 25/08/2024 13.14.38 Bug Check String : Bug Check Code : 0x00000124 Parameter 1 : 00000000`00000004 Parameter 2 : ffff8809`fd7f4028 Parameter 3 : 00000000`00000000 Parameter 4 : 00000000`00000000 Caused By Driver : PSHED.dll Caused By Address : PSHED.dll+10c0 File Description : Platform Specific Hardware Error Driver Product Name : Microsoft® Windows® Operating System Company : Microsoft Corporation File Version : 10.0.22621.1 (WinBuild.160101.0800) Processor : x64 Crash Address : ntoskrnl.exe+415cb0 Stack Address 1 : Stack Address 2 : Stack Address 3 : Computer Name : Full Path : C:\Windows\Minidump\082524-5156-01.dmp Processors Count : 28 Major Version : 15 Minor Version : 22621 Dump File Size : 5 856 376 Dump File Time : 25/08/2024 13.15.01 ==================================================
L
Lacomas
05-20-2024, 01:28 AM #1

Hey, my pc has been bluescreening every now and then, its like every 1-4weeks it bluescreens once, so its pretty rarely, but it would be nice to be able to fix it still some specs 32gb ram i7 14700k rtx 4070 ti super ================================================== Dump File : 082524-5156-01.dmp Crash Time : 25/08/2024 13.14.38 Bug Check String : Bug Check Code : 0x00000124 Parameter 1 : 00000000`00000004 Parameter 2 : ffff8809`fd7f4028 Parameter 3 : 00000000`00000000 Parameter 4 : 00000000`00000000 Caused By Driver : PSHED.dll Caused By Address : PSHED.dll+10c0 File Description : Platform Specific Hardware Error Driver Product Name : Microsoft® Windows® Operating System Company : Microsoft Corporation File Version : 10.0.22621.1 (WinBuild.160101.0800) Processor : x64 Crash Address : ntoskrnl.exe+415cb0 Stack Address 1 : Stack Address 2 : Stack Address 3 : Computer Name : Full Path : C:\Windows\Minidump\082524-5156-01.dmp Processors Count : 28 Major Version : 15 Minor Version : 22621 Dump File Size : 5 856 376 Dump File Time : 25/08/2024 13.15.01 ==================================================

D
DarkStains
Member
149
05-21-2024, 05:40 AM
#2
Could these be early signs of CPU wear? Since it occurs infrequently, diagnosing it might be challenging. Update the BIOS and consider using one of Intel's profiles. Review the event log for additional information. Perform a memory test. Examine drive health and SMART data. Run the SFC /scannow utility. Inspect the Device Manager for alerts. Install updated drivers. If degradation is detected, you may need to return it via RMA or use the warranty from a reseller. Further issues will likely follow, so act promptly.
D
DarkStains
05-21-2024, 05:40 AM #2

Could these be early signs of CPU wear? Since it occurs infrequently, diagnosing it might be challenging. Update the BIOS and consider using one of Intel's profiles. Review the event log for additional information. Perform a memory test. Examine drive health and SMART data. Run the SFC /scannow utility. Inspect the Device Manager for alerts. Install updated drivers. If degradation is detected, you may need to return it via RMA or use the warranty from a reseller. Further issues will likely follow, so act promptly.

P
paperclip364
Member
174
05-21-2024, 09:15 AM
#3
I had already tried all these steps and believed I had completed SFC, but when I ran it there were some corrupt files. Hopefully this fixes the issue. I’ll update here if another BSOD occurs.
P
paperclip364
05-21-2024, 09:15 AM #3

I had already tried all these steps and believed I had completed SFC, but when I ran it there were some corrupt files. Hopefully this fixes the issue. I’ll update here if another BSOD occurs.

C
ChibiDusk
Member
164
05-21-2024, 05:42 PM
#4
There is a PCIe error detected. Please supply the dump files. These simple utilities are unreliable. If you need help, navigate to C:\Windows\Minidump and verify the presence of any minidump files. If available, return to your Windows directory and transfer the Minidump folder to the Downloads folder (using the desktop if necessary). Compress the copied folder and attach it to a message. Follow the provided steps carefully, as Windows does not permit modifications in this area.
C
ChibiDusk
05-21-2024, 05:42 PM #4

There is a PCIe error detected. Please supply the dump files. These simple utilities are unreliable. If you need help, navigate to C:\Windows\Minidump and verify the presence of any minidump files. If available, return to your Windows directory and transfer the Minidump folder to the Downloads folder (using the desktop if necessary). Compress the copied folder and attach it to a message. Follow the provided steps carefully, as Windows does not permit modifications in this area.

S
StyleTrick
Senior Member
744
05-22-2024, 02:11 AM
#5
Looking at the Minidump file, I hope it assists with resolving this troubleshooting issue.
S
StyleTrick
05-22-2024, 02:11 AM #5

Looking at the Minidump file, I hope it assists with resolving this troubleshooting issue.

G
gdog557
Member
218
05-22-2024, 06:20 AM
#6
The dump files provide the identifier for the PCIe port the device uses. While it might refer to a port, it usually points to the device itself. Launch Device Manager, then click View → Devices by Connection at the top. Navigate to ACPI X64-based PC → Microsoft ACPI-compatible system. Next, locate PCIe Root Complex and select it. We aim to identify the correct root port. If numbered, that’s sufficient; if not, you have two choices—either update the chipset driver (which may assign numbers) or manually inspect each port. Right-click on a root port (not the one you see when expanding) and choose Properties. In the new window, go to the Details tab and look for Hardware IDs in the dropdown. You should see "PCI\VEN_8086&DEV_A74D". The number 8086 indicates Intel, and DEV_A74D is the device identifier. Once you pinpoint the right port, expand it to confirm the connected device. EDIT 2: A reference image on Google displays root ports with a port number first, which we can’t use directly. The ID highlighted in red is A74D.
G
gdog557
05-22-2024, 06:20 AM #6

The dump files provide the identifier for the PCIe port the device uses. While it might refer to a port, it usually points to the device itself. Launch Device Manager, then click View → Devices by Connection at the top. Navigate to ACPI X64-based PC → Microsoft ACPI-compatible system. Next, locate PCIe Root Complex and select it. We aim to identify the correct root port. If numbered, that’s sufficient; if not, you have two choices—either update the chipset driver (which may assign numbers) or manually inspect each port. Right-click on a root port (not the one you see when expanding) and choose Properties. In the new window, go to the Details tab and look for Hardware IDs in the dropdown. You should see "PCI\VEN_8086&DEV_A74D". The number 8086 indicates Intel, and DEV_A74D is the device identifier. Once you pinpoint the right port, expand it to confirm the connected device. EDIT 2: A reference image on Google displays root ports with a port number first, which we can’t use directly. The ID highlighted in red is A74D.

O
oOEmmaOo
Posting Freak
818
05-23-2024, 06:21 AM
#7
It seems to be the NVME ssd, since this is a prebuilt pc, i checked the firmware and its up to date i also checked bios etc. Ive tried fixing the problem with a Samsung Magician Software, some people have reported that disabling some power saving thing has fixed this issue for them, but this SSD is not recognized by Samsung's software the model is, SAMSUNG MZVL41t0HBLB-00BLL.
O
oOEmmaOo
05-23-2024, 06:21 AM #7

It seems to be the NVME ssd, since this is a prebuilt pc, i checked the firmware and its up to date i also checked bios etc. Ive tried fixing the problem with a Samsung Magician Software, some people have reported that disabling some power saving thing has fixed this issue for them, but this SSD is not recognized by Samsung's software the model is, SAMSUNG MZVL41t0HBLB-00BLL.

T
techiseasy
Senior Member
688
06-02-2024, 09:10 PM
#8
You might reposition it or use a different M.2 slot if available, but a defective SSD seems most likely.
T
techiseasy
06-02-2024, 09:10 PM #8

You might reposition it or use a different M.2 slot if available, but a defective SSD seems most likely.

P
prxxl
Member
72
06-04-2024, 12:28 PM
#9
I have extra SATA SSDs, but I’m worried about the warranty if I handle the PC parts. I’m not sure. Also, I’ve heard it’s risky to use different PSU cables for SSDs, so I don’t think that’s safe. Maybe I should reach out to the seller and ask if I can reseat it without breaking the warranty. I’m really new to this, just setting up my first prebuilt system.
P
prxxl
06-04-2024, 12:28 PM #9

I have extra SATA SSDs, but I’m worried about the warranty if I handle the PC parts. I’m not sure. Also, I’ve heard it’s risky to use different PSU cables for SSDs, so I don’t think that’s safe. Maybe I should reach out to the seller and ask if I can reseat it without breaking the warranty. I’m really new to this, just setting up my first prebuilt system.

R
RJBboy
Junior Member
47
06-08-2024, 12:00 AM
#10
PCIe and CPU power aren't always consistent, yet I'm not familiar with SATA.
R
RJBboy
06-08-2024, 12:00 AM #10

PCIe and CPU power aren't always consistent, yet I'm not familiar with SATA.

Pages (2): 1 2 Next