BSOD, error 0x1000000a , 0x1000007f ntoskrnl.exe & Rt86win7.sys

Pc Specs - Amd Athlon II X2 240 (Regor). Asrock M3A785GXH/128M. Kingston KVR1333D3N9/2G 2GB DDR3 Ram. Cooler Master eXtreme Power Plus 390W. Windows 7 Professional.

The PC was assembled around 2 1/2 years back. Except for the PSU that was bought around 4 years back. Unfortunately I can't remember when exactly. I'll find out.

The issue at present, is random but frequent BSOD crashes. Sometimes while using the computer, mostly surfing and videos. Other times, when idle, like downloading.

I have replaced two hard drives since the BSOD crashes first started around a year back. It first surfaced around a year back. Now it's happening again. There was random restarting too. The pc would also not boot several times.

Memtest86 gave a 'unexpected interrupt' error, in garbled words, when I ran it overnight.

Couple of days back, a technician was called in. According to his diagnosis, the CMOS settings had become corrupt due to some changes I had made in the BIOS. I had overclocked the mGPU settings briefly. But reverted to default settings after the problems. I didn't touch the memory timings. He also added that the CPU was overloaded by this and was overheating. This morning it BSODed again.

I haven't run any cpu stress tests yet. I can't think of any other details as I am short on time(the pc might crash).

Hey Magus, thanks for taking the time to reply so quickly. It must be inconvenient due the difference in time zones. I'll install the new realtek lan drivers. I'll also run memtest again. I'll wait till you can debug again.

I'll get right to it. There's only one stick of ram on the machine btw.

I could borrow a friend's. Just curious, is it because the problem might be with the memory controller in the motherboard?

I ran memtest again, this time it passed. Could it be the corrupt CMOS settings that was making memtest give that weird erorr? Aww heck, now I can't remember if I first ran memtest, before or after the technician's diagnosis of the CMOS being corrupt. Matter of fact, I didn't even ask him how he fixed it! Isn't a CMOS corruption when you get a 'Checksum error' at bootup? Gotta lay off the mary jane.

Also, I had a another BSOD problem with a WRkrn.sys file after I uninstalled AVG. Turned out it was a Webroot AV driver. I had to do a 'last known good configuration'. All in all, I haven't had a BSOD since yesterday.

Right now, I'm thinking, I could sit on it and wait for it to happen again. Or I could run some stress tests? OCCT? Should I risk it though, considering my PSU is old and only 390W? Thanks for all your suggestions and time Magus.

I forgot ask, does memtest restart the computer after the tests are done?