Computer crashed randomly, while playing hearts, 0x0000003d

[woodardhsd]

My father-in-laws PC crashed a while back. He was playing hearts at the time, and it went straight to the blue screen. Sorry, I don't have a ton of details into the crash, they live in Kentucky and they had to bring the PC to our house in NC to troubleshoot.

 

[woodardhsd]

For some reason, on this PC, I can't create a zip file from the SF utility I ran. I'll transfer the file to my other computer and post it in the morning. The computer crashed again tonight while I was getting ready to burn a cd to run memtest86, so I've attached another dm log file below. I couldn't snap a picture of the blue screen quick enough, but it said something about memory at the top.

The error details (after windows rebooted) said this:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000000411
BCP2: FFFFF6FC40062AF8
BCP3: 000000009C374962
BCP4: FFFFF8A00346D011
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\061014-15085-01.dmp
C:\Users\Wayne\AppData\Local\Temp\WER-47283-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[koolkat77]

Welcome to the forum woodardhsd,

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {411, fffff6fc40062af8, 9c374962, fffff8a00346d011}

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

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000411, The subtype of the bugcheck.
Arg2: fffff6fc40062af8
Arg3: 000000009c374962
Arg4: fffff8a00346d011

Debugging Details:
------------------

Suggest that you start with testing RAM.
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

 

[woodardhsd]

I had already started a memory test with memtest86+ last night, with all 4 memory sticks in. On the first pass, it found 568 errors before I stopped it to retrieve the results of the SF diagnostic test I ran earlier(I have attached it below). I started the test again (again with all 4 sticks) and let it run overnight. This morning I found no errors, but I'm not sure how many passes it did.

After reading your post, I did as you asked and removed all but one stick and the test is currently running. I will report back the results.

 

[koolkat77]

Alright, see you then

 

[woodardhsd]

The first stick tested OK after 8 passes.



Just a quick question about the memtest86+ procedure. The first stick (in slot #1) tested OK, so I skipped to test #3 above. I think I may have goofed, because I put stick #2 in slot #1. I guess I should have put it in slot #2.

 

[essenbe]

I have a couple of questions. First, are you using memtest86+ from Memtest86+ - Advanced Memory Diagnostic Tool? There is another test named the same without the + at the end. Why they try to confuse people with so similar names, I have no idea, but the one I linked to above is the best and pretty much the standard. Please be sure and use it. As far as the tests, I always recommend to either mark each stick or lay them out so you know which is which. Test each stick in each dim slot for 8 complete passes or until you get an error. If you get an error, stop the test. Also write down which stick was tested in which slot and whether it passed or failed. The reason for all of this is to test each stick to find out if the ram is bad or the dim slot on the board is bad, which does happen more often than people think.

As far as your tests, you didn't goof. You can do them in any order you want just as long as in the end you have tested each stick in each slot. As time consuming as it is, it is the only way to determine if it is the ram or the board. But, please use the test I linked to above. If you have any questions, feel free to ask. Also, check the manufacturer's web site. Most of the most reputable and best manufacturers offer a lifetime warranty on their ram. If you RMA the ram, RMA all sticks and get a complete kit in return. A kit is tested to all work together where individual sticks are not. Some ram and boards can be very picky, a kit can avoid many of those problems.

 

[woodardhsd]

I followed the link that koolkat77 posted in post #3. It appears to be the same one you posted.

I should have mentioned this earlier, but the computer is a HP Pavilion A6242n (HP Pavilion a6242n Desktop PC Product Specifications | HP® Support). It originaly came with Vista, but I installed Win7 before I gave it to my in-laws. It has the original memory in it. There are 2 1GB DIMMs and 2 512MB DIMMs. The 1GB's are some brand I've never heard of (cant remember) and the 512's are samsung.

 

[essenbe]

most likely you will have to buy new ram if the computer is not under warranty. Also running ram with different density can cause issues. Your Motherboard, according to the link you provided, says it can hold 8 GB of ram, which I assume is 2 GB sticks in each slot. If you replace it I would use the specs from the link for ram and buy at least 2X2GB kit. I think you will notice a big difference in performance, especially if you installed the 64 bit OS. If you installed the X86 version (32 bit) the most that it can address is 4GB and the most that you will see as usable is 3.5-3.7GB. That is a limitation of a 32 bit system.

 

[woodardhsd]

The PC is definitely not under warranty, I think I bought that back around 2007. If it is indeed the memory, that's exactly what I plan to do. The annoying thing is there are no local places to buy memory before tomorrow, which is when m father-in-law is leaving. So I'll have to send him back home to Kentucky with a broken PC. Maybe I can show him to install the new memory himself before he leaves.

 

[Boozad]

Maybe I can show him to install the new memory himself before he leaves.

I'd go with that, RAM is probably the easiest hardware upgrade you can do in a PC, I even got my dad to do it once. Just make double sure you tell him to turn the rig off though first and disconnect the power.