Odd issues in Windows 10, even losing system files.

To be more specific, the I/O error occurs because of a corrupt memory address:

Rich (BB code): 
1: kd> .cxr 0xffffd38d16f1d5c0
rax=0000000000000000 rbx=ffffd38d16f1e038 rcx=0000000000000007
rdx=0000000004ea6e10 rsi=ffff96832adbb000 rdi=ffff96832adbb000
rip=fffff805068ce2a2 rsp=ffffd38d16f1dfc8 rbp=ffffd38d16f1e089
 r8=000000000000001c  r9=ffffb20eefc80080 r10=0000024da88c7e10
r11=0000000000000e10 r12=ffff968333685da0 r13=ffffd38d16f1e230
r14=00000000c0000034 r15=0000024da3eb13b4
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!HvpGetCellPaged+0xa2:
fffff805`068ce2a2 418b02          mov     eax,dword ptr [r10] ds:002b:0000024d`a88c7e10=????????
 
x BlueRobot said:
It is odd that the issue only appears to happen after a few months,
Click to expand...
Yes exactly my thought. Never seen some odd stuff like that before, at least not with some memory or hdd failure which came up in some test.

Indeed not a lot more we can do unfortunately. Thank you very much so far, for all help and insight!

To be more specific, the I/O error occurs because of a corrupt memory address:
Click to expand...
I'm still prepared to do another memory test, just to be sure. However this can take a while as I have to be near the system to be able to do that.

Do you have an advise as to which program I can use best to test and evt. with which settings?
 
We usually always recommend MemTest86 for at least 8 passes, which require two runs of four passes which the maximum the free version offers.
 
Ok so that would be the same as I used before, just 4 passes more. Then I will give that a try as soon as I get my hands on that PC again.
It can take months.

Or when the PC starts to give issues again before that time, I can start with that test and then report back here in this thread. Seems the best idea to me for the moment.
Thank you for everything so far.
 
Apologies for stepping on toes, but I see you have four 8GB RAM cards installed. Perhaps you could try removing one at a time and running for a while on the other three? Swap them around after a while to see whether one stick is flaky?
 
ubuysa said:
Apologies for stepping on toes
Click to expand...
Trying to be helpfull is not stepping on toes as far as I'm concerned.
But you might have missed that it takes many months before some issue takes place.
If one of the sticks would be wrong, it should show in tests. On removing one by one, it could take a couple of years to find out which one it was. :) Unless we got lucky.

When thinking of how little this problem occurs (so about twice a year), it means working with less memory every time for a long time. Since there is nothing much on the system, in that case I'd rather wait until the problem occurs and then do some thorough tests.

However, swapping them around for some time is not a bad idea, so I can try that. However, also in that case I must be near the system myself to do that. But if I am, I will certainly change them.
Thanks.
 
Back
Top