2 errors in Memtest, constant BSOD's - please advise

rtk84

Commendable
May 27, 2016
4
0
1,520
Hello.

I have encountered serious (for me) problem and I'd be greatful for some advise from experienced users & experts.

I have just run my new gaming laptop from OriginPC (EON17-SLX) with 32GB Kingston HyperX Impact DDR4 2400MHz (4 X 8GB). It was supposedly tested through and through.
Unfortunatelly, since the very first minutes (during which I have updated Win 8.1, installed Steam and Bitdefender) I had it turned on, it's giving me BSOD's ( INTERNAL_POWER_ERROR, CACHE_MANAGER_ERROR, KERNEL_SECURITY_CHECK_FAILURE and IRQL_NOT_LESS_OR_EQUAL). Some after 10 minutes, some in 2-3 seconds from loading Win.

I performed all Windows tests & diagnostics - passed.
I performed Memtest, it took 11 hours and gave two errors:
Test 6 Addr: 3CDB04CA8 Expected: 00000020 Actual: 00000220 CPU: 0
Test 6 Addr: 3CFB04C88 Expected: 00000020 Actual: 00000220 CPU: 0

Could you please share your opinion with me? What should I do? Is RAM damaged and needs to be replaced? Or maybe just switching sticks / reinstalling some updates in Win could help?

Best,
Radek
 
Solution
Thank you for all answers.

It turned out that problem was multilayered.

BSODs came from some RAM sticks faulty placement. I have switched the sticks and the OS would not get up at all. Switched it back, made sure they were not loose - no more BSODs.

At the same time there was some drivers conflict giving often freezes on different ocasions. I tried to detect it with LatencyMon, but with no good results. Finally I have reinstalled Windows and then checked all devices one by one, creating points of restore. It turned out Origin has incorrect drivers for WiFi (for another device described incorrectly). After installing correct driver everything runs smootly and LatencyMon also shows no errors.
as it a new laptop and was shipped take battery and power off the unit make sure all the ram is locked in. if the memory error or bsod show up again take out 1/2 the ram make sure it runs fine. if it does swap one ram stick in. if it errors out swap the ram stick again if the laptop runs fine it a bad spot on one of the ram sticks.
 

rtk84

Commendable
May 27, 2016
4
0
1,520
Do you mean something like that:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>3</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2016-05-26T17:53:26.394339600Z" />
<EventRecordID>9888</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>rtk</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">131087587794175235</Data>
<Data Name="BootAppStatus">0</Data>
</EventData>
</Event>
?
 
if you get single bit errors while running memtest then you should update your BIOS to get the best default ram timings
or confirm your ram timings (or slow down your RAM) You might be able to Isolate and remove the defective RAM.

There is really not a point in looking at the memory dumps when you are having these bit corruptions.

you need to get a memtest to run without errors even if you have to slow down the ram timings or replace the RAM.
I think about 8% of ram fails to run at SPEC speeds when actually tested.
 

rtk84

Commendable
May 27, 2016
4
0
1,520
Thank you for all answers.

It turned out that problem was multilayered.

BSODs came from some RAM sticks faulty placement. I have switched the sticks and the OS would not get up at all. Switched it back, made sure they were not loose - no more BSODs.

At the same time there was some drivers conflict giving often freezes on different ocasions. I tried to detect it with LatencyMon, but with no good results. Finally I have reinstalled Windows and then checked all devices one by one, creating points of restore. It turned out Origin has incorrect drivers for WiFi (for another device described incorrectly). After installing correct driver everything runs smootly and LatencyMon also shows no errors.
 
Solution