F5F Stay Refreshed Hardware Desktop Your computer crashes unexpectedly and restarts.

Your computer crashes unexpectedly and restarts.

Your computer crashes unexpectedly and restarts.

Pages (3): 1 2 3 Next
F
FinaLBaTTLe
Member
61
12-15-2022, 10:13 PM
#1
I'm experiencing a black screen after the BIOS update. Restarted and managed to reach the recovery mode with issues. My motherboard displays a Q code white with code 70. Cleared the SD card on the ASUS rog crosshair x670 hero CPU AMD Ryzen 9 7950x RAM G.SKill Ripjaw s5 128GB 4x32GB 5200 DDR5 GPU Zotac Gaming GeForce RTX 3090 Ti running Windows 11 Pro 2 Nvme Samsung 970 Evo Pro 2TB, western digit green both 2TB. Photo of the event.
F
FinaLBaTTLe
12-15-2022, 10:13 PM #1

I'm experiencing a black screen after the BIOS update. Restarted and managed to reach the recovery mode with issues. My motherboard displays a Q code white with code 70. Cleared the SD card on the ASUS rog crosshair x670 hero CPU AMD Ryzen 9 7950x RAM G.SKill Ripjaw s5 128GB 4x32GB 5200 DDR5 GPU Zotac Gaming GeForce RTX 3090 Ti running Windows 11 Pro 2 Nvme Samsung 970 Evo Pro 2TB, western digit green both 2TB. Photo of the event.

H
HubixCube
Member
166
12-23-2022, 09:39 AM
#2
Searching the web I discovered details about Event Error Code 41. This issue appears when a computer powers off or restarts abruptly. During Windows startup, the system verifies if the shutdown was complete. If not, a Kernel Power Event 41 alert is triggered.
H
HubixCube
12-23-2022, 09:39 AM #2

Searching the web I discovered details about Event Error Code 41. This issue appears when a computer powers off or restarts abruptly. During Windows startup, the system verifies if the shutdown was complete. If not, a Kernel Power Event 41 alert is triggered.

C
cdogjuly
Junior Member
12
12-23-2022, 02:37 PM
#3
I checked online but it doesn’t match what you expect. Before the crash, there was an event that occurred prior to it. The image captured shows it just before Kernel Power Event 41. According to some details I found on Microsoft’s support site, the issue might stem from a corrupted system file. In certain cases, this error can arise due to underlying file corruption that prevents your system from handling DCOM events properly. To resolve it, consider running DISM and SFC scans, then proceed with a clean or repair installation if the problem continues. Both tools can be executed together for better results. Make sure to run them from an elevated command prompt and see if the error persists after rebooting. If it does, a full OS reinstall may be necessary.
C
cdogjuly
12-23-2022, 02:37 PM #3

I checked online but it doesn’t match what you expect. Before the crash, there was an event that occurred prior to it. The image captured shows it just before Kernel Power Event 41. According to some details I found on Microsoft’s support site, the issue might stem from a corrupted system file. In certain cases, this error can arise due to underlying file corruption that prevents your system from handling DCOM events properly. To resolve it, consider running DISM and SFC scans, then proceed with a clean or repair installation if the problem continues. Both tools can be executed together for better results. Make sure to run them from an elevated command prompt and see if the error persists after rebooting. If it does, a full OS reinstall may be necessary.

C
Camillah
Member
68
12-30-2022, 10:58 PM
#4
Here are your details organized for clarity:
OS requirements: Windows 8.1, 8, 7, Vista – x86 (32-bit) or x64?
Original OS: What version was originally installed? OEM or full retail purchase?
System age: Hardware age – has the OS been reinstalled?
CPU: Model
Video Card: Model
Motherboard: (applicable for laptops)
Power Supply: Brand and wattage (laptop excluded)
Manufacturer: Exact model number (if applicable)
Type of device: Laptop or desktop?
Purpose: Gaming, idle, startup from standby? Any additional notes?
C
Camillah
12-30-2022, 10:58 PM #4

Here are your details organized for clarity:
OS requirements: Windows 8.1, 8, 7, Vista – x86 (32-bit) or x64?
Original OS: What version was originally installed? OEM or full retail purchase?
System age: Hardware age – has the OS been reinstalled?
CPU: Model
Video Card: Model
Motherboard: (applicable for laptops)
Power Supply: Brand and wattage (laptop excluded)
Manufacturer: Exact model number (if applicable)
Type of device: Laptop or desktop?
Purpose: Gaming, idle, startup from standby? Any additional notes?

M
MineBaros
Member
57
01-01-2023, 08:20 AM
#5
Windows 11 Pro 64-bit New PC from a brand new machine. This year's CPU is Ryzen 9 7950x paired with an Nvidia RTX 3090 Ti. It comes with an Asus ROG Crosshair X670E and a PSU from EVGA. It only activates when idle for more than two hours.
M
MineBaros
01-01-2023, 08:20 AM #5

Windows 11 Pro 64-bit New PC from a brand new machine. This year's CPU is Ryzen 9 7950x paired with an Nvidia RTX 3090 Ti. It comes with an Asus ROG Crosshair X670E and a PSU from EVGA. It only activates when idle for more than two hours.

F
frog76
Member
177
01-02-2023, 08:30 PM
#6
Update the UEFI/BIOS to the latest version released recently. Install the chipset drivers that were just released. Check if this resolves the problem.
F
frog76
01-02-2023, 08:30 PM #6

Update the UEFI/BIOS to the latest version released recently. Install the chipset drivers that were just released. Check if this resolves the problem.

L
limonadenbubi
Member
149
01-03-2023, 10:09 PM
#7
Event 41 simply indicates the PC wasn't powered off correctly, such as when it crashes unexpectedly or when you press the power button or PSU switch while the system is running. This isn't the main issue. Focus on the screenshot for the BugCheck event occurring near Event 41. Determine what kind of Bug Check it is—Bug Check refers to the formal term for a BSOD. Even without a blue screen, Windows logs an entry in Event Viewer and creates a dump file for further analysis after a restart.
L
limonadenbubi
01-03-2023, 10:09 PM #7

Event 41 simply indicates the PC wasn't powered off correctly, such as when it crashes unexpectedly or when you press the power button or PSU switch while the system is running. This isn't the main issue. Focus on the screenshot for the BugCheck event occurring near Event 41. Determine what kind of Bug Check it is—Bug Check refers to the formal term for a BSOD. Even without a blue screen, Windows logs an entry in Event Viewer and creates a dump file for further analysis after a restart.

S
StarKillerSTF
Member
125
01-03-2023, 11:44 PM
#8
Lately everything changed. Yesterday.
S
StarKillerSTF
01-03-2023, 11:44 PM #8

Lately everything changed. Yesterday.

G
GimlixNL
Member
145
01-04-2023, 09:20 AM
#9
I understand that. I shared the photo from the previous event before Event 41.
G
GimlixNL
01-04-2023, 09:20 AM #9

I understand that. I shared the photo from the previous event before Event 41.

S
StrueBlue
Junior Member
16
01-04-2023, 12:06 PM
#10
It's a 0xA bug check, also known as IRQL_NOT_LESS_OR_EQUAL. This is typically a driver-related issue. Visit WhoCrashed, select "analyze," and identify the affected driver.
S
StrueBlue
01-04-2023, 12:06 PM #10

It's a 0xA bug check, also known as IRQL_NOT_LESS_OR_EQUAL. This is typically a driver-related issue. Visit WhoCrashed, select "analyze," and identify the affected driver.

Pages (3): 1 2 3 Next