Recent BlueScreens at random times - Windows 7 x64

Sorry about being late for an update. It's a needed bump (the issue is not solved). I ran a Memtest86+ 5.01 scan and not even 30 minutes into it and there were over 200 errors.
 

Attachments

  • 2014-07-13 00.19.18.jpg
    2014-07-13 00.19.18.jpg
    340.7 KB · Views: 4
Your RAM (or perhaps a motherboard slot) is definitely faulty - the next step would be to arrange a RMA with the company to get them replaced. First though, try testing each RAM stick one at a time in each motherboard to determine which stick(s) are faulty and/or if one of the motherboard slots is also faulty. Hopefully you can then test the system with the known good sticks in good slots to ensure its stable before getting the faulty stick RMA'd.

Stephen
 
It's strange though. I never messed with any RAM slots. And I had no frequent Blue Screens until early this year. I barely had any last year.
 
Your motherboard slots are likely perfectly fine, Stephen was just discussing the possibilities regarding Memtest errors. It's probably simply just faulty RAM which is easily replaced if you contact the manufacturer.

Regards,

Patrick
 
Old restore points AFAIK get deleted over time.
I very much doubt your page file is corrupt, I suspect it was modified when memory was within the page file was accessed.
Are you still getting BSODs?
If so upload the dump files.
 
Code: 
BugCheck [COLOR="#FF0000"]7A[/COLOR], {fffff6fc40058138, [COLOR="#800080"]ffffffffc000009d[/COLOR], 105fcbe0, fffff8800b027000}

This bugcheck indicates important kernel data couldn't be paged into memory which was the cause of the bugcheck.

Code: 
fffff880`0331d848 fffff800`03cfc752 : 00000000`0000007a fffff6fc`40058138 ffffffff`c000009d 00000000`105fcbe0 : nt!KeBugCheckEx
fffff880`0331d850 fffff800`03cb091f : fffffa80`0a044e90 fffff880`0331d9c0 fffff800`03ec4540 fffffa80`0a044e90 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`0331d930 fffff800`03c971b9 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff fffff800`03ca8843 : [COLOR="#800080"]nt!MiIssueHardFault+0x28b[/COLOR]
fffff880`0331da00 fffff800`03cbd6e0 : 00000000`00000001 fffff880`0b027000 fffffa80`059d3b00 fffff6fc`40058110 : [COLOR="#800080"]nt!MmAccessFault+0x1399[/COLOR]
fffff880`0331db60 fffff800`03cbd8d0 : fffffa80`059428e0 00000000`00000001 fffffa80`00000000 fffff800`03cba70b : [COLOR="#008000"]nt!MiInPageSingleKernelStack+0x134[/COLOR]
fffff880`0331dc70 fffff800`03cbd85f : 00000000`00000000 00000000`00000001 fffffa80`051da740 00000000`00000080 : [COLOR="#008000"]nt!MmInPageKernelStack+0x40[/COLOR]
fffff880`0331dcd0 fffff800`03cbd5a4 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`051da700 : [COLOR="#008000"]nt!KiInSwapKernelStacks+0x1f[/COLOR]
fffff880`0331dd00 fffff800`03f2573a : fffff8a0`0863c000 fffff8a0`0863c009 00000000`00000000 00000000`00001000 : [COLOR="#008000"]nt!KeSwapProcessOrStack+0x84[/COLOR]
fffff880`0331dd40 fffff800`03c7a8e6 : fffff880`02f64180 fffffa80`05308040 fffff880`02f6efc0 00000000`00001000 : nt!PspSystemThreadStartup+0x5a
fffff880`0331dd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

What's happening here?
Well it looks like important Kernel data was on the paging file but it couldn't be paged in for some reason, we can see the hard fault which is where the requested memory needs to be paged in from disk but it can't...
But why?

Code: 
2: kd> [COLOR="#008000"]!error ffffffffc000009d[/COLOR]
[COLOR="#FF0000"]Error code: (NTSTATUS) 0xc000009d (3221225629) - STATUS_DEVICE_NOT_CONNECTED[/COLOR]

Well it looks like the drive suddenly disappeared, it just couldn't find the disk at all.
This is usually caused by a failing disk.

I suggest running Seatools, DOS would be a better idea.

Download it here:

SeaTools for DOS | Seagate

Burn the ISO image onto disk or convert it to be an executable for USB, ISO to USB is a good idea.

Boot into Seatools then run short and long generic tests.
 
Not yet, Patrick. I don't know which RAM stick(s) are/is affected. There are 3 in there right now each approximately 2 GB. Earlier today when I wasn't at home, I got a weird BSOD. Here's a snippet from WinDbg:
Code: 
BugCheck 109, {a3a039d89fd81893, 0, 605bdb2df2652f05, 101}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89fd81893, Reserved
Arg2: 0000000000000000, Reserved
Arg3: 605bdb2df2652f05, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

Now, I did notice some unused drivers in the driver list. One is related to the AMD video card drivers that are no longer being used. Could that be causing issues also? I am planning on replacing every single RAM slot with new sticks anyways (just to be on the safe side).

Also, I see that 101 = 5? Type 2 process list corruption or am I reading that wrong? Also, Patrick or Jared, is there a way to tell which RAM stick it is based on the Memtest86+ results?
 
If Memtest provided errors, your RAM is bad. Your #1 next step should be to remove all sticks and test one at a time until you find the bad stick. There's no point in us troubleshooting forward anymore until that's taken care of.

Regards,

Patrick
 
My friend, I will reiterate yet again, and I will explain as best I can so there are no misunderstandings.

Your RAM received errors in Memtest. This implies that your RAM (possibly at least one stick, but it could be more than one) is faulty. Plain and simple, no further explaining to be done. Memtest is a completely isolated environment from the Operating System. No software complications whatsoever are possible, and the two algorithms Memtest uses ensure that only the RAM is tested. No other hardware is tested during Memtest, therefore errors in Memtest cannot be brought upon by any other piece of hardware.

When I asked you if you had replaced the problematic RAM, you replied:

Not yet, Patrick. I don't know which RAM stick(s) are/is affected. There are 3 in there right now each approximately 2 GB.
Click to expand...

Your best course of action is to run one stick at a time and see which one causes errors. If it's only one out of the three, then that's the bad stick. After you've found that bad stick, toss it. You can then either run with two sticks temporarily until you can purchase a new kit of RAM, or you can purchase new RAM right away. If you for example however get no errors when running one stick at a time, this concludes you have a timings/voltage setting set improperly when running all of the sticks together. This can either be manually solved through editing a few DRAM settings in the BIOS, or it's due to the fact that you may be mixing and matching RAM of different kits, etc, therefore it isn't compatible and won't run properly together.

Regards,

Patrick
 
Back
Top