F5F Stay Refreshed Hardware Desktop The PC is experiencing BSOD issues.

The PC is experiencing BSOD issues.

The PC is experiencing BSOD issues.

Pages (3): Previous 1 2 3 Next
T
TuhMarihuana
Junior Member
14
01-06-2021, 06:25 PM
#11
Other issues clearly point to faulty RAM. Try MemTest86 as well. Reset your BIOS settings and disable XMP or DOCP.
T
TuhMarihuana
01-06-2021, 06:25 PM #11

Other issues clearly point to faulty RAM. Try MemTest86 as well. Reset your BIOS settings and disable XMP or DOCP.

M
McPrettyKitty
Junior Member
4
01-07-2021, 12:42 AM
#12
Document IDs: 032123-254406-01.dmp, 032123-14812-01.dmp, 032123-12609-01.dmp
M
McPrettyKitty
01-07-2021, 12:42 AM #12

Document IDs: 032123-254406-01.dmp, 032123-14812-01.dmp, 032123-12609-01.dmp

C
CruelKush
Junior Member
11
01-07-2021, 03:17 AM
#13
Below I have attached the mini dump files. Sorry, it took a long time, it was quite an issue.
C
CruelKush
01-07-2021, 03:17 AM #13

Below I have attached the mini dump files. Sorry, it took a long time, it was quite an issue.

P
psykus
Member
154
01-25-2021, 08:06 PM
#14
Shut down every XMP setting but the problems persist.
P
psykus
01-25-2021, 08:06 PM #14

Shut down every XMP setting but the problems persist.

M
mateuszmamona
Member
174
01-31-2021, 08:42 PM
#15
No problem, I can't reach them at work. I'll have to wait until I'm home.
M
mateuszmamona
01-31-2021, 08:42 PM #15

No problem, I can't reach them at work. I'll have to wait until I'm home.

D
Derpycake777
Member
114
01-31-2021, 09:22 PM
#16
Thank you!
D
Derpycake777
01-31-2021, 09:22 PM #16

Thank you!

M
Monster_Q8
Junior Member
42
02-01-2021, 07:05 AM
#17
No problem, just checking in. What do you need help with?
M
Monster_Q8
02-01-2021, 07:05 AM #17

No problem, just checking in. What do you need help with?

J
Jihf_Jr
Member
87
02-01-2021, 04:23 PM
#18
Ummm...ahhh...errr...why yes, totally I really just (did not) download the files and look them over Many apologies for the delay, give me a few to look them over, and I'll post my thoughts. Hold Please!
J
Jihf_Jr
02-01-2021, 04:23 PM #18

Ummm...ahhh...errr...why yes, totally I really just (did not) download the files and look them over Many apologies for the delay, give me a few to look them over, and I'll post my thoughts. Hold Please!

S
soldier_craft
Member
242
02-07-2021, 02:48 AM
#19
I’m reviewing the relevant sections of the BSoDs. Below are my observations:

- Crash #1 SHOWED A SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M error (1000007e). This is typical—usually the pinpoints a driver or function. Keep track of the address and the driver/image link. Common issues include exception code 0x80000003, which suggests a hard-coded breakpoint or assertion. This shouldn’t occur in production code since developers should avoid such hardcodes. If it does, connect a debugger and ensure DEBUG mode is enabled to investigate further.

- Crash #2 INVOLVED A SYSTEM_SERVICE_EXCEPTION (3b). The exception triggered during a service routine. Key details: the instruction address, context record, and process name were captured. This indicates a deeper issue possibly related to service handling or memory access.

- Crash #3 REPEATS THE SAME WARNING ABOUT HARD CODE. Despite a fresh Windows 10/11 install and a stable BIOS, the crashes persist. This points toward potential hardware problems—especially with RAM. If the system remains unstable, it’s likely a hardware fault rather than software.

Overall, the pattern suggests recurring issues tied to unhandled exceptions or memory errors, possibly exacerbated by recent updates.
S
soldier_craft
02-07-2021, 02:48 AM #19

I’m reviewing the relevant sections of the BSoDs. Below are my observations:

- Crash #1 SHOWED A SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M error (1000007e). This is typical—usually the pinpoints a driver or function. Keep track of the address and the driver/image link. Common issues include exception code 0x80000003, which suggests a hard-coded breakpoint or assertion. This shouldn’t occur in production code since developers should avoid such hardcodes. If it does, connect a debugger and ensure DEBUG mode is enabled to investigate further.

- Crash #2 INVOLVED A SYSTEM_SERVICE_EXCEPTION (3b). The exception triggered during a service routine. Key details: the instruction address, context record, and process name were captured. This indicates a deeper issue possibly related to service handling or memory access.

- Crash #3 REPEATS THE SAME WARNING ABOUT HARD CODE. Despite a fresh Windows 10/11 install and a stable BIOS, the crashes persist. This points toward potential hardware problems—especially with RAM. If the system remains unstable, it’s likely a hardware fault rather than software.

Overall, the pattern suggests recurring issues tied to unhandled exceptions or memory errors, possibly exacerbated by recent updates.

A
Astro_bot
Member
50
02-07-2021, 11:14 AM
#20
The driver section offers options to remove and reinstall all drivers. You can try uninstalling everything and restarting, especially since you've recently reinstalled Windows multiple times. Talking to your brother-in-law using his RAM might help confirm if the issue persists. It’s possible both RAM sticks are faulty. I’ll keep you informed and appreciate your patience.
A
Astro_bot
02-07-2021, 11:14 AM #20

The driver section offers options to remove and reinstall all drivers. You can try uninstalling everything and restarting, especially since you've recently reinstalled Windows multiple times. Talking to your brother-in-law using his RAM might help confirm if the issue persists. It’s possible both RAM sticks are faulty. I’ll keep you informed and appreciate your patience.

Pages (3): Previous 1 2 3 Next