F5F Stay Refreshed Hardware Desktop Error code BSOF indicating a page fault in non-paged area.

Error code BSOF indicating a page fault in non-paged area.

Error code BSOF indicating a page fault in non-paged area.

Pages (2): Previous 1 2
K
Kevin0161003
Member
179
09-07-2016, 08:12 PM
#11
Analyzing from a single dump file may not give accurate results since patterns are better spotted across several files. RAM seems like the most likely culprit based on this observation. I favor testing RAM one stick at a time rather than using memory testers, as they often miss faulty RAM.
K
Kevin0161003
09-07-2016, 08:12 PM #11

Analyzing from a single dump file may not give accurate results since patterns are better spotted across several files. RAM seems like the most likely culprit based on this observation. I favor testing RAM one stick at a time rather than using memory testers, as they often miss faulty RAM.

S
SarityJr
Member
175
09-07-2016, 10:43 PM
#12
MemTest86 completed after four hours with a pass. I adjusted the permissions, thinking it might cause an error, but it still triggered another BSOD. Instead, I found a different issue: "UNEXPECTED_KERNEL_MODE_TRAP" along with a Minidump.zip file.
S
SarityJr
09-07-2016, 10:43 PM #12

MemTest86 completed after four hours with a pass. I adjusted the permissions, thinking it might cause an error, but it still triggered another BSOD. Instead, I found a different issue: "UNEXPECTED_KERNEL_MODE_TRAP" along with a Minidump.zip file.

H
hawk5strike
Member
55
09-07-2016, 11:06 PM
#13
I'm using LinpackXtreme-1.1.5. First run showed BSOF = IRQL NOT LESS OR EQUAL, then the BIOS reset to default and LinpackXtreme passed without a blue screen. Finally, XMP 1 was restored and the AI OC mode worked in the BIOS, eliminating the blue screen. It seems the OC might not have been configured correctly at first.
H
hawk5strike
09-07-2016, 11:06 PM #13

I'm using LinpackXtreme-1.1.5. First run showed BSOF = IRQL NOT LESS OR EQUAL, then the BIOS reset to default and LinpackXtreme passed without a blue screen. Finally, XMP 1 was restored and the AI OC mode worked in the BIOS, eliminating the blue screen. It seems the OC might not have been configured correctly at first.

H
HAR365
Member
162
09-28-2016, 10:39 AM
#14
It seems the update likely resolved the issue, and the current version doesn't significantly affect my perspective.
H
HAR365
09-28-2016, 10:39 AM #14

It seems the update likely resolved the issue, and the current version doesn't significantly affect my perspective.

T
Tico_32
Senior Member
680
09-29-2016, 03:32 PM
#15
1.2v is typical for DDR4 RAM, though it might not be sufficient. After that point, the system switched to XMP 1 but stopped reaching 5.1ghz. Using the AI OC feature in the BIOS, I’ll leave it as is; if a BSOD occurs again under those conditions, we’ll need to reassess.
T
Tico_32
09-29-2016, 03:32 PM #15

1.2v is typical for DDR4 RAM, though it might not be sufficient. After that point, the system switched to XMP 1 but stopped reaching 5.1ghz. Using the AI OC feature in the BIOS, I’ll leave it as is; if a BSOD occurs again under those conditions, we’ll need to reassess.

P
pandaman06
Member
61
10-03-2016, 03:14 PM
#16
It seems you're referring to the dump files showing a RAM-like appearance. Overclocking might be responsible. I may have worded it awkwardly, but the core idea is that the updated dump didn<|pad|> page my earlier reasoning about the crash. Other factors can also mimic RAM behavior.
P
pandaman06
10-03-2016, 03:14 PM #16

It seems you're referring to the dump files showing a RAM-like appearance. Overclocking might be responsible. I may have worded it awkwardly, but the core idea is that the updated dump didn<|pad|> page my earlier reasoning about the crash. Other factors can also mimic RAM behavior.

Pages (2): Previous 1 2