New
#1
Blue Screen BSOD
Hello, I use my computer daily and the BSODs will constantly happen mostly once a day.
OS: Windows 7 Ultimate x64
Installed myself
All parts are brand new ~
About 2weeks old now.
Hello, I use my computer daily and the BSODs will constantly happen mostly once a day.
OS: Windows 7 Ultimate x64
Installed myself
All parts are brand new ~
About 2weeks old now.
Hi and welcome
More than half of these point directly to memory corruption, and the other indirectly do as well. To test your memory
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Let us know if you need further assistance
Ken
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\072910-18548-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Whitespace at end of path element Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols *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 Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c13000 PsLoadedModuleList = 0xfffff800`02e50e50 Debug session time: Thu Jul 29 12:14:06.127 2010 (GMT-4) System Uptime: 0 days 1:56:50.579 Loading Kernel Symbols ............................................................... ................................................................ ................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff9600014ba54, fffff880039c5fa0, 0} Probably caused by : memory_corruption Followup: memory_corruption --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff9600014ba54, Address of the exception record for the exception that caused the bugcheck Arg3: fffff880039c5fa0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: win32k!xxxReadPostMessage+e0 fffff960`0014ba54 488b8960010000 mov rcx,qword ptr [rcx+160h] CONTEXT: fffff880039c5fa0 -- (.cxr 0xfffff880039c5fa0) rax=0000030000000630 rbx=fffff900c22a5c30 rcx=0000000000000113 rdx=0000000000000000 rsi=fffff900c01e5a00 rdi=0000000000000000 rip=fffff9600014ba54 rsp=fffff880039c6980 rbp=fffff880039c6ca0 r8=0000000000000001 r9=0000000000000000 r10=0000000000000000 r11=fffff900c01e5a00 r12=fffff880039c6b68 r13=fffff900c22a5ed8 r14=0000000000000001 r15=0000000000000000 iopl=0 nv up ei pl nz na pe cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010203 win32k!xxxReadPostMessage+0xe0: fffff960`0014ba54 488b8960010000 mov rcx,qword ptr [rcx+160h] ds:002b:00000000`00000273=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x3B PROCESS_NAME: speedfan.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff9600014ba54 STACK_TEXT: fffff880`039c6980 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!xxxReadPostMessage+0xe0 CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k 4 errors : !win32k (fffff9600014b35e-fffff9600014bf46) fffff9600014b350 01 00 00 0f b7 41 0a 66 85 41 04 0f 85 09 *fd ff .....A.f.A...... ... fffff9600014ba50 c8 01 00 00 48 8b *89 60 01 00 00 48 8b 46 40 48 ....H..`...H.F@H ... fffff9600014bbd0 fe 00 00 66 21 41 *04 48 8b 8b 70 01 00 00 b8 ff ...f!A.H..p..... ... fffff9600014bf40 33 c0 89 44 24 60 *31 c9 48 89 4c 24 58 21 44 24 3..D$`1.H.L$X!D$ MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: STRIDE STACK_COMMAND: .cxr 0xfffff880039c5fa0 ; kb FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE Followup: memory_corruption ---------
Hello,
Doing a RAM test is a good idea, as Ken recommended. See this tutorial: RAM - Test with Memtest86+
Out of the three dumps I ran, I see 1 was while Chrome was running, the other when the Windows Media Player Network was running. In both cases, internet was actively being used.
I would therefore recommend removing AVG completely. Here is the removal tool: http://download.avg.com/filedir/util...removerx64.exe
It is a common cause of BSODs on Vista and 7 systems.
Replace it with MSE: http://www.microsoft.com/security_essentials
I also recommend updating UtraISO, which I'm guessing is using the outdated ISODrv64.sys driver:If the BSODs persist after those 2 steps, please enable driver verifier: Driver Verifier - Enable and DisableCode:ISODrv64.sys Fri Nov 02 23:21:18 2007
...Summary of the Dumps:Code:Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Tue Aug 31 11:40:58.207 2010 (UTC - 4:00) System Uptime: 0 days 2:13:23.284 BugCheck 3B, {c0000005, fffff960000ded84, fffff88007e24b30, 0} Probably caused by : memory_corruption BUGCHECK_STR: 0x3B PROCESS_NAME: chrome.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sun Aug 29 14:03:17.096 2010 (UTC - 4:00) System Uptime: 0 days 3:40:54.089 BugCheck 1E, {ffffffffc000001d, fffff960001b9f60, 0, fffff900c06c1f00} Probably caused by : win32k.sys ( win32k!NtUserMagGetContextInformation+118 ) BUGCHECK_STR: 0x1E_c000001d PROCESS_NAME: wmpnetwk.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sat Aug 28 12:47:49.869 2010 (UTC - 4:00) System Uptime: 0 days 3:28:01.320 BugCheck 1E, {ffffffffc0000005, fffff80002fa9d9c, 0, ffffffffffffffff} Probably caused by : memory_corruption ( nt!MiApplyCompressedFixups+40 ) BUGCHECK_STR: 0x1E_c0000005 PROCESS_NAME: SC2.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Alright I did the ramtesting and got around 10 passes before rebooting and saw approx. 1500+ errors? Is there a file I should be sending you guys to look at? Or is that suppose to fix it.
I also removed AVG and did everything else..
You need to replace the ram stick that is giving you errors... Did you test them one at a time, in different slots??
No, the errors are telling you that you have bad RAM or a bad controller. Try running the tests one stick at a time and see if you are still seeing errors - if so, replace the memory. If the errors go away, try testing each stick in other slots on the motherboard to see if it's a motherboard issue, or just a stability issue with those particular RAM sticks together in that board.
Ultimately though, as soon as memtest throws errors my suggestion is to replace all of the RAM with known-good modules (either from the vendor or another machine) and retest.
Here is a tutorial for diagnosing RAM issues. You can skip down to the "If you have errors" part.
Testing the ram is just that, a test.... You will need to replace the modules that fail the test...