I bought a new pc about a week ago..Had problems with BSOD's after the Windows loading screen before entering the login page..did a couple of formats, nothing happened..then found out that when i turn the pc on, got the BSOD (the pc restarts), turned the pc off by holding the ON/OFF button, then when i turned it back on after 10 seconds it booted fine..It's only ever brought up a BSOD 2 times after a successful boot, one time when i clicked on My Documents..and another when i clicked on Firefox..
Here is the Windows_NT6_BSOD_jcgriff2 folder: Attachment 100224
-My OS is Windows 7 Ultimate x64
-It is OEM version ( i Self-Built it online through a PC company that sent it to me "Ready-to-go"
-The PC as i said is 1 week old.
-I have formatted Windows 7 - 8 times.
Here is the Windows_NT6_BSOD_jcgriff2 folder: Attachment 100224
-My OS is Windows 7 Ultimate x64
-It is OEM version ( i Self-Built it online through a PC company that sent it to me "Ready-to-go"
-The PC as i said is 1 week old.
-I have formatted Windows 7 - 8 times.
I looked at six of the dumps. All six point to hardware issues. Five of these indicate memory corruption. One blames Direct X and Monitor Manager. The longest up time before crashing was 40 seconds.
You can read the usual causes of these errors in the links below.
Error code 3B, SYSTEM_SERVICE_EXCEPTION - BSOD Index
Error code BE, ATTEMPTED_WRITE_TO_READONLY_MEMORY - BSOD Index
Error code 1A, MEMORY_MANAGEMENT - BSOD Index
Error code 50, PAGE_FAULT_IN_NONPAGED_AREA - BSOD Index
Have you overclocked anything? If so, return all OC to default values.
I suggest that you run Memtest to test your ram; run Prime to test your CPU and RAM; and run Furmark to test your graphics card. Check the tutorials below.
RAM - Test with Memtest86+
http://www.sevenforums.com/tutorials...t-prime95.html
Video Card - Stress Test with Furmark
I will also ask the hardware guys to look at this thread. I am, by no means, a hardware expert.
Please post the results of each of these tests.
You can read the usual causes of these errors in the links below.
Error code 3B, SYSTEM_SERVICE_EXCEPTION - BSOD Index
Error code BE, ATTEMPTED_WRITE_TO_READONLY_MEMORY - BSOD Index
Error code 1A, MEMORY_MANAGEMENT - BSOD Index
Error code 50, PAGE_FAULT_IN_NONPAGED_AREA - BSOD Index
Have you overclocked anything? If so, return all OC to default values.
I suggest that you run Memtest to test your ram; run Prime to test your CPU and RAM; and run Furmark to test your graphics card. Check the tutorials below.
RAM - Test with Memtest86+
http://www.sevenforums.com/tutorials...t-prime95.html
Video Card - Stress Test with Furmark
I will also ask the hardware guys to look at this thread. I am, by no means, a hardware expert.
Please post the results of each of these tests.
Code:
Kernel base = 0xfffff800`02e51000 PsLoadedModuleList = 0xfffff800`0308ee50 Debug session time: Sat Sep 25 07:03:47.358 2010 (GMT-4) System Uptime: 0 days 0:00:40.840 Loading Kernel Symbols ............................................................... ................................................................ .................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff8000319d74d, fffff880088a8770, 0} Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd ) Followup: MachineOwner --------- 3: 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: fffff8000319d74d, Address of the exception record for the exception that caused the bugcheck Arg3: fffff880088a8770, 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: nt!CmpKcbCacheLookup+1dd fffff800`0319d74d 418b45f4 mov eax,dword ptr [r13-0Ch] CONTEXT: fffff880088a8770 -- (.cxr 0xfffff880088a8770) rax=0000000000000005 rbx=0000000000000000 rcx=000000000000004b rdx=0000000000000019 rsi=fffff8a001e62a18 rdi=fffff880088a9350 rip=fffff8000319d74d rsp=fffff880088a9140 rbp=fffff8a001e62420 r8=0000000000000009 r9=0000000000000000 r10=0000000000000014 r11=fffff880088a92d8 r12=fffff8a00260d948 r13=f7fff8a002672140 r14=0000000000000005 r15=0000000000000001 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 nt!CmpKcbCacheLookup+0x1dd: fffff800`0319d74d 418b45f4 mov eax,dword ptr [r13-0Ch] ds:002b:f7fff8a0`02672134=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: AVGIDSAgent.ex CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8000319d74d STACK_TEXT: fffff880`088a9140 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpKcbCacheLookup+0x1dd FOLLOWUP_IP: nt!CmpKcbCacheLookup+1dd fffff800`0319d74d 418b45f4 mov eax,dword ptr [r13-0Ch] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!CmpKcbCacheLookup+1dd FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff880088a8770 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!CmpKcbCacheLookup+1dd BUCKET_ID: X64_0x3B_nt!CmpKcbCacheLookup+1dd Followup: MachineOwner --------- Kernel base = 0xfffff800`02e16000 PsLoadedModuleList = 0xfffff800`03053e50 Debug session time: Fri Sep 24 17:41:51.207 2010 (GMT-4) System Uptime: 0 days 0:00:18.316 Loading Kernel Symbols ............................................................... ................................................................ . Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck BE, {fffff8800404f478, 800000011708b121, fffff88004da3100, b} Probably caused by : dxgkrnl.sys ( dxgkrnl!MONITOR_MGR::_GetMonitorInstance+cb ) Followup: MachineOwner --------- 2: 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: fffff8800404f478, Virtual address for the attempted write. Arg2: 800000011708b121, PTE contents. Arg3: fffff88004da3100, (reserved) Arg4: 000000000000000b, (reserved) Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xBE PROCESS_NAME: csrss.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88004da3100 -- (.trap 0xfffff88004da3100) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000001 rbx=0000000000000000 rcx=fffffa80058eed98 rdx=0000000000100100 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880041155b7 rsp=fffff88004da3290 rbp=0000000000100100 r8=0000000000000000 r9=fffff88004da3340 r10=0000000000000000 r11=fffff88001873120 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc dxgkrnl!MONITOR_MGR::_GetMonitorInstance+0xcb: fffff880`041155b7 ff15bb9ef3ff call qword ptr [dxgkrnl!_imp_KeAcquireGuardedMutex (fffff880`0404f478)] ds:fffff880`0404f478={nt!KeAcquireGuardedMutex (fffff800`02e9d920)} Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002f06ae2 to fffff80002e86740 STACK_TEXT: fffff880`04da2f98 fffff800`02f06ae2 : 00000000`000000be fffff880`0404f478 80000001`1708b121 fffff880`04da3100 : nt!KeBugCheckEx fffff880`04da2fa0 fffff800`02e8482e : 00000000`00000001 fffffa80`058eed98 fffff6fb`7dbf1000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4237e fffff880`04da3100 fffff880`041155b7 : 00000000`0000000f 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e fffff880`04da3290 fffff880`04111d9f : 00000000`00100100 00000000`00100100 fffffa80`05b71000 00000000`00000001 : dxgkrnl!MONITOR_MGR::_GetMonitorInstance+0xcb fffff880`04da32e0 fffff880`040d50e1 : 00000000`00000000 00000000`fffff8fb 00000000`00100100 00000000`00000000 : dxgkrnl!MonitorGetMonitorHandle+0x143 fffff880`04da3340 fffff880`040d5f58 : 00000000`00000010 00000000`ffffffff 00000000`00000000 00000000`00000000 : dxgkrnl!VIDPN_MGR::OnMonitorConnectionChanged+0x13d fffff880`04da33b0 fffff880`04115d6c : fffffa80`058eedd0 00000000`00000001 fffff8a0`01ce3c00 fffffa80`04e045d0 : dxgkrnl!VIDPN_MGR::_MonitorEventHandler+0x6ec fffff880`04da3410 fffff880`041132e7 : fffffa80`058eecf0 00000000`00100100 00000000`00000001 00000000`00000001 : dxgkrnl!MONITOR_MGR::_IssueMonitorEvent+0x130 fffff880`04da3470 fffff880`041108e8 : fffffa80`04e045d0 fffffa80`05b71000 fffffa80`05b71000 00000000`00000005 : dxgkrnl!MONITOR_MGR::_HandleCreatePhysicalMonitor+0xcf fffff880`04da34f0 fffff880`040c1cdf : fffffa80`00000000 fffffa80`fffffdda fffffa80`04e04480 00000000`00000700 : dxgkrnl!MonitorCreatePhysicalMonitor+0x13c fffff880`04da3570 fffff880`040c36fe : fffffa80`04e04480 fffffa80`04e045d0 00000000`00100100 fffffa80`04e04480 : dxgkrnl!DpiPdoAddPdo+0x567 fffff880`04da3610 fffff880`040bf338 : fffffa80`04e04480 00000000`00000000 fffffa80`04e045d0 00000000`00000001 : dxgkrnl!DpiPdoHandleChildConnectionChange+0xce fffff880`04da3660 fffff880`040bf089 : fffffa80`05b6e000 00000000`00000000 fffffa80`04e045d0 00000000`00000000 : dxgkrnl!DpiFdoInvalidateChildStatus+0xc4 fffff880`04da36c0 fffff880`040bbf1c : fffffa80`04e045d0 fffffa80`04e045d0 00000000`00000002 fffffa80`04e045d0 : dxgkrnl!DpiFdoInvalidateChildRelations+0x189 fffff880`04da37a0 fffff880`040bff70 : fffffa80`00000040 fffffa80`04e045d0 fffffa80`04e04480 00000000`00000000 : dxgkrnl!DpiFdoCreateRelatedObjects+0x48 fffff880`04da37d0 fffff880`040c033d : 00000000`00000000 fffffa80`04e045d0 fffff880`04da3c00 00000000`00000000 : dxgkrnl!DpiFdoStartAdapter+0x6b8 fffff880`04da3a20 fffff880`040b8503 : 000007fe`00000000 fffff8a0`01ca84d0 fffff880`04da3ca0 00000000`00000000 : dxgkrnl!DpiFdoStartAdapterThread+0x121 fffff880`04da3a80 fffff880`0187625a : 00000000`000001b4 fffff880`01873510 00000000`00000000 00000000`000007ff : dxgkrnl!DpiSessionCreateCallback+0x1b fffff880`04da3ab0 fffff880`01876106 : 00000000`00000000 00000000`00000044 fffffa80`04f61730 00000000`00000001 : watchdog!SMgrSessionOpen+0xc6 fffff880`04da3af0 fffff960`000154ec : fffffa80`04f61730 fffff880`04da3ca0 00000000`00000044 fffffa80`04a7dca0 : watchdog!SMgrNotifySessionChange+0x22 fffff880`04da3b30 fffff960`00015814 : fffffa80`04f61730 fffffa80`04f61730 fffffa80`04f61730 000007fe`fd0de740 : win32k!InitializeGreCSRSS+0x20 fffff880`04da3be0 fffff800`02e85993 : fffffa80`037b8060 00000000`001f0003 00000000`00000007 fffff880`04da3c01 : win32k!NtUserInitialize+0xa0 fffff880`04da3c20 000007fe`fd0733da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`002cf488 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd0733da STACK_COMMAND: kb FOLLOWUP_IP: dxgkrnl!MONITOR_MGR::_GetMonitorInstance+cb fffff880`041155b7 ff15bb9ef3ff call qword ptr [dxgkrnl!_imp_KeAcquireGuardedMutex (fffff880`0404f478)] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: dxgkrnl!MONITOR_MGR::_GetMonitorInstance+cb FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ac5509e FAILURE_BUCKET_ID: X64_0xBE_dxgkrnl!MONITOR_MGR::_GetMonitorInstance+cb BUCKET_ID: X64_0xBE_dxgkrnl!MONITOR_MGR::_GetMonitorInstance+cb Followup: MachineOwner --------- Kernel base = 0xfffff800`02e51000 PsLoadedModuleList = 0xfffff800`0308ee50 Debug session time: Sat Sep 25 07:02:19.688 2010 (GMT-4) System Uptime: 0 days 0:01:17.796 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41790, fffffa8000af68f0, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041790, The subtype of the bugcheck. Arg2: fffffa8000af68f0 Arg3: 000000000000ffff Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41790 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: WerFault.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002f34f9e to fffff80002ec1740 STACK_TEXT: fffff880`0b9df828 fffff800`02f34f9e : 00000000`0000001a 00000000`00041790 fffffa80`00af68f0 00000000`0000ffff : nt!KeBugCheckEx fffff880`0b9df830 fffff800`02ef4df9 : 00000000`00000000 000007fe`fb4affff fffffa80`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x33906 fffff880`0b9df9f0 fffff800`031da1d0 : fffffa80`068ce820 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9 fffff880`0b9dfb10 fffff800`031da5db : 00000000`00000000 000007fe`fb390000 fffffa80`00000001 fffffa80`05fb64e0 : nt!MiUnmapViewOfSection+0x1b0 fffff880`0b9dfbd0 fffff800`02ec0993 : fffffa80`068e4120 fffff880`0b9dfca0 fffffa80`04d68810 00000000`00000000 : nt!NtUnmapViewOfSection+0x5f fffff880`0b9dfc20 00000000`7763015a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0012a668 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7763015a STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+33906 fffff800`02f34f9e cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+33906 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906 BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906 Followup: MachineOwner --------- System Uptime: 0 days 0:00:31.231 Loading Kernel Symbols ............................................................... ................................................................ ................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff89fc52d83a5, 1, fffff88010b9adae, 5} Could not read faulting driver name Probably caused by : memory_corruption Followup: memory_corruption --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffff89fc52d83a5, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff88010b9adae, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000005, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c60e0 fffff89fc52d83a5 FAULTING_IP: dxgkrnl!BTL_TOPOLOGY_CONSTRUCTOR::_ANCHOR_INFO::_FindAnchorAdaptersCallback+556 fffff880`10b9adae f3ff8bc54883c4 rep dec dword ptr [rbx-3B7CB73Bh] MM_INTERNAL_CODE: 5 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x50 PROCESS_NAME: nvvsvc.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff880060f40b0 -- (.trap 0xfffff880060f40b0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000028 rbx=0000000000000000 rcx=0000000000002611 rdx=fffff88002f70000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88010b9adae rsp=fffff880060f4240 rbp=0000000000000000 r8=0000000000013088 r9=0000000000000150 r10=fffff80002e1e000 r11=000000000000079d r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc dxgkrnl!BTL_TOPOLOGY_CONSTRUCTOR::_ANCHOR_INFO::_FindAnchorAdaptersCallback+0x556: fffff880`10b9adae f3ff8bc54883c4 rep dec dword ptr [rbx-3B7CB73Bh] ds:0cd0:ffffffff`c48348c5=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002f0d8c1 to fffff80002e8e740 STACK_TEXT: fffff880`060f3f48 fffff800`02f0d8c1 : 00000000`00000050 fffff89f`c52d83a5 00000000`00000001 fffff880`060f40b0 : nt!KeBugCheckEx fffff880`060f3f50 fffff800`02e8c82e : 00000000`00000001 fffff8a0`00aa3ae0 fffff8a0`018d7800 fffffa80`00000798 : nt! ?? ::FNODOBFM::`string'+0x40e8b fffff880`060f40b0 fffff880`10b9adae : fffff8a0`fffff833 fffff8a0`00aa3ae0 fffff8a0`00b24e80 fffff8a0`06b6b1f0 : nt!KiPageFault+0x16e fffff880`060f4240 fffff880`10b9fc7b : 00000000`00000002 fffffa80`00000000 fffff880`00000000 fffff880`10af8906 : dxgkrnl!BTL_TOPOLOGY_CONSTRUCTOR::_ANCHOR_INFO::_FindAnchorAdaptersCallback+0x556 fffff880`060f4300 fffff880`10b29b5d : fffffa80`05c99000 fffffa80`04da11a8 fffffa80`05c99000 fffff880`10b9fa71 : dxgkrnl!CCD_BTL::_FillTopology+0x13cf fffff880`060f4360 fffff880`10b9a82e : fffff880`060f4440 00000000`00000002 fffff880`060f48d0 00000000`129b2731 : dxgkrnl!DXGGLOBAL::IterateAdaptersWithCallback+0x71 fffff880`060f43c0 fffff880`10b92bf6 : fffffa80`05c99000 fffff880`060f44e0 ffff0000`16a1d17b fffffa80`04da1168 : dxgkrnl!BTL_TOPOLOGY_CONSTRUCTOR::_ANCHOR_INFO::_Query+0x9a fffff880`060f4420 fffff880`10b8f41f : fffff880`060f4630 00000000`00000002 00000000`00000000 00000000`00000000 : dxgkrnl!CCD_TOPOLOGY::QueryTopologyClass+0x92 fffff880`060f44c0 fffff880`10b8f369 : fffff880`060f4630 00000000`00000002 00000000`00000000 00000000`00000000 : dxgkrnl!CCD_RECENT_TOPOLOGY_RETRIEVER::LoadByTopologySetId+0xa3 fffff880`060f4500 fffff880`10b91da7 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`10b8f494 : dxgkrnl!CCD_RECENT_TOPOLOGY_RETRIEVER::LoadByConnectedSetId+0x7d fffff880`060f4540 fffff880`10b413bf : 00000000`0000000f 00000000`0000000f 00000000`00000000 fffff880`060f4950 : dxgkrnl!CCD_TOPOLOGY::RetrievePersisted+0x333 fffff880`060f47c0 fffff880`10b42250 : fffff900`c078eb50 fffff900`c078eb50 fffff880`060f4a20 00000000`00000000 : dxgkrnl!DxgkGetPathsModality+0x337 fffff880`060f4930 fffff880`10b42338 : fffff900`c078eb50 fffff880`060f4bb0 00000000`c0000023 fffff880`060f4c38 : dxgkrnl!GetRequestedPathsModality+0xdc fffff880`060f49c0 fffff960`0028dbc6 : 00000000`79737355 fffff880`060f4ae8 00000000`00000001 00000000`00000002 : dxgkrnl!DxgkQueryDisplayConfig+0x90 fffff880`060f4a20 fffff960`001b0d37 : 00000000`ffffc84a fffff880`060f4bb0 00000000`00000004 fffff800`02e9a772 : win32k!DrvQueryDisplayConfig+0x132 fffff880`060f4ab0 fffff800`02e8d993 : 00000000`00000001 fffffa80`05926060 00000000`01165290 00000000`017c4ba8 : win32k!NtUserQueryDisplayConfig+0x293 fffff880`060f4bb0 00000000`76b5729a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`017c4b88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76b5729a STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !dxgkrnl fffff88010b9ada7 - dxgkrnl!BTL_TOPOLOGY_CONSTRUCTOR::_ANCHOR_INFO::_FindAnchorAdaptersCallback+54f [ 8b:83 ] 1 error : !dxgkrnl (fffff88010b9ada7) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT Followup: memory_corruption --------- BCCodes: 3b, 1a, 0x50, 1000007e
1. Update these drivers:
Rt64win7.sys Fri Nov 27 11:45:07 2009
Realtek 8101E/8168/8169 Net
http://www.realtek.com.tw/DOWNLOADS/work
jraid.sys Thu Oct 29 10:14:20 2009
JMicron RAID
Update this one if there's a more recent version
Driver
2. If newer drivers don't fix it, uninstall AVG and replace it with MSE
3. There is a reference to memorry_corruption, run memtest overnight: Memtest86+ - Advanced Memory Diagnostic Tool
4. If you get more crash dumps, attach them.
092510-27019-01.dmp
SYSTEM_SERVICE_EXCEPTION (3b)
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
PROCESS_NAME: AVGIDSAgent.ex
Stack: nt!
FAILURE_BUCKET_ID: X64_0x3B_nt!CmpKcbCacheLookup+1dd
092510-24679-01.dmp
Probably caused by : dxgkrnl.sys ( dxgkrnl!MONITOR_MGR::_GetMonitorInstance+cb )
ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
PROCESS_NAME: csrss.exe
Stack: nt!, win32k!, dxgkrnl!, nt! ?? ::FNODOBFM::`string'+0x4237e
FAILURE_BUCKET_ID: X64_0xBE_dxgkrnl MONITOR_MGR::_GetMonitorInstance+cb
092510-24039-01.dmp
SYSTEM_SERVICE_EXCEPTION (3b)
Probably caused by : ntkrnlmp.exe ( nt!ObpLookupDirectoryEntry+16a )
PROCESS_NAME: svchost.exe
Stack: nt!
FAILURE_BUCKET_ID: X64_0x3B_nt!ObpLookupDirectoryEntry+16a
092510-23774-01.dmp
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
MEMORY_MANAGEMENT (1a)
PROCESS_NAME: WerFault.exe
Stack: nt!, nt! ?? ::FNODOBFM::`string'+0x33906
BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906
092410-25084-01.dmp
Probably caused by : memory_corruption
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced
PROCESS_NAME: nvvsvc.exe
Stack: nt!, win32k!, dxgkrnl!, nt! ?? ::FNODOBFM::`string'+0x40e8b
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
092410-20826-01.dmp
MEMORY_MANAGEMENT (1a)
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )
PROCESS_NAME: System
Stack: nt!, fltmgr!, ntfs!, nt!MmAccessFault, nt! ?? ::FNODOBFM::`string'+0x42ba5
FAILURE_BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5
092310-25116-01.dmp
Probably caused by : memory_corruption
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
PROCESS_NAME: System
Stack: nt!, HTTP!
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
092310-21621-01.dmp
Probably caused by : memory_corruption
PAGE_FAULT_IN_NONPAGED_AREA (50)
PROCESS_NAME: nvvsvc.exe
Stack: nt!, dxgkrnl!, nt! ?? ::FNODOBFM::`string'+0x40e8b
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
Your cirrent drivers:
1. Update these drivers:
Rt64win7.sys Fri Nov 27 11:45:07 2009
Realtek 8101E/8168/8169 Net
http://www.realtek.com.tw/DOWNLOADS/work
jraid.sys Thu Oct 29 10:14:20 2009
JMicron RAID
Update this one if there's a more recent version
Driver
2. If newer drivers don't fix it, uninstall AVG and replace it with MSE
3. There is a reference to memorry_corruption, run memtest overnight: Memtest86+ - Advanced Memory Diagnostic Tool
4. If you get more crash dumps, attach them.
092510-27019-01.dmp
SYSTEM_SERVICE_EXCEPTION (3b)
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
PROCESS_NAME: AVGIDSAgent.ex
Stack: nt!
FAILURE_BUCKET_ID: X64_0x3B_nt!CmpKcbCacheLookup+1dd
092510-24679-01.dmp
Probably caused by : dxgkrnl.sys ( dxgkrnl!MONITOR_MGR::_GetMonitorInstance+cb )
ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
PROCESS_NAME: csrss.exe
Stack: nt!, win32k!, dxgkrnl!, nt! ?? ::FNODOBFM::`string'+0x4237e
FAILURE_BUCKET_ID: X64_0xBE_dxgkrnl MONITOR_MGR::_GetMonitorInstance+cb
092510-24039-01.dmp
SYSTEM_SERVICE_EXCEPTION (3b)
Probably caused by : ntkrnlmp.exe ( nt!ObpLookupDirectoryEntry+16a )
PROCESS_NAME: svchost.exe
Stack: nt!
FAILURE_BUCKET_ID: X64_0x3B_nt!ObpLookupDirectoryEntry+16a
092510-23774-01.dmp
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
MEMORY_MANAGEMENT (1a)
PROCESS_NAME: WerFault.exe
Stack: nt!, nt! ?? ::FNODOBFM::`string'+0x33906
BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906
092410-25084-01.dmp
Probably caused by : memory_corruption
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced
PROCESS_NAME: nvvsvc.exe
Stack: nt!, win32k!, dxgkrnl!, nt! ?? ::FNODOBFM::`string'+0x40e8b
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
092410-20826-01.dmp
MEMORY_MANAGEMENT (1a)
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )
PROCESS_NAME: System
Stack: nt!, fltmgr!, ntfs!, nt!MmAccessFault, nt! ?? ::FNODOBFM::`string'+0x42ba5
FAILURE_BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5
092310-25116-01.dmp
Probably caused by : memory_corruption
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
PROCESS_NAME: System
Stack: nt!, HTTP!
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
092310-21621-01.dmp
Probably caused by : memory_corruption
PAGE_FAULT_IN_NONPAGED_AREA (50)
PROCESS_NAME: nvvsvc.exe
Stack: nt!, dxgkrnl!, nt! ?? ::FNODOBFM::`string'+0x40e8b
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
Your cirrent drivers:
Code:
start end module name fffff800`00ba7000 fffff800`00bb1000 kdcom kdcom.dll Tue Jul 14 04:31:07 2009 (4A5BDFDB) fffff800`02e08000 fffff800`02e51000 hal hal.dll Tue Jul 14 04:27:36 2009 (4A5BDF08) fffff800`02e51000 fffff800`0342d000 nt ntkrnlmp.exe Sat Jun 19 07:16:41 2010 (4C1C44A9) fffff880`00c00000 fffff880`00cc0000 CI CI.dll Tue Jul 14 04:32:13 2009 (4A5BE01D) fffff880`00cd0000 fffff880`00d14000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 04:29:10 2009 (4A5BDF66) fffff880`00d14000 fffff880`00d28000 PSHED PSHED.dll Tue Jul 14 04:32:23 2009 (4A5BE027) fffff880`00d28000 fffff880`00d86000 CLFS CLFS.SYS Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`00d86000 fffff880`00da6000 jraid jraid.sys Thu Oct 29 10:14:20 2009 (4AE94EDC) fffff880`00da6000 fffff880`00dd5000 SCSIPORT SCSIPORT.SYS Tue Jul 14 03:01:04 2009 (4A5BCAC0) fffff880`00dd5000 fffff880`00def000 mountmgr mountmgr.sys Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`00def000 fffff880`00df8000 atapi atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`00e00000 fffff880`00e5c000 volmgrx volmgrx.sys Tue Jul 14 02:20:33 2009 (4A5BC141) fffff880`00e5c000 fffff880`00e63000 pciide pciide.sys Tue Jul 14 02:19:49 2009 (4A5BC115) fffff880`00e63000 fffff880`00e73000 PCIIDEX PCIIDEX.SYS Tue Jul 14 02:19:48 2009 (4A5BC114) fffff880`00e77000 fffff880`00f1b000 Wdf01000 Wdf01000.sys Tue Jul 14 02:22:07 2009 (4A5BC19F) fffff880`00f1b000 fffff880`00f2a000 WDFLDR WDFLDR.SYS Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`00f2a000 fffff880`00f81000 ACPI ACPI.sys Tue Jul 14 02:19:34 2009 (4A5BC106) fffff880`00f81000 fffff880`00f8a000 WMILIB WMILIB.SYS Tue Jul 14 02:19:51 2009 (4A5BC117) fffff880`00f8a000 fffff880`00f94000 msisadrv msisadrv.sys Tue Jul 14 02:19:26 2009 (4A5BC0FE) fffff880`00f94000 fffff880`00fc7000 pci pci.sys Tue Jul 14 02:19:51 2009 (4A5BC117) fffff880`00fc7000 fffff880`00fd4000 vdrvroot vdrvroot.sys Tue Jul 14 03:01:31 2009 (4A5BCADB) fffff880`00fd4000 fffff880`00fe9000 partmgr partmgr.sys Tue Jul 14 02:19:58 2009 (4A5BC11E) fffff880`00fe9000 fffff880`00ffe000 volmgr volmgr.sys Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`01039000 fffff880`01063000 ataport ataport.SYS Tue Jul 14 02:19:52 2009 (4A5BC118) fffff880`01063000 fffff880`0106e000 amdxata amdxata.sys Tue May 19 20:56:59 2009 (4A12F2EB) fffff880`0106e000 fffff880`010ba000 fltmgr fltmgr.sys Tue Jul 14 02:19:59 2009 (4A5BC11F) fffff880`010ba000 fffff880`010ce000 fileinfo fileinfo.sys Tue Jul 14 02:34:25 2009 (4A5BC481) fffff880`010ce000 fffff880`0112c000 msrpc msrpc.sys Tue Jul 14 02:21:32 2009 (4A5BC17C) fffff880`0112c000 fffff880`0119f000 cng cng.sys Tue Jul 14 02:49:40 2009 (4A5BC814) fffff880`0119f000 fffff880`011eb000 volsnap volsnap.sys Tue Jul 14 02:20:08 2009 (4A5BC128) fffff880`01200000 fffff880`0121e000 tdx tdx.sys Tue Jul 14 02:21:15 2009 (4A5BC16B) fffff880`01225000 fffff880`013c8000 Ntfs Ntfs.sys Tue Jul 14 02:20:47 2009 (4A5BC14F) fffff880`013c8000 fffff880`013e2000 ksecdd ksecdd.sys Tue Jul 14 02:20:54 2009 (4A5BC156) fffff880`013e2000 fffff880`013f3000 pcw pcw.sys Tue Jul 14 02:19:27 2009 (4A5BC0FF) fffff880`013f3000 fffff880`013fd000 Fs_Rec Fs_Rec.sys Tue Jul 14 02:19:45 2009 (4A5BC111) fffff880`01400000 fffff880`01460000 NETIO NETIO.SYS Tue Jul 14 02:21:46 2009 (4A5BC18A) fffff880`01460000 fffff880`0148b000 ksecpkg ksecpkg.sys Fri Dec 11 08:03:32 2009 (4B21E0B4) fffff880`0148b000 fffff880`0149b000 vmstorfl vmstorfl.sys Tue Jul 14 02:42:54 2009 (4A5BC67E) fffff880`0149b000 fffff880`014a3000 spldr spldr.sys Mon May 11 19:56:27 2009 (4A0858BB) fffff880`014b6000 fffff880`015a8000 ndis ndis.sys Tue Jul 14 02:21:40 2009 (4A5BC184) fffff880`015a8000 fffff880`015f2000 fwpkclnt fwpkclnt.sys Tue Jul 14 02:21:08 2009 (4A5BC164) fffff880`01603000 fffff880`01800000 tcpip tcpip.sys Mon Jun 14 06:39:04 2010 (4C15A458) fffff880`0181c000 fffff880`01846000 cdrom cdrom.sys Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`01846000 fffff880`0184f000 Null Null.SYS Tue Jul 14 02:19:37 2009 (4A5BC109) fffff880`0184f000 fffff880`01856000 Beep Beep.SYS Tue Jul 14 03:00:13 2009 (4A5BCA8D) fffff880`01856000 fffff880`01864000 vga vga.sys Tue Jul 14 02:38:47 2009 (4A5BC587) fffff880`01864000 fffff880`01889000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 02:38:51 2009 (4A5BC58B) fffff880`01889000 fffff880`01899000 watchdog watchdog.sys Tue Jul 14 02:37:35 2009 (4A5BC53F) fffff880`01899000 fffff880`018a2000 RDPCDD RDPCDD.sys Tue Jul 14 03:16:34 2009 (4A5BCE62) fffff880`018a2000 fffff880`018ab000 rdpencdd rdpencdd.sys Tue Jul 14 03:16:34 2009 (4A5BCE62) fffff880`018ab000 fffff880`018b4000 rdprefmp rdprefmp.sys Tue Jul 14 03:16:35 2009 (4A5BCE63) fffff880`018b4000 fffff880`018bf000 Msfs Msfs.SYS Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`018bf000 fffff880`018d0000 Npfs Npfs.SYS Tue Jul 14 02:19:48 2009 (4A5BC114) fffff880`018d0000 fffff880`018db000 avgfwd6a avgfwd6a.sys Wed Oct 07 01:04:57 2009 (4ACBBF09) fffff880`018db000 fffff880`018e8000 TDI TDI.SYS Tue Jul 14 02:21:18 2009 (4A5BC16E) fffff880`018f7000 fffff880`01931000 rdyboost rdyboost.sys Tue Jul 14 02:34:34 2009 (4A5BC48A) fffff880`01931000 fffff880`01943000 mup mup.sys Tue Jul 14 02:23:45 2009 (4A5BC201) fffff880`01943000 fffff880`0194c000 hwpolicy hwpolicy.sys Tue Jul 14 02:19:22 2009 (4A5BC0FA) fffff880`0194c000 fffff880`01986000 fvevol fvevol.sys Tue Jul 14 02:22:15 2009 (4A5BC1A7) fffff880`01986000 fffff880`0199c000 disk disk.sys Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`0199c000 fffff880`019cc000 CLASSPNP CLASSPNP.SYS Tue Jul 14 02:19:58 2009 (4A5BC11E) fffff880`019cc000 fffff880`019d80c0 avgrkx64 avgrkx64.sys Thu Feb 11 05:52:44 2010 (4B737F0C) fffff880`019d9000 fffff880`019e3000 AVGIDSwa AVGIDSwa.sys Wed May 12 03:50:03 2010 (4BE9FB3B) fffff880`02c29000 fffff880`02c7a000 avgtdia avgtdia.sys Fri Jun 04 00:09:57 2010 (4C081A25) fffff880`02c7a000 fffff880`02cbf000 netbt netbt.sys Tue Jul 14 02:21:28 2009 (4A5BC178) fffff880`02cbf000 fffff880`02d49000 afd afd.sys Tue Jul 14 02:21:40 2009 (4A5BC184) fffff880`02d49000 fffff880`02d52000 wfplwf wfplwf.sys Tue Jul 14 03:09:26 2009 (4A5BCCB6) fffff880`02d52000 fffff880`02d78000 pacer pacer.sys Tue Jul 14 03:09:41 2009 (4A5BCCC5) fffff880`02d78000 fffff880`02d87000 netbios netbios.sys Tue Jul 14 03:09:26 2009 (4A5BCCB6) fffff880`02d87000 fffff880`02da4000 serial serial.sys Tue Jul 14 03:00:40 2009 (4A5BCAA8) fffff880`02da4000 fffff880`02dbf000 wanarp wanarp.sys Tue Jul 14 03:10:21 2009 (4A5BCCED) fffff880`02dbf000 fffff880`02dd3000 termdd termdd.sys Tue Jul 14 03:16:36 2009 (4A5BCE64) fffff880`03e00000 fffff880`03e47000 avgldx64 avgldx64.sys Fri Jun 04 00:06:48 2010 (4C081968) fffff880`03e47000 fffff880`03e4f000 AppleCharger AppleCharger.sys Mon Mar 01 04:26:17 2010 (4B8B25C9) fffff880`03e4f000 fffff880`03e75000 tunnel tunnel.sys Tue Jul 14 03:09:37 2009 (4A5BCCC1) fffff880`03e75000 fffff880`03e8b000 intelppm intelppm.sys Tue Jul 14 02:19:25 2009 (4A5BC0FD) fffff880`03e8b000 fffff880`03eaf000 HDAudBus HDAudBus.sys Tue Jul 14 03:06:13 2009 (4A5BCBF5) fffff880`03ec5000 fffff880`03f16000 rdbss rdbss.sys Tue Jul 14 02:24:09 2009 (4A5BC219) fffff880`03f16000 fffff880`03f22000 nsiproxy nsiproxy.sys Tue Jul 14 02:21:02 2009 (4A5BC15E) fffff880`03f22000 fffff880`03f2d000 mssmbios mssmbios.sys Tue Jul 14 02:31:10 2009 (4A5BC3BE) fffff880`03f2d000 fffff880`03f3c000 discache discache.sys Tue Jul 14 02:37:18 2009 (4A5BC52E) fffff880`03f3c000 fffff880`03fbf000 csc csc.sys Tue Jul 14 02:24:26 2009 (4A5BC22A) fffff880`03fbf000 fffff880`03fdd000 dfsc dfsc.sys Tue Jul 14 02:23:44 2009 (4A5BC200) fffff880`03fdd000 fffff880`03fee000 blbdrive blbdrive.sys Tue Jul 14 02:35:59 2009 (4A5BC4DF) fffff880`03fee000 fffff880`03ff5080 avgmfx64 avgmfx64.sys Mon Apr 26 00:06:15 2010 (4BD4AEC7) fffff880`04000000 fffff880`0401b000 raspppoe raspppoe.sys Tue Jul 14 03:10:17 2009 (4A5BCCE9) fffff880`0401b000 fffff880`0403c000 raspptp raspptp.sys Tue Jul 14 03:10:18 2009 (4A5BCCEA) fffff880`0403c000 fffff880`04056000 rassstp rassstp.sys Tue Jul 14 03:10:25 2009 (4A5BCCF1) fffff880`04056000 fffff880`04061000 rdpbus rdpbus.sys Tue Jul 14 03:17:46 2009 (4A5BCEAA) fffff880`04061000 fffff880`04070000 kbdclass kbdclass.sys Tue Jul 14 02:19:50 2009 (4A5BC116) fffff880`04070000 fffff880`0407f000 mouclass mouclass.sys Tue Jul 14 02:19:50 2009 (4A5BC116) fffff880`0407f000 fffff880`04080480 swenum swenum.sys Tue Jul 14 03:00:18 2009 (4A5BCA92) fffff880`0409e000 fffff880`040f4000 USBPORT USBPORT.SYS Tue Jul 14 03:06:31 2009 (4A5BCC07) fffff880`040f4000 fffff880`04105000 usbehci usbehci.sys Tue Jul 14 03:06:30 2009 (4A5BCC06) fffff880`04105000 fffff880`04151000 Rt64win7 Rt64win7.sys Fri Nov 27 11:45:07 2009 (4B0F9FA3) fffff880`04151000 fffff880`0415d000 serenum serenum.sys Tue Jul 14 03:00:33 2009 (4A5BCAA1) fffff880`0415d000 fffff880`0417a000 parport parport.sys Tue Jul 14 03:00:40 2009 (4A5BCAA8) fffff880`0417a000 fffff880`0418a000 CompositeBus CompositeBus.sys Tue Jul 14 03:00:33 2009 (4A5BCAA1) fffff880`0418a000 fffff880`041a0000 AgileVpn AgileVpn.sys Tue Jul 14 03:10:24 2009 (4A5BCCF0) fffff880`041a0000 fffff880`041c4000 rasl2tp rasl2tp.sys Tue Jul 14 03:10:11 2009 (4A5BCCE3) fffff880`041c4000 fffff880`041d0000 ndistapi ndistapi.sys Tue Jul 14 03:10:00 2009 (4A5BCCD8) fffff880`041d0000 fffff880`041ff000 ndiswan ndiswan.sys Tue Jul 14 03:10:11 2009 (4A5BCCE3) fffff880`04299000 fffff880`042dc000 ks ks.sys Tue Jul 14 03:00:31 2009 (4A5BCA9F) fffff880`042dc000 fffff880`042ee000 umbus umbus.sys Tue Jul 14 03:06:56 2009 (4A5BCC20) fffff880`042ee000 fffff880`04348000 usbhub usbhub.sys Tue Jul 14 03:07:09 2009 (4A5BCC2D) fffff880`04348000 fffff880`0435d000 NDProxy NDProxy.SYS Tue Jul 14 03:10:05 2009 (4A5BCCDD) fffff880`0435d000 fffff880`04380000 nvhda64v nvhda64v.sys Tue Jun 22 01:07:25 2010 (4C1FE29D) fffff880`04380000 fffff880`043bd000 portcls portcls.sys Tue Jul 14 03:06:27 2009 (4A5BCC03) fffff880`043bd000 fffff880`043df000 drmk drmk.sys Tue Jul 14 04:01:25 2009 (4A5BD8E5) fffff880`043df000 fffff880`043e4200 ksthunk ksthunk.sys Tue Jul 14 03:00:19 2009 (4A5BCA93) fffff880`05800000 fffff880`0582d000 AVGIDSDriver AVGIDSDriver.sys Wed May 12 03:49:44 2010 (4BE9FB28) fffff880`058bb000 fffff880`05adce80 RTKVHD64 RTKVHD64.sys Tue Jan 19 12:42:09 2010 (4B558C81) fffff880`05add000 fffff880`05aeb000 crashdmp crashdmp.sys Tue Jul 14 03:01:01 2009 (4A5BCABD) fffff880`05aeb000 fffff880`05af7000 dump_dumpata dump_dumpata.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`05af7000 fffff880`05b00000 dump_atapi dump_atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`05b00000 fffff880`05b13000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:21:51 2009 (4A5BC18F) fffff880`05b13000 fffff880`05b1f000 Dxapi Dxapi.sys Tue Jul 14 02:38:28 2009 (4A5BC574) fffff880`05b1f000 fffff880`05b3c000 usbccgp usbccgp.sys Tue Jul 14 03:06:45 2009 (4A5BCC15) fffff880`05b3c000 fffff880`05b3df00 USBD USBD.SYS Tue Jul 14 03:06:23 2009 (4A5BCBFF) fffff880`05b3e000 fffff880`05b4c000 hidusb hidusb.sys Tue Jul 14 03:06:22 2009 (4A5BCBFE) fffff880`05b4c000 fffff880`05b65000 HIDCLASS HIDCLASS.SYS Tue Jul 14 03:06:21 2009 (4A5BCBFD) fffff880`05b65000 fffff880`05b6d080 HIDPARSE HIDPARSE.SYS Tue Jul 14 03:06:17 2009 (4A5BCBF9) fffff880`05b6e000 fffff880`05b7c000 kbdhid kbdhid.sys Tue Jul 14 03:00:20 2009 (4A5BCA94) fffff880`05b7c000 fffff880`05b89000 mouhid mouhid.sys Tue Jul 14 03:00:20 2009 (4A5BCA94) fffff880`05b89000 fffff880`05b97000 monitor monitor.sys Tue Jul 14 02:38:52 2009 (4A5BC58C) fffff880`05b97000 fffff880`05bba000 luafv luafv.sys Tue Jul 14 02:26:13 2009 (4A5BC295) fffff880`05bba000 fffff880`05bcf000 lltdio lltdio.sys Tue Jul 14 03:08:50 2009 (4A5BCC92) fffff880`05bcf000 fffff880`05be7000 rspndr rspndr.sys Tue Jul 14 03:08:50 2009 (4A5BCC92) fffff880`05be7000 fffff880`05bf3000 AVGIDSFilter AVGIDSFilter.sys Wed May 12 03:48:52 2010 (4BE9FAF4) fffff880`05e15000 fffff880`05edd000 HTTP HTTP.sys Tue Jul 14 02:22:16 2009 (4A5BC1A8) fffff880`05edd000 fffff880`05efb000 bowser bowser.sys Tue Jul 14 02:23:50 2009 (4A5BC206) fffff880`05efb000 fffff880`05f13000 mpsdrv mpsdrv.sys Tue Jul 14 03:08:25 2009 (4A5BCC79) fffff880`05f13000 fffff880`05f40000 mrxsmb mrxsmb.sys Sat Feb 27 09:52:19 2010 (4B88CF33) fffff880`05f40000 fffff880`05f8e000 mrxsmb10 mrxsmb10.sys Sat Feb 27 09:52:28 2010 (4B88CF3C) fffff880`05f8e000 fffff880`05fb1000 mrxsmb20 mrxsmb20.sys Sat Feb 27 09:52:26 2010 (4B88CF3A) fffff880`08a29000 fffff880`08acf000 peauth peauth.sys Tue Jul 14 04:01:19 2009 (4A5BD8DF) fffff880`08acf000 fffff880`08ada000 secdrv secdrv.SYS Wed Sep 13 16:18:38 2006 (4508052E) fffff880`08ada000 fffff880`08b07000 srvnet srvnet.sys Tue Jun 22 06:20:32 2010 (4C202C00) fffff880`08b07000 fffff880`08b78000 spsys spsys.sys Mon May 11 20:20:58 2009 (4A085E7A) fffff880`08b78000 fffff880`08b8a000 tcpipreg tcpipreg.sys Tue Jul 14 03:09:49 2009 (4A5BCCCD) fffff880`0fe00000 fffff880`0fe46000 dxgmms1 dxgmms1.sys Tue Jul 14 02:38:32 2009 (4A5BC578) fffff880`0fe46000 fffff880`0fe53000 usbuhci usbuhci.sys Tue Jul 14 03:06:27 2009 (4A5BCC03) fffff880`0fe59000 fffff880`10aeae00 nvlddmkm nvlddmkm.sys Sat Jul 10 00:15:58 2010 (4C37918E) fffff880`10aeb000 fffff880`10aec180 nvBridge nvBridge.kmd Sat Jul 10 00:07:54 2010 (4C378FAA) fffff880`10aed000 fffff880`10be1000 dxgkrnl dxgkrnl.sys Fri Oct 02 04:00:14 2009 (4AC5509E) fffff960`00030000 fffff960`0033f000 win32k win32k.sys Sat Jun 19 07:31:59 2010 (4C1C483F) fffff960`004f0000 fffff960`004fa000 TSDDD TSDDD.dll Tue Jul 14 03:16:34 2009 (4A5BCE62) fffff960`00710000 fffff960`00737000 cdd cdd.dll unavailable (00000000) Unloaded modules: fffff880`019e3000 fffff880`019f1000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`019f1000 fffff880`019fd000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01800000 fffff880`01809000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01809000 fffff880`0181c000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000
1. Replace AVG with MSE
2. Run memtest.org overnight
Post back results. Attach new crash dumps.
2. Run memtest.org overnight
Post back results. Attach new crash dumps.
Cybercore and I were posting at the same time. His advice to replace AVG with MSE while troubleshooting is spot on. However, it does not look like you can stay running long enough to do that. If you can, uninstall AVG using this tool: Info > Tool (32bit) - Tool (64 bit). If you have AVG Identity Protections installed, remove it with this tool: Info > Tool. AVG is known to cause BSOD on some, not all, Win 7 systems.
All of your drivers are dated July 13, 2009 or later and should be good. There may be even later versions of some of them; but I suggest that you run the hardware tests before updating drivers.
All of your drivers are dated July 13, 2009 or later and should be good. There may be even later versions of some of them; but I suggest that you run the hardware tests before updating drivers.
I dont think i made myself clear..After the BSOD, then turning the pc off and back on my system runs fine, i can play games, surf the net for hours with no problems..so i don't know what's going on. I don't think that AVG is the problem because i had avast! before and still had the same problems.
�� Quote: Originally Posted by SmashGR 
I dont think i made myself clear..After the BSOD, then turning the pc off and back on my system runs fine, i can play games, surf the net for hours with no problems..so i don't know what's going on. I don't think that AVG is the problem because i had avast! before and still had the same problems.
It is worth doing:
1. Uninstalling AVG -> this way you'll be sure about AVG
2. Running memtest86 overnight -> this way you can see if your RAM is healthy
Both AVG and possibly faulty RAM often cause BSOD's. Especially that an AVG driver has caused one of your BSOD's, as well as memory_corruption has caused two of your other bsod's <- bugcheck 0x50.
~~~~~~~~~~~~~~~
092510-27019-01.dmp
SYSTEM_SERVICE_EXCEPTION (3b)
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
PROCESS_NAME: AVGIDSAgent.ex
Stack: nt!
FAILURE_BUCKET_ID: X64_0x3B_nt!CmpKcbCacheLookup+1dd
092410-25084-01.dmp
Probably caused by : memory_corruption
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced
PROCESS_NAME: nvvsvc.exe
Stack: nt!, win32k!, dxgkrnl!, nt! ?? ::FNODOBFM::`string'+0x40e8b
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
Ok uninstalled AVG..what other Anti-virus do you recommend?..i'm not to kean on MSE..
Microsoft Security Essentials:
http://www.microsoft.com/security_essentials/
Please do the memory test tonight.
http://www.microsoft.com/security_essentials/
Please do the memory test tonight.
Also please note you should run the memtest overnight really, just 15 min or 1 hour is not enough.
I agree with cybercore. Use MSE while you are troubleshooting. Avast runs well with Win 7 also; but stick to MSE until you get your system running smoothly. To backup what cybercore recommended, let Memtest run for at least seven passes. This will probably take sis or seven hours.
I also do not think the antivirus is the problem; but it is mentioned in one of the error codes as a possible cause. You want to eliminate all known possible causes while you are troubleshooting.
I also do not think the antivirus is the problem; but it is mentioned in one of the error codes as a possible cause. You want to eliminate all known possible causes while you are troubleshooting.
Ok will let memtest run overnight and get the results to you tomorrow...
We will be here. I should add that if errors show up you can stop the test. At that point pull all of your RAM but one stick and test that stick. If that stick passes, pull it and test the next stick.
It passed the memtest 13 times and no errors 
Passed the Video Card test too, and the CPU Test with no errors..
Passed the Video Card test too, and the CPU Test with no errors..
That is good news. It does not help us find the problem; but it does say your hardware is performing properly. I would like for you to run Memtest again-from a cold boot after your system has been off for a while. This is scenario is apparently when you get your crashes.
After you run Memtest again and if you receive no errors, I recommend that you enable Driver Verifier. The instructions are in this excellent tutorial by Jonathan King: Driver Verifier - Enable and Disable. Upload any BSOD's generated by Driver Verifier.
After you run Memtest again and if you receive no errors, I recommend that you enable Driver Verifier. The instructions are in this excellent tutorial by Jonathan King: Driver Verifier - Enable and Disable. Upload any BSOD's generated by Driver Verifier.
Ok here it goes...I left my pc off overnight, started it up this morning, went straight into memtest and from 0% it brought up 60,000 errors :S
I stopped it after that, pressed ESC so it would restart the system (like it does when BSOD shows up), turned it off by the ON/OFF button, then after 5 seconds turned it back on again, ran the memtest and no errors showed up.So i'm guessing the problem is my RAM after a cold-boot??
I stopped it after that, pressed ESC so it would restart the system (like it does when BSOD shows up), turned it off by the ON/OFF button, then after 5 seconds turned it back on again, ran the memtest and no errors showed up.So i'm guessing the problem is my RAM after a cold-boot??
There is obviously a memory issue at cold boot. It could be the RAM, a bad RAM slot, or a memory controller problem. It could even be a PSU problem. I am going to ask the hardware guys to take a look at this thread. I am not a hardware expert; but we definitely have some here. I am not sure what to do next; so I will get some help.
Test each stick individually till you find one that passes, then begin to test each slot to eliminate the possibility of bad slots on the motherboard... replace the ram that fails on good slots.. Hope this helps... 
This issue will usually end up being fixed by RMA'ing the RAM.
There are a few things we can check first.
Re-seat all the cables and power connections.
Re-seat the RAM, take it out and make sure it is firmly in place.
D/L CPUZ and post the CPU, Mainboard, Memory and SPD tabs, using the snipping tool.
For snipping tool, start button> in the search box type 'Snipping tool' >enter.
Select the area you want to copy, save to a convient place.
How to Post a Screenshot in Seven Forums
What is the BIOS version?
If you don't have you motherboard manual download it and read the BIOS voltage section.
Check the motherboard version before D/L the manual. It's on the lower left corner of your motherboard.
Gigabyte P55 US3L
We can adjust some of the RAM and NB voltages and see if this helps.
There are a few things we can check first.
Re-seat all the cables and power connections.
Re-seat the RAM, take it out and make sure it is firmly in place.
D/L CPUZ and post the CPU, Mainboard, Memory and SPD tabs, using the snipping tool.
For snipping tool, start button> in the search box type 'Snipping tool' >enter.
Select the area you want to copy, save to a convient place.
How to Post a Screenshot in Seven Forums
What is the BIOS version?
If you don't have you motherboard manual download it and read the BIOS voltage section.
Check the motherboard version before D/L the manual. It's on the lower left corner of your motherboard.
Gigabyte P55 US3L
We can adjust some of the RAM and NB voltages and see if this helps.
The last time I saw a cold boot issue like this it was a power supply problem of some sort. It seemed to be a problem with the board not getting enough power on a cold boot causing it not to boot up correctly. Good work on the trouble shooting guys.
Thank you, Tews, Dave, and Chev for the help. I appreciate it, guys.
Thanks alot guys..and i hope after all this we'll see an end to it all.
I got the Snip for ya: Attachment 100652
Didn't really understand what you wanted from the Motherboard Manual.
I got the Snip for ya: Attachment 100652
Didn't really understand what you wanted from the Motherboard Manual.
Carl i think he need's tabs: CPU (which u provided), Mainboard, Memory and SPD.
Could you snip the rest too?
Thanks
Could you snip the rest too?
Thanks
Smash, I did not get anything but this one. Well, maybe I did; but I cannot read it.
Same here, only the one CPUZ CPU tab in that zip file.
Can you try using the "Snipping Tool" you can select just the CPUZ window, it will make it easier for everyone to see?
Have a look at the tutorial on uploading pictures to the Forum, it's easy after the first time you get through it.
For snipping tool, start button> in the search box type 'Snipping tool' >enter.
Select the area you want to copy, save to a convient place.
Tutorial for uploading files to the forum, Click here > How to Post a Screenshot in Seven Forums
The info will help us with the next steps.
Have you changed RAM or NB voltages in BIOS before?
If not ,then read the section in your motherboard manual, this will help with the next steps.
Can you try using the "Snipping Tool" you can select just the CPUZ window, it will make it easier for everyone to see?
Have a look at the tutorial on uploading pictures to the Forum, it's easy after the first time you get through it.
For snipping tool, start button> in the search box type 'Snipping tool' >enter.
Select the area you want to copy, save to a convient place.
Tutorial for uploading files to the forum, Click here > How to Post a Screenshot in Seven Forums
The info will help us with the next steps.
Have you changed RAM or NB voltages in BIOS before?
If not ,then read the section in your motherboard manual, this will help with the next steps.
After re-seating RAM and all power cables last night and cold-booting it again today it came up with hundreds of errors.
Here are the snips:
CPU:
Attachment 100798
Memory:
Attachment 100799
Motherboard:
Attachment 100800
SPD w/ Memory slot 1
Attachment 100801
SPD w/ Memory slot 3
Attachment 100802
Here are the snips:
CPU:
Attachment 100798
Memory:
Attachment 100799
Motherboard:
Attachment 100800
SPD w/ Memory slot 1
Attachment 100801
SPD w/ Memory slot 3
Attachment 100802
Good information.
This type of error can be caused by:
Bad RAM or bad RAM settings
Bad motherboard slots or other problems
Bad PSU
Since returning these one by one or all at once can be time consuming, if you would like we can try to adjust some of the RAM and NB settings.
As mentioned previously, you may end up RMA'ing the RAM, but this is worth a try.
If you want to proceed, look in your BIOS and post the RAM voltage and NB voltage (which is MCH Core).
Next time you have the computer off for long enough to test the cold boot symptoms, put your RAM in slots 2 & 4, just to comfirm.
Are the DRAM timings in auto? or set manually?
Let us know if you want to continue with these adjustments.
EDIT:
There are newer BIOS updates listed on your mobo site, there is no FF listed.
Your BIOS version (from the CPUZ Mainboard tab) is FFb, this is a beta version and could be causing problems.
This is a quote from the Gigabyte website.
You might want to contact the company you got your computer from and question them if a beta BIOS from 5 months ago, and two full versions later is "Ready to go".
If your comfortable updating the BIOS and it won't void your warranty, I would update it to the current listed FH.
If your not comfortable with doing that, I would let the PC company upgrade the BIOS and fix the RAM problem.
Let us know if you want to continue, we will be here to help you.
This type of error can be caused by:
Bad RAM or bad RAM settings
Bad motherboard slots or other problems
Bad PSU
Since returning these one by one or all at once can be time consuming, if you would like we can try to adjust some of the RAM and NB settings.
As mentioned previously, you may end up RMA'ing the RAM, but this is worth a try.
If you want to proceed, look in your BIOS and post the RAM voltage and NB voltage (which is MCH Core).
Next time you have the computer off for long enough to test the cold boot symptoms, put your RAM in slots 2 & 4, just to comfirm.
Are the DRAM timings in auto? or set manually?
Let us know if you want to continue with these adjustments.
EDIT:
There are newer BIOS updates listed on your mobo site, there is no FF listed.
Your BIOS version (from the CPUZ Mainboard tab) is FFb, this is a beta version and could be causing problems.
This is a quote from the Gigabyte website.
Quote:
What is a BETA?
BETA describes a new version that is reliable yet may not include all the features of the final product. During this phase we are previewing new features and gathering customer input to insure our product provides the best experience possible.
BETA describes a new version that is reliable yet may not include all the features of the final product. During this phase we are previewing new features and gathering customer input to insure our product provides the best experience possible.
Quote:
-It is OEM version ( i Self-Built it online through a PC company that sent it to me "Ready-to-go"
If your comfortable updating the BIOS and it won't void your warranty, I would update it to the current listed FH.
If your not comfortable with doing that, I would let the PC company upgrade the BIOS and fix the RAM problem.
Let us know if you want to continue, we will be here to help you.
I don't understand what RMA'ing the RAM means.
I don't know where to go to find the RAM and NB voltage, nor do i know what MCH Core is. :P
I also don't know where to see if the DRAM timings are auto or set manually.
Please explain
Edit: Also my motherboard manual says that for 2 modules to work they need to be placed in slot 1 and 3.
I don't know where to go to find the RAM and NB voltage, nor do i know what MCH Core is. :P
I also don't know where to see if the DRAM timings are auto or set manually.
Please explain
Edit: Also my motherboard manual says that for 2 modules to work they need to be placed in slot 1 and 3.
Let's do it.
Sending it to Athens to the company i got it from will take weeks because the transportation truck drivers are on strike all over the country (Typical Greece :P )
So how do we update the BIOS the safest way??
Sending it to Athens to the company i got it from will take weeks because the transportation truck drivers are on strike all over the country (Typical Greece :P )
So how do we update the BIOS the safest way??
I have a Gigabyte mtherboard (P55-UD3) and there is a BIOS tool called QFlash to update the BIOS from a USB stick.
If your motherboard has that tool:
- Download and extract the BIOS file to the stick.
- Reboot the computer, and press the key for QFlash, OR go to the BIOS (DEL) and the key for QFlash should be listed at the bottom, press it.
- Navigate to the file on your USB drive.
- Confirm.
- Pray you don't have a power cut.
- Done!
If your motherboard has that tool:
- Download and extract the BIOS file to the stick.
- Reboot the computer, and press the key for QFlash, OR go to the BIOS (DEL) and the key for QFlash should be listed at the bottom, press it.
- Navigate to the file on your USB drive.
- Confirm.
- Pray you don't have a power cut.
- Done!
Can i use the same USB stick that memtest is on?
Or does it have to be formatted?
Or does it have to be formatted?
I would use another one. I just put mine on a USB stick with my documents and stuff.
From Gigabyte
What is Q-Flash� Q-Flash is a BIOS flash utility embedded in Flash ROM. With Q-Flash you can update the system BIOS without having to enter operating systems like MS-DOS or Windows first.
(Not all motherboards support Q-Flash�, please use @BIOS� or DOS flash utility to update BIOS if your motherboard does not have Q-Flash�.)
Features With this utility, you can access Q-Flash by either pressing <End> key during the POST or pressing the <F8> key in BIOS setup menu. No need to enter operating systems like MS-DOS or Windows first.
Caution Before using Q-Flash utility, go to GIGABYTE website to download the latest compressed BIOS update file that matches your motherboard model. Extract the file and save the new BIOS file to your floppy disk, USB flash drive, or hard drive. And be noted that the USB flash drive or hard drive must use FAT32/16/12 file system.
Warning:
Because BIOS flashing is potentially risky, if you do not encounter problems using the current version of BIOS, it is recommended that you not flash the BIOS. To flash the BIOS, do it with caution. Inadequate BIOS flashing may result in system
Quote:
What is Q-Flash� Q-Flash is a BIOS flash utility embedded in Flash ROM. With Q-Flash you can update the system BIOS without having to enter operating systems like MS-DOS or Windows first.
(Not all motherboards support Q-Flash�, please use @BIOS� or DOS flash utility to update BIOS if your motherboard does not have Q-Flash�.)
Features With this utility, you can access Q-Flash by either pressing <End> key during the POST or pressing the <F8> key in BIOS setup menu. No need to enter operating systems like MS-DOS or Windows first.
Caution Before using Q-Flash utility, go to GIGABYTE website to download the latest compressed BIOS update file that matches your motherboard model. Extract the file and save the new BIOS file to your floppy disk, USB flash drive, or hard drive. And be noted that the USB flash drive or hard drive must use FAT32/16/12 file system.
Warning:
Because BIOS flashing is potentially risky, if you do not encounter problems using the current version of BIOS, it is recommended that you not flash the BIOS. To flash the BIOS, do it with caution. Inadequate BIOS flashing may result in system
Wish me luck guys.. 
Fingers crossed!
Eyes crossed 
Guys i formatted the USB Stick that had memtest in (slow format not quick) extracted the Bios file from Gigabyte straight into the USB Stick, rebooted and opened up Q-Flash and it says "No Drive Found" :S
Any ideas?
Any ideas?
Hi
Could try the following?
Could try the following?
- "Legacy USB Storage Detect" Enabled in the Integrated Peripherals Page of the BIOS
- USB-drive to be plugged in when booting into QFlash
"USB Legacy Function" and "USB Storage Function" are enabled by default.
Plugged it when booting into Q-Flash and still says "No Drive Found"
Someone up there don't like me...
Plugged it when booting into Q-Flash and still says "No Drive Found"
Someone up there don't like me...
Hi
Could you try another USB stick?
Hopefully one that is different from the current one that you are using
Regards
Could you try another USB stick?
Hopefully one that is different from the current one that you are using
Regards
I tried another smaller USB Stick (128MB) and still says "No Drive Found"
Help? :P
Edit: I tried another USB Stick and it found it..so wish me luck..
Help? :P
Edit: I tried another USB Stick and it found it..so wish me luck..
�� Quote: Originally Posted by SmashGR I don't understand what RMA'ing the RAM means.
I don't know where to go to find the RAM and NB voltage, nor do i know what MCH Core is. :P
I also don't know where to see if the DRAM timings are auto or set manually.
Please explain
Edit: Also my motherboard manual says that for 2 modules to work they need to be placed in slot 1 and 3.
I don't know where to go to find the RAM and NB voltage, nor do i know what MCH Core is. :P
I also don't know where to see if the DRAM timings are auto or set manually.
Please explain
Edit: Also my motherboard manual says that for 2 modules to work they need to be placed in slot 1 and 3.
Return Material Authorization (RMA) means return to supplier for replacement.
The link to your motherboard in post #19, was so you can download your motherboard manual and read the section that will tell you where you can find this information.
Quote:
If you don't have you motherboard manual download it and read the BIOS voltage section.
Check the motherboard version before D/L the manual. It's on the lower left corner of your motherboard.
Gigabyte P55 US3L
Check the motherboard version before D/L the manual. It's on the lower left corner of your motherboard.
Gigabyte P55 US3L
The term used is 'Bricking' your motherboard. Because all it is good for is holding the door open, like a brick does.
Quote:
Warning:
Because BIOS flashing is potentially risky, if you do not encounter problems using the current version of BIOS, it is recommended that you not flash the BIOS. To flash the BIOS, do it with caution. Inadequate BIOS flashing may result in system malfunction.
Because BIOS flashing is potentially risky, if you do not encounter problems using the current version of BIOS, it is recommended that you not flash the BIOS. To flash the BIOS, do it with caution. Inadequate BIOS flashing may result in system malfunction.
If your area is prone to power outages, get or borrow a UPS - uninterruptible power supply.
From the Gigabyte Forum website:
Click here >How Do I Update My BIOS?
Quote:
Take a USB pendrive and make sure it is formatted with a FAT32 file system.
Read the info on this site before you start.
Couldn't wait for your responce Dave, sorry about that but it just started to rain and we have alot of powercuts in my area so i had to do it asap.
The results were: BIOS Update passed! (or something like that)
I checked my BIOS version now and it says "FH"
I am posting from my newly BIOS-Updated PC so i think i can still use a brick to hold my door open ^^
I am gonna leave it off for 3 - 4 hours and cold-boot it with my RAM's in slots 2 and 4 but i need a confirmation from you to do so.
I await a reply
Regards
The results were: BIOS Update passed! (or something like that)
I checked my BIOS version now and it says "FH"
I am posting from my newly BIOS-Updated PC so i think i can still use a brick to hold my door open ^^
I am gonna leave it off for 3 - 4 hours and cold-boot it with my RAM's in slots 2 and 4 but i need a confirmation from you to do so.
I await a reply
Regards
Glad to hear it.
If you weren't nervous when you did it, you should have been.
Download your motherboard manual from the link above, it will help you to find the information we will need to continue.
If you weren't nervous when you did it, you should have been.
Download your motherboard manual from the link above, it will help you to find the information we will need to continue.
I love to take risks ^^
I have my motherboard manual. (not electronic)
What next?
I have my motherboard manual. (not electronic)
What next?
From the manual D/L'ed from Gigabyte, go to page 33 and start reading about your BIOS.
Voltages are on page 37 & 38.
RAM timings starts on page 41. >>>>> Standard Timing Control
Look in your BIOS and post the RAM voltage and NB voltage (which is QPI/VTT ).
Check if the RAM timings are still set to "Auto".
Let us know the settings.
Voltages are on page 37 & 38.
RAM timings starts on page 41. >>>>> Standard Timing Control
Look in your BIOS and post the RAM voltage and NB voltage (which is QPI/VTT ).
Check if the RAM timings are still set to "Auto".
Let us know the settings.
Dave just to let you know i placed my RAM in slots 2 and 4 and i could hear the Harddrive working and everything but nothing came up on the screen.
Changing them back over and getting you the settings..
Stay with me for 5 minutes
Changing them back over and getting you the settings..
Stay with me for 5 minutes
Oke so here it goes:
>>>MCH/ICH
PCH Core 1.050V [Auto]
CPU PLL 1.800V [Auto]
>>>DRAM
DRAM Voltage 1.500V [Auto]
DRAM Termination 0.750V [Auto]
Then we got:
DRAM Timing Selectable (SPD) [Auto]
Profile DDR Voltage 1.5V
Profile QPI Voltage 1.1V
x Channel Interleaving 6 Auto
x Rank Interleaving 4 Auto
Here are the setting..i hope they are the right ones..
Regards
Edit:
I just got another 3 BSOD's.
-1 while opening Bittorrent.
-1 while opening Firefox.
-and 1 during windows boot :S
Here is the report: Attachment 100870
P.S I think the other 6 from the start of the thread are still in there so ignore them.
Look at the latest 3.
>>>MCH/ICH
PCH Core 1.050V [Auto]
CPU PLL 1.800V [Auto]
>>>DRAM
DRAM Voltage 1.500V [Auto]
DRAM Termination 0.750V [Auto]
Then we got:
DRAM Timing Selectable (SPD) [Auto]
Profile DDR Voltage 1.5V
Profile QPI Voltage 1.1V
x Channel Interleaving 6 Auto
x Rank Interleaving 4 Auto
Here are the setting..i hope they are the right ones..
Regards
Edit:
I just got another 3 BSOD's.
-1 while opening Bittorrent.
-1 while opening Firefox.
-and 1 during windows boot :S
Here is the report: Attachment 100870
P.S I think the other 6 from the start of the thread are still in there so ignore them.
Look at the latest 3.
Your right your mobo manual says the RAM has to be in slots 1 & 3.
Set the first four RAM timings manually to 9-9-9-24 and your Command Rate (CMD) to 2, leave the rest on Auto.
The QPI/VTT is the memory controller voltage, change this to 1.14v.
DRAM Voltage to 1.55v.
Check for stability, at the next cold boot.
Set the first four RAM timings manually to 9-9-9-24 and your Command Rate (CMD) to 2, leave the rest on Auto.
The QPI/VTT is the memory controller voltage, change this to 1.14v.
DRAM Voltage to 1.55v.
Check for stability, at the next cold boot.
Oke
The RAM timings were already 9-9-9-24 so i changed CMD to 2 in both channels (Although it still says 1 under Timing and 2 under Control)
I Set QPI/Vtt Voltage to 1.150V (Didn't have 1.140V)
I Set DRAM Voltage to 1.560V (Didn't have 1.550V)
Will check cold boot tomorrow morning.
The RAM timings were already 9-9-9-24 so i changed CMD to 2 in both channels (Although it still says 1 under Timing and 2 under Control)
I Set QPI/Vtt Voltage to 1.150V (Didn't have 1.140V)
I Set DRAM Voltage to 1.560V (Didn't have 1.550V)
Will check cold boot tomorrow morning.
Cold booted 5 minutes ago and got loads of errors again on memtest. -.-
Do we have any other options other than to send it back to the Company?
Because to be really honest, i would rather cold-boot it into a BSOD (for the rest of my life
) turn it off then have it be alright.
Edit: Just got a new BSOD while opening World of Warcraft saying: PAGE_FAULT_IN_NON_PAGED_AREA
Attachment 100983
Do we have any other options other than to send it back to the Company?
Because to be really honest, i would rather cold-boot it into a BSOD (for the rest of my life
) turn it off then have it be alright.Edit: Just got a new BSOD while opening World of Warcraft saying: PAGE_FAULT_IN_NON_PAGED_AREA
Attachment 100983
Change the QPI/VTT to 1.20v.
Your max is 1.21v, I wouldn't recommend going over 1.20v.
DRAM Voltage to 1.60v.
Max is 1.65v.
You must maintain a max of 0.50v difference between QPI/VTT and DRAM or risk damaging the CPU, according to Intel specs.
Check for stability, at the next cold boot.
If it still crashes try the QPI/VTT at 1.20v and DRAM at 1.65v
Check for stability, at the next cold boot.
If this doesn't work then you should RMA the RAM, if it's faulty and gets errors it might fail completely at some point.
New RAM will likely stop the blue screens during your games.
If there is no improvement, return QPI/VTT to 1.10v and DRAM to 1.50v.
Let us know the results.
Your max is 1.21v, I wouldn't recommend going over 1.20v.
DRAM Voltage to 1.60v.
Max is 1.65v.
You must maintain a max of 0.50v difference between QPI/VTT and DRAM or risk damaging the CPU, according to Intel specs.
Check for stability, at the next cold boot.
If it still crashes try the QPI/VTT at 1.20v and DRAM at 1.65v
Check for stability, at the next cold boot.
If this doesn't work then you should RMA the RAM, if it's faulty and gets errors it might fail completely at some point.
New RAM will likely stop the blue screens during your games.
If there is no improvement, return QPI/VTT to 1.10v and DRAM to 1.50v.
Let us know the results.
Entering the BIOS brought up a message in a red frame saying that system boot failed because of overclocking or something about voltages and was asking me to set the settings back to default..i pressed esc and set the QPI/Vtt to 1.21V (there wasn't 1.20V) and DRAM to 1.60V.
Will cold boot later on and then try DRAM with 1.65V.
Will get back to you later on.
Will cold boot later on and then try DRAM with 1.65V.
Will get back to you later on.
That's interesting, none of the voltages are past max settings, shouldn't have had that message.
Try it a see if it will boot, after it's cold.
If it won't boot, re-set to origional settings, QPI/VTT to 1.10v and DRAM to 1.50v.
I would say your next step is to RMA the RAM.
This is the most likely faulty hardware, if it turns out to be the same issues then we can trouble shoot other hardware.
Try it a see if it will boot, after it's cold.
If it won't boot, re-set to origional settings, QPI/VTT to 1.10v and DRAM to 1.50v.
I would say your next step is to RMA the RAM.
This is the most likely faulty hardware, if it turns out to be the same issues then we can trouble shoot other hardware.
Dave my system cold booted fine. without any BSOD.
Is this the end?
Edit: Spoke too soon i think...I went in the other room to celebrate, came back to a BSOD.
Then got a BSOD at startup after setting DRAM Voltage to 1.64V (i think due to unstable system)
So setting everything back to normal and when i get a chance (and after the strikes) will RMA my RAM's.
Is this the end?
Edit: Spoke too soon i think...I went in the other room to celebrate, came back to a BSOD.
Then got a BSOD at startup after setting DRAM Voltage to 1.64V (i think due to unstable system)
So setting everything back to normal and when i get a chance (and after the strikes) will RMA my RAM's.
You had my hopes up for a second, sorry to hear that it didn't help.
Even if it ran at those max settings I wouldn't want to keep it like that, best thing is to return the RAM and hopefully it will run solid and stable with the new RAM.
Let us know how it's running when you get the new RAM installed.
Even if it ran at those max settings I wouldn't want to keep it like that, best thing is to return the RAM and hopefully it will run solid and stable with the new RAM.
Let us know how it's running when you get the new RAM installed.
Thanks guys for the time being..
Will get back to you when i get them replaced.
Will get back to you when i get them replaced.
I hope the new RAM will solve the problem. Please let us know.
Your welcome, come back and let us know how the new RAM is working.
Could me running x64 have anything to do with it because i was told by the company that i havent got enough RAM for x64..or are they talking BS?
4 Gb is enough RAM to run 64 bit with no problems. Unless you are running a heavy CAD program or something similar, 4 Gb is fine.
Agree with Carl, your RAM is fine.
Minimum RAM recommended with x64 is 2GB.
I would definately stay with x64.
Unless your running 10-15 programs at the same time, heavy graphics or drawing programs like CAD, your RAM is just fine.
So, sounds like BS to me.
Minimum RAM recommended with x64 is 2GB.
I would definately stay with x64.
Unless your running 10-15 programs at the same time, heavy graphics or drawing programs like CAD, your RAM is just fine.
So, sounds like BS to me.
Didn't get time to send off my RAM..
When i turn my pc on i just wait for blue screen..then turn it off, then back on again and its fine.
But could this damage my RAM after time?
When i turn my pc on i just wait for blue screen..then turn it off, then back on again and its fine.
But could this damage my RAM after time?
It will probably not damage your RAM. It is the same as rebooting as far as your RAM is concerned.
That won't damage your RAM any more than it is now.
Cold boot BSoDs are usually caused by bad RAM, sometimes fixed by adjusting the settings, you adjusted the settings to max and still get BSoDs.
If left as is, it will normally get worse.
You should RMA the RAM.
Cold boot BSoDs are usually caused by bad RAM, sometimes fixed by adjusting the settings, you adjusted the settings to max and still get BSoDs.
If left as is, it will normally get worse.
You should RMA the RAM.
Không có nhận xét nào:
Đăng nhận xét