BSOD in everything I do

Okay I have replaced my RAM, as well as tried every RAM slot, replaced my GPU, changed the SATA cable for my HD, changed my monitor. I have still yet to cease any of these BSODs. For two days straight, when I first turn on my PC, it freezes and stops during the POST screen and have a couple of times, it'll go to the startup repair launcher and if I presss continue you windows, it'll reboot itself and/or blue screens. So I would have to open up my computer and usually reseating the RAM sticks fixes the problem, only to boot past the startup. Earlier today, it went into chkdsk and found alot of corrupted window files. Yesterday I did the same chkdsk and it found nothing. sfc /scannow three times and its all good. Tested my RAM for 7 passes yesterday, all good. Did a harddrive check, after the chkdsk, all good. Driver Verifier has been enabled for about 4 days now. Also my temps have been fine.

Sometimes I won't get a BSOD for a few days then one day I'll get struck by a couple to a point where went it restarts, it freezes during startup then it'll bring me to the startup repair screen.

Sometimes the blue screens are too quick for me to see what happened.

Recently the blue screens have been saying win32k.sys

I'm out of ideas. Thanks for all the help you have given me these past few months.

https://rapidshare.com/files/1956781055/MEMORY.DMP <--dmp file i had to upload due to its size.

Bump.

Update: I turned on my PC for the first time this morning then it loaded up fine but as soon as I hit the desktop, it BSOD but it didn't leave any dmp file in the minidump folder or left a big DMP file in the windows folder.

Multiple threads where we tried to help and were abandoned... Makes me question whether you really want help from us.

• https://www.sevenforums.com/crashes-d...ml#post1780510
• https://www.sevenforums.com/crashes-d...ml#post1838992
• https://www.sevenforums.com/crashes-d...ml#post1858704

All of these recommend that you test your RAM. It is possible you might have bad/conflicting RAM modules... Perhaps you should do as suggested by all three people in those threads and post back as asked?

Please do not start new threads for the same problem; it makes it very difficult to help and it gets very confusing trying to help over multiple threads.

Well I was told from the first thread I made before was to make a new thread if its been a while cause usually the ones subscribed to it had unsubscribed, which is why I made a new thread. I wouldn't be wasting my time making all of these threads if I didn't need help. I appreciate everyone that has helped me here. I've done everything that was asked of me to do and so far nothing has worked.

To answer your advice, I've checked my RAM last night and they were all passes. Also I did a Data Lifeguard Diagnostic Extended test which ended just now and came up with no errors.

Just say the word and I'll stop posting all of my computer problems.

You should respond in the thread first. See if anyone gets back to you. Not everyone unsubscribes from threads quickly. I am still subscribed to threads from months ago and occasionally get a message that someone wrote in one of those threads.

Follow the instructions given in https://www.sevenforums.com/crashes-d...ml#post1780510 and post back the CPU-Z screenshots and voltage info.

Enclosed are the CPU-Z pics.

http://speccy.piriform.com/results/d...IV70SlHxHKbMlU <-- link to my specs from speccy.

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\XplicitMind\Windows_NT6_BSOD_jcgriff2\040312-22854-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0301f000 PsLoadedModuleList = 0xfffff800`03263650
Debug session time: Tue Apr  3 17:35:20.945 2012 (UTC - 6:00)
System Uptime: 0 days 0:01:05.147
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff80003073dee, 3073121, fffff88003ddb0d0, b}

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

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

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff80003073dee, Virtual address for the attempted write.
Arg2: 0000000003073121, PTE contents.
Arg3: fffff88003ddb0d0, (reserved)
Arg4: 000000000000000b, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xBE

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88003ddb0d0 -- (.trap 0xfffff88003ddb0d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff80003073dea
rdx=00000000000007ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030a77c0 rsp=fffff88003ddb268 rbp=fffff88003ddb310
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
r11=fffffa8006994392 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!FsRtlResetBaseMcb:
fffff800`030a77c0 83610400        and     dword ptr [rcx+4],0 ds:fffff800`03073dee=45d23345
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003047e32 to fffff8000309bd40

STACK_TEXT:  
fffff880`03ddaf68 fffff800`03047e32 : 00000000`000000be fffff800`03073dee 00000000`03073121 fffff880`03ddb0d0 : nt!KeBugCheckEx
fffff880`03ddaf70 fffff800`03099e6e : 00000000`00000001 fffff800`03073dee 00000000`00000000 fffffa80`087f5d80 : nt! ?? ::FNODOBFM::`string'+0x4521e
fffff880`03ddb0d0 fffff800`030a77c0 : fffff880`0121d40d fffffa80`087f5d00 00000000`00000000 fffff8a0`040f5600 : nt!KiPageFault+0x16e
fffff880`03ddb268 fffff880`0121d40d : fffffa80`087f5d00 00000000`00000000 fffff8a0`040f5600 0000007f`ffffff00 : nt!FsRtlResetBaseMcb
fffff880`03ddb270 fffff880`01215fc6 : fffff880`03ddb610 fffff980`1524cc10 fffff8a0`040f5650 00000000`00000000 : Ntfs!NtfsNonCachedIo+0x24d
fffff880`03ddb440 fffff880`01217a68 : fffff880`03ddb610 fffff980`1524cc10 fffff880`03ddb701 fffffa80`08acc001 : Ntfs!NtfsCommonRead+0x7a6
fffff880`03ddb5e0 fffff800`03540c16 : fffff980`1524cc10 fffff980`1524cc10 fffffa80`08acc030 fffffa80`0a79c690 : Ntfs!NtfsFsdRead+0x1b8
fffff880`03ddb7f0 fffff880`0116fbcf : fffff980`1524cfb0 fffff880`03ddb8a0 fffffa80`0a7cf010 fffffa80`0a79c690 : nt!IovCallDriver+0x566
fffff880`03ddb850 fffff880`0116e6df : fffffa80`087f4de0 fffffa80`087f4de0 fffffa80`087f4d00 fffff980`1524cc10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`03ddb8e0 fffff800`03540c16 : fffff980`1524cc10 00000000`00000002 fffffa80`08e9e5d0 fffffa80`06bf1218 : fltmgr!FltpDispatch+0xcf
fffff880`03ddb940 fffff800`030c3125 : fffff980`1524cc30 fffffa80`0882cad0 fffffa80`09c8a601 fffffa80`08e926a0 : nt!IovCallDriver+0x566
fffff880`03ddb9a0 fffff800`030c2bf9 : 00000000`00000001 00000000`00000001 fffffa80`0882ca10 00000000`000008f0 : nt!IoPageRead+0x255
fffff880`03ddba30 fffff800`030a949a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff800`00000000 : nt!MiIssueHardFault+0x255
fffff880`03ddbac0 fffff800`03099e6e : 00000000`00000000 00000000`00b20ff8 00000000`00000a01 00000000`74a42828 : nt!MmAccessFault+0x146a
fffff880`03ddbc20 000007fe`fd6d11fd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`01d5e3f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd6d11fd


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4521e
fffff800`03047e32 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4521e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0xBE_VRF_nt!_??_::FNODOBFM::_string_+4521e

BUCKET_ID:  X64_0xBE_VRF_nt!_??_::FNODOBFM::_string_+4521e

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

The crashes are pointing to hard disk problems; either corrupted data or worse...

• 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 Check Disk (chkdsk) - Read Event Viewer Log.
  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 Data Lifeguard Diagnostic for Western Digital to check for a faulty hard disk.