Seems to be random 'STOP' error; after BSOD. comeout scr saver-or rand

jasonc · 28 Feb 2014

I have noticed a lot of recent crashes. Four times in the last week. Twice in as many days.

PC go in screen mode after a minute and I have to type password to get back in, no custom screen saver used, pc just goes to login screen after a minute of no use.

Sometimes it crashes while i have been using the pc continuously.

I have used the .bat method to get the zip file (attached)

I have checked and seems my pc is up-to-date going by windows update.

I have not had the computer that long a few years if that.

Can anyone suggest what could be causing this to happen so often. Once in a blue moon seems okish to me, within reason. But 4 times in the last week is a bit suspect.

Not sure what else I can say right now, but if there is anything else that I need to provide or let you know, please ask.

Thanks

Arc · 01 Mar 2014

Hi jasonc.

The zip you uploaded does not contain any crash dump.

Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any dis cleanup program before you upload another zip.

jasonc · 29 Apr 2014

Hello again, well it happened again and attached is the zip. Hopefully I have does this correctly.

I had just opened firefox and was browsing the net and then the BSOD showed itself. Not happy about this and can not understand why this is happening so much lately.

Hopefully someone can figure out what is going on with my pc.

Thank you.

Arc · 29 Apr 2014

Hi jasonc.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
_________________________________

Code:

BugCheck 1A, {41790, fffffa80008fab70, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

Followup: MachineOwner
---------

* A page table page has been corrupted.

jasonc · 29 Apr 2014

ok will do, thank you. I'll report back tomorrow as i have 8gig ram ! not sure how long that will take.

Arc · 29 Apr 2014

No problem, take your time. :)

jasonc · 29 Apr 2014

ok that took almost no time at all. But nearly had a heart attack when the pc started to do things it never done before!! The pc started to beep and found I accidental pulled out the power to the HD. Plugged it back in turned pc back on and then the screen started to go all funny. OMG, that the heck is going on.... Turns out the I had not pushed in hard enough one of the cards.

Ok after doing the first scan with both I get error within minutes. Turned off pc and removed 'card 1' ran scan again and got error, turned off pc and removed 'card 2' and put 'card 1' back in its original slot. Ran and got no errors on first pass. turned off and put card 2 in a different slot and got errors again, so seems that card 2 is at fault.

Ok it does say to run at least 8 times. But as the first pass took no time at all I just took it that it should in theory be ok with just one pass. So I shall leave card 2 out and get another one and mark as card 3 ! then use that for a bit and see if I get any problems with card 1 or the new card 3 ! I hope not.

Thank you anyway for helping me figure out that the problem is likely to be with just card 2. Both the cards were new and got at the same time. And were not second hand. Ok there may be a problem later on with card 1, but we shall see.

Thanks again..

Arc · 30 Apr 2014

Errors/red lines means one or more RAM is faulty. A single error is enough to rule out the RAM as faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+. Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

No code has to be inserted here.
It is a RAM, a bad RAM.

But if you have got a result like that:

No code has to be inserted here.
It is a motherboard issue. The particular slot is bad.

jasonc · 30 Apr 2014

Yes I worked out how to do that step without reading it. I now only have one slot with the good card in it, and the pc is not as quick as it was before! I shall be buying card3 soon as I can and hope no more problems. Thanks to the help I got here.

Arc · 30 Apr 2014

jasonc said:

Yes I worked out how to do that step without reading it.

jasonc said:

I now only have one slot with the good card in it, and the pc is not as quick as it was before! I shall be buying card3 soon as I can and hope no more problems. Thanks to the help I got here.

With the less quantity of RAM, the computer is supposed to run a bit slowly. But you have a good job there!

When getting the new RAM, make it sure that the specs (timing, FSB etc) matches with the existing one. :)