Solved BSOD even when not under load

[mapstone]

Hi guys,

I have been getting BSOD in the past every second day, I have formatted my computer multiple times, which seems to make it a lot less frequent but not completely fix the problem

So the two most recent crashes I was playing a game and as soon as I exited to the desktop it crashed and the second one I left the computer on over night downloading (not under any real load) and woke up to find it has crashed.

I am possibly thinking it could be bad RAM as it is a crap brand, but if anyone can look into my attachment and make any suggestions, that would be greatly appreciated

Thanks.

 

[mapstone]

SYSTEM SPECS:


OS windows 7 home premiujm 64 bit CPU intel core i5 2400 Motherboard ASRock H61M/U3S3 (CPUSocket) Memory 8.00 GB Dual-Channel DDR3 @ 532MHz Graphics Card(s) 1023MB GeForce GTX 550 Ti (Gigabyte) Sound Card na Monitor(s) Displays Acer H274HL (1920x1080@60Hz) Screen Resolution N/A Hard Drives 932GB Seagate ST31000524AS ATA Device (SATA) PSU corsair gs600

 

[koolkat77]

Welcome.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• How to Test and Diagnose RAM Issues with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

• If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial: How to Run the Memory Diagnostics Tool in Windows 7

 

[mapstone]

Thanks I will try that and let you know how i go, in the dump files I had is there any answer to why the system had BSOD?

 

[koolkat77]

Yes, norton seems to be crashing there but I suspect RAM. So let us know the results.

 

[mapstone]

I carried out the memtest overnight with all passes no errors,I had another BSOD in the meantime, so thought I would upload that.

Still going to buy decent RAM later this week as I still suspect it could be the intermittent problem.

Thanks for your help again

 

[koolkat77]

Norton tends to cause BSOD-s. Recommend uninstalling it with the Norton Removal Tool and replace with Microsoft Security Essentials. See if this stops the BSOD-s.

• Download and run the Norton Removal Tool to remove the Norton Product

Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

• Microsoft Security Essentials, Free antivirus for windows.
• Malwarebytes Anti-Malware Free
• Good and Free system security combination
• 
  

   Warning

:ar: Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Perform a System File Check to check the integrity of all protected Windows 7 :

1. Click on the start rb:
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type

   SFC /scannow

Full tutorial here:

• SFC /Scannow Command - System File Checker

Disk Check on your hard drive for file system errors and bad sectors on it.

• How to run Disk Check on Windows 7

Reduce items at start-up. Nothing except anti-virus.

• http://www.sevenforums.com/tutorials/1401-startup-programs-change.html
• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

For monitoring the heat/celsius of the system, use Speccy or HWMonitor:

• Speccy System Information
• HWMonitor

 

[mapstone]

ok tried uninstalling norton and had not had a BSOD in ages, but had one just now while I was playing a game.

I have attached a copy of the dump file.

Any help is much appreciated.

Thank.

 

[mapstone]

try this attachment, incidentally didn't wait for the program to finish scanning all file.

Thanks Again!

 

[koolkat77]

Looks like RAM is the problem.

Since memtest did not find errors I would recommend getting a new kit.
or borrow to test.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8887, fffffa8004c12050, fffffa8004c136a0, 503}

Probably caused by : hardware_ram ( ZEROED_PAGE_CORRUPTED )

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

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

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

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


BUGCHECK_STR:  0x1a_8887

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  steam.exe

CURRENT_IRQL:  2

