Blue screen for awhile now

#1
My computer has been blue screening for awhile now (at least a year). I thought i had fixed it before i deployed, got back home and was still doing it. I dont know how active this forum is but please help. I hope that i have everything attached. If you need anything else please let me know. Thank you.
 


Attachments

Josephur

Windows Forum Admin
Staff member
Premium Supporter
#2
Your latest dump file indicates kernel structures in memory are getting corrupted. I would run Windows Memory Diagnostics or Memtest86. Narrow down which stick of memory is faulty and replace it.

Code:
5: 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: a3a039d898ada6be, Reserved
Arg2: b3b7465eeb2a7624, Reserved
Arg3: fffff800034c3020, Failure type dependent information
Arg4: 0000000000000001, 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

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


FAULTING_IP:
nt!ExRaiseHardError+0
fffff800`034c3020 488bc4          mov     rax,rsp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x109

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT: 
fffff880`031775d8 00000000`00000000 : 00000000`00000109 a3a039d8`98ada6be b3b7465e`eb2a7624 fffff800`034c3020 : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff800034c3081 - nt!ExRaiseHardError+61
    [ 4c:6c ]
1 error : !nt (fffff800034c3081)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_memory_corruption_one_bit

FAILURE_ID_HASH:  {2dbb898e-c425-bad1-90fe-71c78117521f}

Followup: memory_corruption
---------
 


#3
Ok, awesome, thank you for the guidance. I will let you know how it goes.
 


#4
So I ran memtest 3 times and got no errors. I thought there was a way to run it multiple times but maybe thats the newer version. Either way I will try to change out the RAM cards and see where that gets me. Next step after that will be building a new rig lol.
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#5
Sometimes Memtest86 will miss errors and a more effective way can be simply running on one stick at a time. If the stick blue screens it's bad, if it doesn't it's good.

If your drivers and bios are generally up to date then try the above but in any case post the next bsod you get and we'll take another look.
 


#6
So I got fed up with everything and formatted my hard drive the next day i blue screened twice, here are the logs. I have new RAM on the way, just waiting for it to get here.
 


Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#7
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff880070af428, 0, fffff880012ad0bc, 0}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
Hi,
Bugcheck 50 can be caused by a number of things:
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
Another common cause is the installation of a faulty system service.
Antivirus software can also trigger this error, as can a corrupted NTFS volume.

As all of your dump files have blamed memory corruption then the obvious choice has been to test the RAM. As I pointed out though Memtest86 can miss errors and sometimes it's easier to test the RAM by simply running the machine on one stick at a time. If a stick blue screens then consider that one bad, swap sticks and test again. Do this until you find the stick or sticks which bsod. If you find that no sticks bsod then swop RAM slots and test again just to make sure it isn't a RAM slot thats gone.

There is also a chance that the memory corruption could be caused by another factor particularly old or out of date Bios and corrupt NTFS volumes.

I did notice that NTFS was in the Call Stack (a kind of list of the last sub routines) and so it's worth testing your drive for errors:
http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/
Whichever way you use in the above guide make sure you check for and repair broken sectors.

BiosVersion = 1104
BiosReleaseDate = 01/28/2010
The latest Bios for your motherboard stands at 1408:
http://www.asus.com/Motherboards/P6T/HelpDesk_Download/

Code:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
This tells me your missing Windows 7 Service pack 1:
http://www.microsoft.com/en-gb/download/details.aspx?id=5842

Rtnic64.sys Fri May 30 16:12:23 2008: Realtek Ethernet NIC driver please update:
Rt64win7.sys Thu Feb 26 09:04:13 2009: Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC please update:
http://www.realtek.com.tw/downloads...d=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

Post any new dump files.
 


#8
So my new RAM cards came in had them running for about a week or two now and no blue screen. I built another computer and the one i had problems with is now my multimedia comp for my tv. Thank you guys for all your help.
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
#9
Much thanks for updating your thread. Hope all goes well with the new pc.. :)
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.