New
#1
Random Crashes
So I just built this computer and I've already had three crashes.
Hope someone can help =]
So I just built this computer and I've already had three crashes.
Hope someone can help =]
3 errors, 3 different STOP codes. This is usually indicative of a hardware problem, so I'd suggest starting with these diagnostics:
If the diagnostics come up clean and the BSOD's continue - please post back and we'll run more tests.H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)
Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
Here's a summary of the BSOD's:
Code:Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Thu Jan 21 15:28:20.719 2010 (GMT-5) System Uptime: 0 days 0:06:52.061 BugCheck 34, {50830, fffff880025fa7d8, fffff880025fa030, fffff800028c02a9} Probably caused by : memory_corruption ( nt!MiRemoveNode+149 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Thu Jan 21 15:34:28.171 2010 (GMT-5) System Uptime: 0 days 0:05:04.888 BugCheck 24, {1904fb, fffff8800317e738, fffff8800317df90, fffff8800135344a} Probably caused by : Ntfs.sys ( Ntfs!EfsCleanup+1a ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Fri Jan 22 19:24:14.079 2010 (GMT-5) System Uptime: 0 days 10:18:33.390 BugCheck 1A, {5002, fffff780c0000000, 8e32, 40007e90fffffffe} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a247 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: chrome.exe
So i understand what you mean but I ran memtest and no problems, now i admit I couldnt get the HDD test to work properly(something about missing something) but could it be that i just have some faulty drives?
So here are two more crashes I had....happened when i was trying to post here actually xD
Hi DK
These were caused by memory corruption.
I would
download and run memtestx86 for at least 5 passes
If you are overclcocking STOP
Run a system file check
type cmd in search>right click and run as admin>sfc /scannow
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\092409-18174-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\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 Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a49000 PsLoadedModuleList = 0xfffff800`02c86e50 Debug session time: Thu Sep 24 00:44:43.721 2009 (GMT-5) System Uptime: 0 days 0:20:19.032 Loading Kernel Symbols ............................................................... ................................................................ ............. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffffa800e6c4010, 2, 1, fffff80002b77a57} Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+87 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffffa800e6c4010, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002b77a57, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf10e0 fffffa800e6c4010 CURRENT_IRQL: 2 FAULTING_IP: nt!MiReleaseConfirmedPageFileSpace+87 fffff800`02b77a57 480fb328 btr qword ptr [rax],rbp CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: kldw.exe TRAP_FRAME: fffff88007b5e620 -- (.trap 0xfffff88007b5e620) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa80066c4010 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002b77a57 rsp=fffff88007b5e7b0 rbp=0000000040000000 r8=fffff88007b5e7e0 r9=fffffa800502a650 r10=0000000fffffffff r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!MiReleaseConfirmedPageFileSpace+0x87: fffff800`02b77a57 480fb328 btr qword ptr [rax],rbp ds:0004:fffffa80`066c4010=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002aba469 to fffff80002abaf00 STACK_TEXT: fffff880`07b5e4d8 fffff800`02aba469 : 00000000`0000000a fffffa80`0e6c4010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`07b5e4e0 fffff800`02ab90e0 : fffff880`07b5e670 fffffa80`041ab760 fffffa80`00001000 00000000`00000801 : nt!KiBugCheckDispatch+0x69 fffff880`07b5e620 fffff800`02b77a57 : fffffa80`04a284c0 fffffa80`041ab760 fffffa80`0600a870 fffff880`07b5e808 : nt!KiPageFault+0x260 fffff880`07b5e7b0 fffff800`02b2d108 : 40000000`00000000 fffffa80`0183c180 00000000`6e350008 00000000`6e353000 : nt!MiReleaseConfirmedPageFileSpace+0x87 fffff880`07b5e830 fffff800`02aee5d9 : 00000000`00000000 00000000`6e35bfff fffffa80`00000000 fffffa80`05020000 : nt! ?? ::FNODOBFM::`string'+0x33868 fffff880`07b5e9f0 fffff800`02dd0e50 : fffffa80`04852c10 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9 fffff880`07b5eb10 fffff800`02dd125b : 00000980`00000000 00000000`6e350000 fffffa80`00000001 fffffa80`06d13160 : nt!MiUnmapViewOfSection+0x1b0 fffff880`07b5ebd0 fffff800`02aba153 : 00000000`00000000 00000000`00000001 fffffa80`0502a650 00000000`00000004 : nt!NtUnmapViewOfSection+0x5f fffff880`07b5ec20 00000000`76d0015a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0008e308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d0015a STACK_COMMAND: kb FOLLOWUP_IP: nt!MiReleaseConfirmedPageFileSpace+87 fffff800`02b77a57 480fb328 btr qword ptr [rax],rbp SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiReleaseConfirmedPageFileSpace+87 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+87 BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+87 Followup: MachineOwner ---------
So i did what you said and you where right, it said there where some corrupt files. I had the ram to 1:4 and i guess that might have something to do with it. still, where do i go from here?
It told me to see the file i attached, but i have no idea what to do with it to be honest, help?
OK So I have definitely some issues =[
This are a lot of crashes and I would really appreciate some help.
I stopped OC the ram, and it most definitely seemed to help for a while.
So i started letting my sisters use the computer and things started acting up again.
Any help would be appreciated.
Any help?