BSOD in everything I do

[XplicitMind]

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.

 

[XplicitMind]

Added two more minidumps.

Recent BSOD "Attempt to write in read-only memory"

https://rapidshare.com/files/764117480/MEMORY.DMP < -- Another big DMP file.

 

[XplicitMind]

Update: Mozilla Firefox all of a sudden crashes and the windows bar on the bottom suddenly turned color. As soon as I clicked on the Firefox icon, I get a BSOD. Currently uploading.

 

[XplicitMind]

Bump.

 

[XplicitMind]

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.

 

[writhziden]

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

• http://www.sevenforums.com/crashes-...hile-playing-sw-tor-idling-6.html#post1780510
• http://www.sevenforums.com/crashes-...le-using-firefox-playing-lol.html#post1838992
• http://www.sevenforums.com/crashes-debugging/220698-bsod-portcls-sys.html#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.

 

[XplicitMind]

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.

 

[writhziden]

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 http://www.sevenforums.com/crashes-...hile-playing-sw-tor-idling-6.html#post1780510 and post back the CPU-Z screenshots and voltage info.

 

[XplicitMind]

Enclosed are the CPU-Z pics.

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

 

[writhziden]

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 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 Data Lifeguard Diagnostic for Western Digital to check for a faulty hard disk.

 

[XplicitMind]

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)...
326144 file records processed. File verification completed.
280 large file records processed. 0 bad file records processed. 2 EA records processed. 60 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
373444 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
326144 file SDs/SIDs processed. Cleaning up 1364 unused index entries from index $SII of file 0x9.
Cleaning up 1364 unused index entries from index $SDH of file 0x9.
Cleaning up 1364 unused security descriptors.
Security descriptor verification completed.
23651 data files processed. CHKDSK is verifying Usn Journal...
34156216 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
326128 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
224660636 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

976657407 KB total disk space.
77502660 KB in 75005 files.
54732 KB in 23652 indexes.
0 KB in bad sectors.
457467 KB in use by the system.
65536 KB occupied by the log file.
898642548 KB available on disk.

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

Internal Info:
00 fa 04 00 6c 81 01 00 09 f9 02 00 00 00 00 00 ....l...........
e3 00 00 00 3c 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.

