Computer randomly blue screens

[padimus]

I apologize in advance for what is probably a bad thread title. Any who down to business. I've had this computer for just over a year and in the first couple months my cooling system leaked ruining my video card. I returned it to manufacturer and it was replaced and everything was fine until December when my Power supply died (RMA'd it and computer worked fine until Late January.) Now I'm getting BSODs with loads of different errors. I have reformatted twice, the first time just in hopes that it would be a software issue. The 2nd time was because Windows would not load it would take me to start up repair and would say nothing was found. A friend who was trying to help me said said it would probably a Mobo issue or a HDD issue and I would like to know for sure before I go and spend money on something was wasn't broken. Thanks in advance for any and all help you all provide

System is a year and 2 months old
Running Windows 7 Home Premium 64bit OEM
Reformatted Twice
Original OS is Windows 7 Home Premium 64bit
Will provide any additional information upon request

 

[padimus]

Oh, and sorry I forgot to put that these next couple weeks will probably be busy for me so I may be slow to respond sorry

 

[writhziden]

Security Software (this is just to check that it is working and on the system; nothing needs to be done with this information at this time):

msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	832	8	200	1380	4/4/2012 12:06 PM	3.0.8402.0	12.48 KB (12,784 bytes)	4/27/2011 5:21 PM
msseces.exe	c:\program files\microsoft security client\msseces.exe	2508	8	200	1380	4/4/2012 12:07 PM	2.1.1116.0	1.37 MB (1,436,736 bytes)	6/15/2011 2:35 PM

Install all Windows updates. You do not have Service Pack 1 installed yet.