STACK_TEXT:  
fffff880`0b6705e8 fffff800`0308652e : 00000000`0000001a 00000000`00008887 fffffa80`04c12050 fffffa80`04c136a0 : nt!KeBugCheckEx
fffff880`0b6705f0 fffff800`03042f0d : 00000000`00195b57 fffffa80`04c12050 fffff8a0`0cec0848 fffffa80`07116b38 : nt!MiUnlinkPageFromLockedList+0x1de
fffff880`0b670670 fffff800`03043892 : 00000000`00000000 fffffa80`0aeac300 00000000`00000000 fffff880`0b670900 : nt!MmPurgeSection+0x4bd
fffff880`0b670760 fffff800`030447d1 : fffffa80`07078da8 fffff880`031d77f0 fffff8a0`00000000 fffff880`00000000 : nt!CcPurgeCacheSection+0x172
fffff880`0b6707d0 fffff800`0309bd72 : fffffa80`0aeac3a0 fffff880`031d77f0 00000000`00000001 fffffa80`0aeac3a0 : nt!CcPurgeAndClearCacheSection+0x75
fffff880`0b670880 fffff880`01431f70 : 00000000`00000000 00000000`00000000 fffff8a0`0485ac70 00000000`00000000 : nt!CcSetFileSizesEx+0x2c6
fffff880`0b670900 fffff880`014aa3fc : 00000000`00000000 fffff8a0`0485ac70 00000000`00000000 fffffa80`0b56fb01 : Ntfs!NtfsSetBothCacheSizes+0x50
fffff880`0b670960 fffff880`014a2abe : fffffa80`0b56fb80 fffffa80`0ac0f580 fffffa80`0b56fb00 00000000`00000000 : Ntfs!NtfsDeleteAllocation+0x2cc
fffff880`0b670a40 fffff880`014a1b49 : fffffa80`0b56fb80 fffffa80`0b58de70 fffff8a0`0485ab40 00000000`00000020 : Ntfs!NtfsReplaceAttribute+0x16e
fffff880`0b670b30 fffff880`014aeff5 : fffffa80`0b56fb80 fffffa80`0b58db60 fffff8a0`0485aed8 fffff8a0`0485ab00 : Ntfs!NtfsOverwriteAttr+0x585
fffff880`0b670c90 fffff880`014b211f : fffffa80`0b56fb80 fffffa80`0b58db60 fffff8a0`0485aed8 fffff880`00000048 : Ntfs!NtfsOpenAttributeInExistingFile+0x6e5
fffff880`0b670e20 fffff880`014c21f6 : fffffa80`0b56fb80 fffffa80`0b58db60 fffff8a0`0485aed8 00000000`00000705 : Ntfs!NtfsOpenExistingPrefixFcb+0x1ef
fffff880`0b670f10 fffff880`014bf9a1 : fffffa80`0b56fb80 fffffa80`0b58db60 fffff880`0b6710e0 fffff880`0b671130 : Ntfs!NtfsFindStartingNode+0x5e6
fffff880`0b670fe0 fffff880`01428a0d : fffffa80`0b56fb80 fffffa80`0b58db60 fffff880`0b671390 fffffa80`0b302700 : Ntfs!NtfsCommonCreate+0x3e1
fffff880`0b6711c0 fffff800`03081968 : fffff880`0b671300 00000000`00000000 fffff8a0`16aa99f0 fffff8a0`129ed2a0 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`0b6711f0 fffff880`0142918f : fffff880`014289f0 fffff880`01428020 fffff880`0b671300 fffff880`014ca000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`0b6712d0 fffff880`014c2a2c : 00000000`00000000 00000000`00000000 fffff880`0b671520 fffffa80`0b58db60 : Ntfs!NtfsCommonCreateOnNewStack+0x4f
fffff880`0b671330 fffff880`0111ebcf : fffffa80`07a0b030 fffffa80`0b58db60 00000000`00000000 00000000`00000000 : Ntfs!NtfsFsdCreate+0x1ac
fffff880`0b6714e0 fffff880`0113e2b9 : fffffa80`0b58db60 fffffa80`07a05010 fffffa80`0b58db00 fffffa80`0784e860 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0b671570 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!FltpCreate+0x2a9


STACK_COMMAND:  kb

SYMBOL_NAME:  ZEROED_PAGE_CORRUPTED

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware_ram

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x1a_8887_ZEROED_PAGE_CORRUPTED

BUCKET_ID:  X64_0x1a_8887_ZEROED_PAGE_CORRUPTED

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

 

[mapstone]

I'm going to get new RAM tomorrow, just wondering what program you used to get that bug check analysis report?

 

[koolkat77]

Explained here: http://www.sevenforums.com/crash-lo...d-analysis-getting-started-5.html#post2251058

How I do it: http://www.sevenforums.com/crash-lockup-debug-how/277355-debugging-bsod-my-way.html

 

[mapstone]

Ok have replaced ram to 2X 8 gb kingston sticks, so far so good! But time will tell....

Thanks for your help koolkat!

 

[koolkat77]

Keep us posted and good luck.

 

[koolkat77]

Ok have replaced ram to 2X 8 gb kingston sticks, so far so good! But time will tell....

Thanks for your help koolkat!

So did getting new ram solve your problem?

   Tip

If your problem is solved please use the

Mark this thread as solved link at the top of your thread or down on the left corner

 

[mapstone]

yep hasn't missed a beat!

 

[koolkat77]

Then you can mark this thread as solved. If you have problems again, create a new one

Good luck.