I've ran the chkdsk multiple times and only once it did this, which was yesterday.

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


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
The attribute of type 0x80 and instance tag 0x0 in file 0xa56
has allocated length of 0xba2000 instead of 0xb82000.
Deleted corrupt attribute list entry
with type code 128 in file 2646.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x4a000000000504. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 1284.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x23000000004a86. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 19078.
Unable to locate attribute with instance tag 0x0 and segment
reference 0xe000000005307. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 21255.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x180000000057d8. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 22488.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x130000000102cd. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 66253.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x16000000014425. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 82981.
Attribute record of type 0x80 and instance tag 0x6 is cross linked
starting at 0x84ef14 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x6
in file 0x3601 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 13825.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x838c75 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x23138 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 143672.
326144 file records processed. File verification completed.
Deleting orphan file record segment 1284.
473 large file records processed. 0 bad file records processed. 2 EA records processed. 60 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
The file reference 0x3000000021d47 of index entry SrtTrail.log of index $I30
with parent 0x2e is not the same as 0x5000000021d47.
Deleting index entry SrtTrail.log in index $I30 of file 46.
The file reference 0x3000000021d49 of index entry uploadrecord.txt of index $I30
with parent 0x2e is not the same as 0x4000000021d49.
Deleting index entry uploadrecord.txt in index $I30 of file 46.
The file reference 0x3000000021d49 of index entry UPLOAD~1.TXT of index $I30
with parent 0x2e is not the same as 0x4000000021d49.
Deleting index entry UPLOAD~1.TXT in index $I30 of file 46.
The file reference 0xb8000000000016 of index entry WPDNSE of index $I30
with parent 0x13961 is not the same as 0xb9000000000016.
Deleting index entry WPDNSE in index $I30 of file 80225.
The file reference 0xca000000000497 of index entry ec3e36af0cdcb3e1.customDestinations-ms of index $I30
with parent 0x13c85 is not the same as 0xcf000000000497.
Deleting index entry ec3e36af0cdcb3e1.customDestinations-ms in index $I30 of file 81029.
The file reference 0xca000000000497 of index entry EC3E36~1.CUS of index $I30
with parent 0x13c85 is not the same as 0xcf000000000497.
Deleting index entry EC3E36~1.CUS in index $I30 of file 81029.
The file reference 0x900000001ecad of index entry bcab8d2d-5dd5-4ac4-9e6c-da4e9288a8b2.png of index $I30
with parent 0x13cd1 is not the same as 0xb00000001ecad.
Deleting index entry bcab8d2d-5dd5-4ac4-9e6c-da4e9288a8b2.png in index $I30 of file 81105.
The file reference 0x900000001ecad of index entry BCAB8D~1.PNG of index $I30
with parent 0x13cd1 is not the same as 0xb00000001ecad.
Deleting index entry BCAB8D~1.PNG in index $I30 of file 81105.
The file reference 0x18000000014361 of index entry HDAudio.NVX of index $I30
with parent 0x15401 is not the same as 0x19000000014361.
Deleting index entry HDAudio.NVX in index $I30 of file 87041.
The file reference 0xc000000014417 of index entry Report.wer of index $I30
with parent 0x23123 is not the same as 0xb000000014417.
Deleting index entry Report.wer in index $I30 of file 143651.
392804 index entries processed. Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file WPDNSE (22) into directory file 80225.
Recovering orphaned file HDAudio.NVX (1175) into directory file 87041.
Recovering orphaned file SC20E8~1 (126125) into directory file 80225.
Recovering orphaned file scoped_dir9140 (126125) into directory file 80225.
Recovering orphaned file tmp.edb (138567) into directory file 242067.
Recovering orphaned file DMI84D8.tmp (138569) into directory file 80225.
Recovering orphaned file CRITIC~4.163 (141053) into directory file 99492.
Recovering orphaned file Critical_6.1.7600.16385_38a965e7e5582d5582a6e5b2bfae70caa59d63b_cab_09a0ab99 (141053) into directory file 99492.
Recovering orphaned file 54155D~1 (143640) into directory file 99434.
Recovering orphaned file 54155d2271d908e25db4a09e49c9b287_d90c5151-bd99-47e9-88bc-b9726cebacbd (143640) into directory file 99434.
Recovering orphaned file NO63E0~1 (143651) into directory file 81486.
Recovering orphaned file NonCritical_x64_8dd2a6bea57836935d86a299b4735d5c6f632592_0be4ac83 (143651) into directory file 81486.
Recovering orphaned file SC8FD5~1 (143677) into directory file 80225.
Recovering orphaned file scoped_dir28769 (143677) into directory file 80225.
Recovering orphaned file SC4561~1 (143682) into directory file 80225.
Recovering orphaned file scoped_dir19712 (143682) into directory file 80225.
30 unindexed files scanned. CHKDSK is recovering remaining unindexed files.
20 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
326144 file SDs/SIDs processed. Cleaning up 39 unused index entries from index $SII of file 0x9.
Cleaning up 39 unused index entries from index $SDH of file 0x9.
Cleaning up 39 unused security descriptors.
Security descriptor verification completed.
Inserting data attribute into file 2646.
Inserting data attribute into file 13825.
Inserting data attribute into file 143672.
33334 data files processed. CHKDSK is verifying Usn Journal...
The USN Journal length 0x8b206ce8 in file 0xe107 is less the
largest USN encountered, 0x8b2c4ea8, plus eight in file 0xa56.
Repairing Usn Journal $J data stream.
Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

976657407 KB total disk space.
150343304 KB in 147131 files.
87968 KB in 33335 indexes.
0 KB in bad sectors.
423855 KB in use by the system.
65536 KB occupied by the log file.
825802280 KB available on disk.

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

Internal Info:
00 fa 04 00 fc c0 02 00 12 16 05 00 00 00 00 00 ................
9f 01 00 00 3c 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.

I've done the Data Lifeguard Diagnostic Extended test earlier today and came up with no errors.

 

[writhziden]

Have you tried running Windows one module at a time (remove a memory module)? Test each module by seeing if the crashes stop. Also, test the module slots in the motherboard to see if there is a bad slot. Try to find a good module and good slot. Then test the other module in the good slot to see if it is a bad module. Test the other slots with the good module to find any bad slots. Avoid Static Damage to Your PC when swapping modules.

 

[XplicitMind]

How long should I test one module at a time?

 

[writhziden]

At least as long as it usually takes for your get a crash (on average). Longer if you want to make sure.

 

[XplicitMind]

Alright. The moment I crash, I'll swap a module to each slot. Thanks for all the help.

I'll reply back to this thread with my findings.

 

[writhziden]

No problem. Sorry if I was a little harsh earlier. We do want to help you, but it gets confusing and frustrating when people jump from thread to thread and sometimes people helping can take that as a sign of disrespect. Glad you cleared up why you were doing it, and your reasoning was understandable. I will keep an eye on this thread as long as you need help, so no need to start a new one.