Loading Dump File [D:\Kingston\BSODDmpFiles\padimus\Windows_NT6_BSOD_jcgriff2\032712-21621-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0281a000 PsLoadedModuleList = 0xfffff800`02a57e50
Debug session time: Tue Mar 27 18:39:27.654 2012 (UTC - 6:00)
System Uptime: 0 days 0:07:48.214
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 137, 0, 0}

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000000137
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880031c46b0 -- (.trap 0xfffff880031c46b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80086410c8 rbx=0000000000000000 rcx=00000000000000ff
rdx=fffff8a005eba8f0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002990797 rsp=fffff880031c4840 rbp=fffffa8006ef5000
 r8=fffffa8009060036  r9=fffffa8006cfb048 r10=fffffa8009363010
r11=fffffa8009355a00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiEmptyPageAccessLog+0xe7:
fffff800`02990797 8b4138          mov     eax,dword ptr [rcx+38h] ds:0001:00000000`00000137=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002836b6e to fffff8000288bf00

STACK_TEXT:  
fffff880`031c4548 fffff800`02836b6e : 00000000`0000001a 00000000`00041287 00000000`00000137 00000000`00000000 : nt!KeBugCheckEx
fffff880`031c4550 fffff800`02889fee : 00000000`00000000 00000000`00002436 00000000`00001000 fffff800`0289e87d : nt! ?? ::FNODOBFM::`string'+0x42c75
fffff880`031c46b0 fffff800`02990797 : bc200001`ed9a9404 fffffa80`09363050 00000000`00000000 fffff800`02899d64 : nt!KiPageFault+0x16e
fffff880`031c4840 fffff800`029909f0 : fffffa80`09065910 00000003`00000000 00000000`000000ff fffffa80`086410c8 : nt!MiEmptyPageAccessLog+0xe7
fffff880`031c48b0 fffff800`02990bf6 : fffffa80`06cfb000 00000000`00000c04 fffff680`00039f90 00000000`00000002 : nt!MiAllocateAccessLog+0x80
fffff880`031c48e0 fffff800`028f41d8 : 00000003`00000000 c0400001`cad4e867 00000000`00000000 00000000`00000c04 : nt!MiLogPageAccess+0x46
fffff880`031c4930 fffff800`0290ca0e : fffffa80`09065ca8 fffff880`00000001 00000000`00000001 fffff880`031c4bb0 : nt! ?? ::FNODOBFM::`string'+0x21846
fffff880`031c4ae0 fffff800`028a06e2 : 00000000`000001d5 00000000`00000000 fffffa80`00000000 00000000`00000006 : nt! ?? ::FNODOBFM::`string'+0x49926
fffff880`031c4b80 fffff800`028a096f : 00000000`00000008 fffff880`031c4c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`031c4bd0 fffff800`02b2f166 : fffffa80`06bab680 00000000`00000080 fffffa80`06b8c040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`031c4d40 fffff800`0286a486 : fffff800`02a04e80 fffffa80`06bab680 fffff800`02a12c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031c4d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+42c75
fffff800`02836b6e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42c75

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42c75

BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42c75

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

One of your .dmp files was corrupt. This usually suggests data corruption and/or memory problems. The good crash report suggests the latter.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run the Western Digital Data Lifeguard Diagnostic tests for the hard disk to make sure the disk is not faulty.
  
  
• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[padimus]

Thanks! When I get home on Monday I will start on that!

 

[writhziden]

No problem. Do things at whatever pace you need to. I'll be keeping my scanners peeled for your posts back.

 

[padimus]

I can't get on my computer long enough to do any thing. It crashes almost as soon as windows boots up. I ran Western Digital Lifeguard diagnostic earlier today (was being a little more stable) and when I came home it was had a Blue Screen. I've been trying to post the log from the Disk Check that I have but my computer BSODs before I can post it up here :/. Also I've made sure to install all available Windows Updates.

EDIT: I forgot to mention that it's not always a BSOD, sometimes my screen just freaks out and locks up.

 

[padimus]

Ok, I got it working for the time being in safe mode! The event log for the ChkDsk I ran is as follows:


Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
152832 file records processed. File verification completed.
438 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
199770 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
152832 file SDs/SIDs processed. Cleaning up 31 unused index entries from index $SII of file 0x9.
Cleaning up 31 unused index entries from index $SDH of file 0x9.
Cleaning up 31 unused security descriptors.
Security descriptor verification completed.
23470 data files processed. CHKDSK is verifying Usn Journal...
35723800 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
152816 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
227385927 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

976657407 KB total disk space.
66743992 KB in 106628 files.
85116 KB in 23471 indexes.
0 KB in bad sectors.
284591 KB in use by the system.
65536 KB occupied by the log file.
909543708 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
227385927 allocation units available on disk.

Internal Info:
00 55 02 00 3f fc 01 00 ee f8 03 00 00 00 00 00 .U..?...........
cb 00 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

 

[writhziden]

Hard disk checked out. I would suggest getting the Memtest86+ step done as soon as you are able.

 

[padimus]

alrighty i'll get right on that! I just ran the Western Digital test again to make sure that it wasn't that and it said it passed. Off to Memtest86!

 

[padimus]

Okay, I'm doing what is hopefully the last Memtest86+ test that I have to run, (ram stick #4 in slot #4.) Ram stick 3 was good but according to Memtest86+ Slot 3 had gone bad!

 

[writhziden]

Which stick did you run in slot 3 that showed up with errors? Or have you used multiple sticks and received errors in slot 3?

 

[padimus]

Thank you so much! I guess it was just the bad RAM slot, been a few days with no BSODs

 

[padimus]

Which stick did you run in slot 3 that showed up with errors? Or have you used multiple sticks and received errors in slot 3?

I ran stick 3 in slot 3 when it gave me a error I ran stick 3 in slot 1 and it worked, I then ran stick 1 and slot 3 just to make sure it wasn't a fluke. and it gave me a error again. Right now I'm running with Sticks 1,2 and, 4 in slots 1,2 and, 4. I just got another Blue Screen it was a Bad Pool Header :/

 

[writhziden]

Let's see if we can track down why the RAM is causing problems.

• Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

 

[padimus]

OK, I thought it was solved and I could wash my hands of BSODs but my computer disagrees. I've gotten 4 Blue screens last night (Irql less or not equal, Bad Pool Header, and 2 without error messages.) : / thanks again for everything you've done to help me out so far

 

[padimus]

Let's see if we can track down why the RAM is causing problems.

• Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

Oh wow that wasn't showing up on my laptop until just now haha ok i'll get on that

 

[padimus]

Well it seems that I was reading the RAM slots backwards. Ram slot #2 is empty and, according to memtest86+, was the one giving me errors.

 

[writhziden]

Timings look good, and the 666.7 MHz is fine with AMD boards. Try removing the RAM from the slot that is in dual channel mode with the bad slot. See if it runs stable with the remaining 4 GB.

 

[padimus]

Okay I got ram in slots A2 and B2 (according to my mobo user guide that's channel 2) with 4gb total

 

[padimus]

I just got a blue screen, there was no error name though just technical information i'll post that on the bottom if it helps any. I'm going to try running memtest tonight before I go to bed.

STOP: 0X000007F (0X0000000000000008, 0X0000000090050021, 0X00000000000006F8, 0XFFFFF800021CBC61)