Memory fail/BSOD watching videos.

[DanLasko]

It's been doing this lately, and i get the blue screen telling me memory has failed and is shutting down. It's only up for a second, but right before that, the screen goes nuts with distortion and i hear buzzing (audio malfunction). Thanks

HP s5660f
Windows 7 Home Premium 64bit
ATI Radeon HD 5450
1 TB hard drive. Not much on it. New computer. Months old

 

[zigzag3143]

It's been doing this lately, and i get the blue screen telling me memory has failed and is shutting down. It's only up for a second, but right before that, the screen goes nuts with distortion and i hear buzzing (audio malfunction). Thanks

HP s5660f
Windows 7 Home Premium 64bit
ATI Radeon HD 5450
1 TB hard drive. Not much on it. New computer. Months old

These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[DanLasko]

I did all of that. After the verifier step, and trying to get it to crash again, I don't think I got it to. And If it did randomly playing music on Spotify, today...I'm not sure what my next step would be. It's a new computer. I don't do anything to it other than just use it. I don't know what overclocking is. Is that just running too many things at once? Music and a browser, and random things in the background. I have a couple remote desktop apps running in the background sometimes.
If you have any ideas, just let me know. Or even if this is a common problem that I just need to live with. After it crashes, when it boots up automatically is checks a lot of things on the black and white screen. Thanks.

 

[writhziden]

Overclocking is setting hardware to run faster than it is intended to through either the BIOS or through software in Windows. If you do not know what it is, you are probably not doing it unless you have software on the system that is automatically doing it for you without your knowledge. If you have such software, your crash reports will indicate it.

Can you upload your latest crash reports by following the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html ?

 

[DanLasko]

Here you go.

 

[writhziden]

Antivirus software:

avastsvc.exe	c:\program files\avast software\avast\avastsvc.exe	1348	8	200	1380	3/2/2012 6:40 PM	6.0.1289.0	43.72 KB (44,768 bytes)	10/4/2011 9:34 PM
avastui.exe	c:\program files\avast software\avast\avastui.exe	3004	8	200	1380	3/2/2012 6:41 PM	6.0.1289.0	3.55 MB (3,722,416 bytes)	10/4/2011 9:34 PM

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\DanLasko\Windows_NT6_BSOD_jcgriff2\030212-24679-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02c58000 PsLoadedModuleList = 0xfffff800`02e95e70
Debug session time: Fri Mar  2 16:33:39.603 2012 (UTC - 7:00)
System Uptime: 0 days 15:12:52.977
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880012408a8, fffff88009f078e8, fffff88009f07150}

Probably caused by : Ntfs.sys ( Ntfs!NtfsMcbCleanupLruQueue+88 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880012408a8, The address that the exception occurred at
Arg3: fffff88009f078e8, Exception Record Address
Arg4: fffff88009f07150, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
Ntfs!NtfsMcbCleanupLruQueue+88
fffff880`012408a8 83790400        cmp     dword ptr [rcx+4],0

EXCEPTION_RECORD:  fffff88009f078e8 -- (.exr 0xfffff88009f078e8)
ExceptionAddress: fffff880012408a8 (Ntfs!NtfsMcbCleanupLruQueue+0x0000000000000088)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000004
Attempt to read from address 0000000000000004

CONTEXT:  fffff88009f07150 -- (.cxr 0xfffff88009f07150)
rax=fffff8a0027509e8 rbx=fffff88001240820 rcx=0000000000000000
rdx=0000000000002289 rsi=fffff8a002750b10 rdi=fffff8a002750ad0
rip=fffff880012408a8 rsp=fffff88009f07b20 rbp=fffff80002e6d5a0
 r8=0000000000001f40  r9=0000000000000000 r10=fffff80002c58000
r11=0000000000000155 r12=fffff8a002750ad0 r13=0000000000000001
r14=fffff88009f07ce8 r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
Ntfs!NtfsMcbCleanupLruQueue+0x88:
fffff880`012408a8 83790400        cmp     dword ptr [rcx+4],0 ds:002b:00000000`00000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000004

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f000e0
 0000000000000004 

FOLLOWUP_IP: 
Ntfs!NtfsMcbCleanupLruQueue+88
fffff880`012408a8 83790400        cmp     dword ptr [rcx+4],0

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff80002cd57e1 to fffff880012408a8

STACK_TEXT:  
fffff880`09f07b20 fffff800`02cd57e1 : fffffa80`0b2001f0 fffff880`09f07b50 00000000`00000000 fffffa80`00000002 : Ntfs!NtfsMcbCleanupLruQueue+0x88
fffff880`09f07cb0 fffff800`02f686fa : 00000000`00000000 fffffa80`0b2001f0 00000000`00000080 fffffa80`051ed040 : nt!ExpWorkerThread+0x111
fffff880`09f07d40 fffff800`02ca6b46 : fffff880`009eb180 fffffa80`0b2001f0 fffffa80`051fd040 fffff880`0121d2b4 : nt!PspSystemThreadStartup+0x5a
fffff880`09f07d80 00000000`00000000 : fffff880`09f08000 fffff880`09f02000 fffff880`09f079f0 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsMcbCleanupLruQueue+88

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d79996d

STACK_COMMAND:  .cxr 0xfffff88009f07150 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_Ntfs!NtfsMcbCleanupLruQueue+88

BUCKET_ID:  X64_0x7E_Ntfs!NtfsMcbCleanupLruQueue+88

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

Possible causes are Memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...


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

 

[DanLasko]

Chkdsk:

Chkdsk was executed in read/write mode.

Checking file system on D:
Volume label is HP_RECOVERY.

CHKDSK is verifying files (stage 1 of 5)...
256 file records processed. File verification completed.
0 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
314 index entries processed. Index verification completed.


CHKDSK is verifying security descriptors (stage 3 of 5)...
256 file SDs/SIDs processed. Cleaning up 8 unused index entries from index $SII of file 0x9.
Cleaning up 8 unused index entries from index $SDH of file 0x9.
Cleaning up 8 unused security descriptors.
Security descriptor verification completed.
30 data files processed. CHKDSK is verifying Usn Journal...
248144 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
240 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
392555 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

12794879 KB total disk space.
11157740 KB in 143 files.
60 KB in 31 indexes.
66855 KB in use by the system.
65536 KB occupied by the log file.
1570224 KB available on disk.

4096 bytes in each allocation unit.
3198719 total allocation units on disk.
392556 allocation units available on disk.




Wininit:

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

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

CHKDSK is verifying files (stage 1 of 5)...
465920 file records processed. File verification completed.
404 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)...
547298 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
465920 file SDs/SIDs processed. Cleaning up 29 unused index entries from index $SII of file 0x9.
Cleaning up 29 unused index entries from index $SDH of file 0x9.
Cleaning up 29 unused security descriptors.
Security descriptor verification completed.
40690 data files processed. CHKDSK is verifying Usn Journal...
34277864 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
465904 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
125816840 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

963862527 KB total disk space.
459863972 KB in 233318 files.
135088 KB in 40691 indexes.
0 KB in bad sectors.
596107 KB in use by the system.
65536 KB occupied by the log file.
503267360 KB available on disk.

4096 bytes in each allocation unit.
240965631 total allocation units on disk.
125816840 allocation units available on disk.

Internal Info:
00 1c 07 00 65 2e 04 00 b7 c6 07 00 00 00 00 00 ....e...........
0b 0e 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]

Disk check came up clean, so that is not too likely to be causing the issue.

I do see not all Windows updates are installed. Update to Service Pack 1 (SP1):

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site
​

Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH