Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Testing GPU

26 Jan 2012   #1
a1rifle

Win7 Ultimate x86
 
 
BSOD Testing GPU

Hello everyone!
I just got a brand new PC and I had been overcloking it for 3 days.
I had no problems with the processor(i7 2600k). But not the same for the video card(asus gtx 560). I viewed some overclocking tutorials using the stock cooler and I was pretty confident in my overclocking ability. Initially, I used the buil-in overclock tool from Asus, the Asus SmartDoctor. I had played a bit with the frequencies, and when it came to memory overlock, BSoD appeared. I, then, installed MSI Afterburner, but then unistalled it because the BSoDs kept going. All the testes were made with FurMark 1.9.2. The temperature of the GPU never excedeed 70 degreed Celsius. I am waiting for some expanations. Thank you

UPDATE: New results. BSoD during driver verifier
minidump.rar


My System SpecsSystem Spec
.
26 Jan 2012   #2
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [H:\BSODDmpFiles\a1rifle\Windows7_Vista_jcgriff2\012612-27846-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`03050000 PsLoadedModuleList = 0xfffff800`0328de70 Debug session time: Thu Jan 26 08:24:15.426 2012 (UTC - 7:00) System Uptime: 0 days 0:00:47.378 Loading Kernel Symbols ............................................................... ................................................................ ............................................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffffa80266fb668, 0, fffff8000335e17f, 2} Could not read faulting driver name Probably caused by : ntkrnlmp.exe ( nt!PnpDeviceObjectFromDeviceInstance+6b ) Followup: MachineOwner --------- 6: 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: fffffa80266fb668, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff8000335e17f, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f80e0 fffffa80266fb668 FAULTING_IP: nt!PnpDeviceObjectFromDeviceInstance+6b fffff800`0335e17f 488b4828 mov rcx,qword ptr [rax+28h] MM_INTERNAL_CODE: 2 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff880064f6930 -- (.trap 0xfffff880064f6930) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa80266fb640 rbx=0000000000000000 rcx=fffff8a002e094e0 rdx=0000000000000030 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8000335e17f rsp=fffff880064f6ac0 rbp=00000000015eb8e0 r8=0000000000000030 r9=000001e0038e8110 r10=fffff8a002e09502 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!PnpDeviceObjectFromDeviceInstance+0x6b: fffff800`0335e17f 488b4828 mov rcx,qword ptr [rax+28h] ds:fffffa80`266fb668=???????????????? Resetting default scope LOCK_ADDRESS: fffff800032c4420 -- (!locks fffff800032c4420) Resource @ nt!PiEngineLock (0xfffff800032c4420) Available WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted. WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted. 1 total locks PNP_TRIAGE: Lock address : 0xfffff800032c4420 Thread Count : 0 Thread address: 0x0000000000000000 Thread wait : 0x0 LAST_CONTROL_TRANSFER: from fffff8000313f7d2 to fffff800030c05c0 STACK_TEXT: fffff880`064f67c8 fffff800`0313f7d2 : 00000000`00000050 fffffa80`266fb668 00000000`00000000 fffff880`064f6930 : nt!KeBugCheckEx fffff880`064f67d0 fffff800`030be6ae : 00000000`00000000 fffffa80`066fb4e0 fffff800`0324ea00 00000000`00000ac4 : nt! ?? ::FNODOBFM::`string'+0x40d80 fffff880`064f6930 fffff800`0335e17f : 00000000`00000000 00000000`015eb8e0 00000000`00000000 00000000`00000020 : nt!KiPageFault+0x16e fffff880`064f6ac0 fffff800`0335e4ce : 00000000`00000000 00000000`00000000 00000000`015eb8e0 00000000`20207050 : nt!PnpDeviceObjectFromDeviceInstance+0x6b fffff880`064f6b00 fffff800`0335e6b0 : fffff8a0`02e56730 fffff800`00000000 fffff880`064f6c01 fffff800`0358bdf0 : nt!PiControlGetSetDeviceStatus+0xee fffff880`064f6b90 fffff800`030bf813 : fffffa80`0a6e2060 00000000`0104ea50 fffff880`064f6c60 00000000`0104eab8 : nt!NtPlugPlayControl+0x100 fffff880`064f6be0 00000000`77bf070a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0104ea28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bf070a STACK_COMMAND: kb FOLLOWUP_IP: nt!PnpDeviceObjectFromDeviceInstance+6b fffff800`0335e17f 488b4828 mov rcx,qword ptr [rax+28h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!PnpDeviceObjectFromDeviceInstance+6b FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44 FAILURE_BUCKET_ID: X64_0x50_nt!PnpDeviceObjectFromDeviceInstance+6b BUCKET_ID: X64_0x50_nt!PnpDeviceObjectFromDeviceInstance+6b Followup: MachineOwner ---------
  2. Loading Dump File [H:\BSODDmpFiles\a1rifle\Windows7_Vista_jcgriff2\012612-27658-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`0305b000 PsLoadedModuleList = 0xfffff800`03298e70 Debug session time: Thu Jan 26 08:22:27.915 2012 (UTC - 7:00) System Uptime: 0 days 0:00:34.867 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {fffffa7808907b8a, 2, 0, fffff8800196f4ea} Probably caused by : NETIO.SYS ( NETIO!FsbFree+5a ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 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 kernel debugger is available get stack backtrace. Arguments: Arg1: fffffa7808907b8a, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff8800196f4ea, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033030e0 fffffa7808907b8a CURRENT_IRQL: 2 FAULTING_IP: NETIO!FsbFree+5a fffff880`0196f4ea 0fb7520a movzx edx,word ptr [rdx+0Ah] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff8000471f920 -- (.trap 0xfffff8000471f920) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000000008bb rbx=0000000000000000 rcx=fffffa800a8f0080 rdx=fffffa7808907b80 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800196f4ea rsp=fffff8000471fab0 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000000 r10=fffffa8009a9f790 r11=0000000000000002 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz ac po cy NETIO!FsbFree+0x5a: fffff880`0196f4ea 0fb7520a movzx edx,word ptr [rdx+0Ah] ds:4a00:fffffa78`08907b8a=???? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800030cab29 to fffff800030cb5c0 STACK_TEXT: fffff800`0471f7d8 fffff800`030cab29 : 00000000`0000000a fffffa78`08907b8a 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff800`0471f7e0 fffff800`030c97a0 : 00000000`00000000 00000000`00000000 fffffa80`00000122 fffffa80`00000122 : nt!KiBugCheckDispatch+0x69 fffff800`0471f920 fffff880`0196f4ea : 00000000`00000000 fffffa80`096440f0 00000000`00000001 fffffa80`0a8f0080 : nt!KiPageFault+0x260 fffff800`0471fab0 fffff880`01a3f754 : fffffa80`0a8f0080 00000000`00000000 fffffa80`07608820 00000000`00000000 : NETIO!FsbFree+0x5a fffff800`0471faf0 fffff880`01a3fc24 : fffffa80`00000000 fffffa80`09a9f390 00000000`00000000 fffffa80`0980422c : tcpip!UdpDeliverDatagrams+0x194 fffff800`0471fc80 fffff880`01a5e287 : fffffa80`08930e30 fffff800`00000000 00000000`00000002 00000000`00000000 : tcpip!UdpReceiveDatagrams+0x324 fffff800`0471fd70 fffff880`01a5e2f9 : fffff800`0471fef0 fffff880`01b6c9a0 fffff800`0471ff00 fffff880`01b6c9a0 : tcpip!IppDeliverListToProtocol+0xf7 fffff800`0471fe30 fffff880`01a5e7f0 : fffffa80`0890e000 fffff880`01b6c9a0 fffffa80`097b4f50 fffff800`0471fef0 : tcpip!IppProcessDeliverList+0x59 fffff800`0471fea0 fffff880`01a5d681 : fffffa80`07bebd48 fffffa80`0890e000 fffff880`01b6c9a0 00000000`098b0b01 : tcpip!IppReceiveHeaderBatch+0x231 fffff800`0471ff80 fffff880`01a5c0f2 : fffffa80`098b6960 00000000`00000000 fffffa80`098b0b01 fffffa80`00000001 : tcpip!IpFlcReceivePackets+0x651 fffff800`04720180 fffff880`01a7662a : fffffa80`098b0bb0 fffff800`047202b0 fffffa80`098b0bb0 00000000`00010000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2 fffff800`04720260 fffff800`030dacda : fffffa80`097b4e20 fffff800`0471b000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda fffff800`047202b0 fffff880`01a76052 : fffff880`01a76550 fffff800`047203c0 fffff800`04720402 fffff800`04720620 : nt!KeExpandKernelStackAndCalloutEx+0xda fffff800`04720390 fffff880`019390eb : fffffa80`098b2220 00000000`00000000 fffffa80`08e271a0 fffffa80`0765dc60 : tcpip!FlReceiveNetBufferListChain+0xb2 fffff800`04720400 fffff880`01902fc6 : 00000001`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb fffff800`04720470 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6 STACK_COMMAND: kb FOLLOWUP_IP: NETIO!FsbFree+5a fffff880`0196f4ea 0fb7520a movzx edx,word ptr [rdx+0Ah] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: NETIO!FsbFree+5a FOLLOWUP_NAME: MachineOwner MODULE_NAME: NETIO IMAGE_NAME: NETIO.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18a FAILURE_BUCKET_ID: X64_0xD1_NETIO!FsbFree+5a BUCKET_ID: X64_0xD1_NETIO!FsbFree+5a Followup: MachineOwner ---------
  3. Loading Dump File [H:\BSODDmpFiles\a1rifle\Windows7_Vista_jcgriff2\012612-35240-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`03015000 PsLoadedModuleList = 0xfffff800`03252e70 Debug session time: Wed Jan 25 09:42:17.869 2012 (UTC - 7:00) System Uptime: 0 days 0:04:31.821 Loading Kernel Symbols ............................................................... ................................................................ .............................................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {ffffffffca8b4814, 1, fffff8801020fb2b, 2} Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Could not read faulting driver name Probably caused by : nvlddmkm.sys ( nvlddmkm+110b2b ) Followup: MachineOwner --------- 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: ffffffffca8b4814, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff8801020fb2b, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032bd0e0 ffffffffca8b4814 FAULTING_IP: nvlddmkm+110b2b fffff880`1020fb2b 098b11488bca or dword ptr [rbx-3574B7EFh],ecx MM_INTERNAL_CODE: 2 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: System CURRENT_IRQL: 0 TRAP_FRAME: fffff88002d1e370 -- (.trap 0xfffff88002d1e370) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000000000b0 rbx=0000000000000000 rcx=fffffa800a2e8000 rdx=fffff88002d1e790 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8801020fb2b rsp=fffff88002d1e508 rbp=fffffa800a5383f0 r8=0000000000000000 r9=fffffa800a5383f0 r10=0000000000000005 r11=fffffa800a522010 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nvlddmkm+0x110b2b: fffff880`1020fb2b 098b11488bca or dword ptr [rbx-3574B7EFh],ecx ds:0001:ffffffff`ca8b4811=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800031047d2 to fffff800030855c0 STACK_TEXT: fffff880`02d1e208 fffff800`031047d2 : 00000000`00000050 ffffffff`ca8b4814 00000000`00000001 fffff880`02d1e370 : nt!KeBugCheckEx fffff880`02d1e210 fffff800`030836ae : 00000000`00000001 00000000`00000003 00000000`00000000 00000000`000007e9 : nt! ?? ::FNODOBFM::`string'+0x40d80 fffff880`02d1e370 fffff880`1020fb2b : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KiPageFault+0x16e fffff880`02d1e508 00000000`00000000 : 00000000`00000000 00000000`00000002 00000000`00000000 fffff880`02d1e790 : nvlddmkm+0x110b2b STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+110b2b fffff880`1020fb2b 098b11488bca or dword ptr [rbx-3574B7EFh],ecx SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nvlddmkm+110b2b FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4e99233b FAILURE_BUCKET_ID: X64_0x50_nvlddmkm+110b2b BUCKET_ID: X64_0x50_nvlddmkm+110b2b Followup: MachineOwner ---------
  4. Loading Dump File [H:\BSODDmpFiles\a1rifle\Windows7_Vista_jcgriff2\012512-45427-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`03000000 PsLoadedModuleList = 0xfffff800`0323de70 Debug session time: Wed Jan 25 08:11:28.606 2012 (UTC - 7:00) System Uptime: 0 days 0:03:57.558 Loading Kernel Symbols ............................................................... ................................................................ ........................................... Loading User Symbols Loading unloaded module list ................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904fb, fffff8800353f7f8, fffff8800353f060, fffff88001665725} Probably caused by : Ntfs.sys ( Ntfs!NtfsReleasePagingResource+5 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. Arguments: Arg1: 00000000001904fb Arg2: fffff8800353f7f8 Arg3: fffff8800353f060 Arg4: fffff88001665725 Debugging Details: ------------------ EXCEPTION_RECORD: fffff8800353f7f8 -- (.exr 0xfffff8800353f7f8) ExceptionAddress: fffff88001665725 (Ntfs!NtfsReleasePagingResource+0x0000000000000005) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000080000000 Attempt to read from address 0000000080000000 CONTEXT: fffff8800353f060 -- (.cxr 0xfffff8800353f060) rax=0000000000000702 rbx=fffffa800ae366f0 rcx=0000000000000000 rdx=0000000080000000 rsi=0000000000000001 rdi=fffffa800ae36738 rip=fffff88001665725 rsp=fffff8800353fa38 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000727 r10=fffff8a003fef010 r11=fffff8800353fb12 r12=0000000000000001 r13=0000000000000702 r14=fffff8a003fef3a8 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 Ntfs!NtfsReleasePagingResource+0x5: fffff880`01665725 663b02 cmp ax,word ptr [rdx] ds:002b:00000000`80000000=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT 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_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000080000000 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032a80e0 0000000080000000 FOLLOWUP_IP: Ntfs!NtfsReleasePagingResource+5 fffff880`01665725 663b02 cmp ax,word ptr [rdx] FAULTING_IP: Ntfs!NtfsReleasePagingResource+5 fffff880`01665725 663b02 cmp ax,word ptr [rdx] BUGCHECK_STR: 0x24 LAST_CONTROL_TRANSFER: from fffff8800166f3c5 to fffff88001665725 STACK_TEXT: fffff880`0353fa38 fffff880`0166f3c5 : 00000000`00000000 00000000`00000000 fffff8a0`03fef140 00000000`00000702 : Ntfs!NtfsReleasePagingResource+0x5 fffff880`0353fa40 fffff880`0165cc74 : fffffa80`0ae366f0 00000000`00000001 00000000`00000000 00000000`00000000 : Ntfs! ?? ::FNODOBFM::`string'+0x65f5 fffff880`0353fa90 fffff880`016f3f67 : fffff880`0353fbf8 fffffa80`08a97180 fffffa80`0ae366f0 00000000`00000009 : Ntfs!NtfsExtendedCompleteRequestInternal+0xd4 fffff880`0353fad0 fffff880`016cdc9f : fffffa80`0ae366f0 fffff8a0`03fef140 fffff8a0`03fef010 fffffa80`08a97180 : Ntfs!NtfsCommonClose+0x9c4 fffff880`0353fba0 fffff800`0307d7e1 : 00000000`00000000 fffff800`03369900 fffffa80`06723601 3908656e`00000002 : Ntfs!NtfsFspClose+0x15f fffff880`0353fc70 fffff800`033106fa : 21ee54a3`6d9bbfc2 fffffa80`06723680 00000000`00000080 fffffa80`066f2040 : nt!ExpWorkerThread+0x111 fffff880`0353fd00 fffff800`0304eb46 : fffff880`0336a180 fffffa80`06723680 fffff880`033750c0 c99a5ebd`9c370ee7 : nt!PspSystemThreadStartup+0x5a fffff880`0353fd40 00000000`00000000 : fffff880`03540000 fffff880`0353a000 fffff880`0353f9b0 00000000`00000000 : nt!KiStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: Ntfs!NtfsReleasePagingResource+5 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d79996d STACK_COMMAND: .cxr 0xfffff8800353f060 ; kb FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsReleasePagingResource+5 BUCKET_ID: X64_0x24_Ntfs!NtfsReleasePagingResource+5 Followup: MachineOwner ---------
  1. Possible causes are Memory problems... Graphics card memory problems... CMOS... Corrupted hard disk system files... Corrupted System Files... Missing Windows Updates... Drivers... Antivirus software...
  2. Most likely due to your Antivirus software... Could also be due to your network adapter driver being corrupted or needing updating... Missing Windows Updates...
  3. Possible causes are Memory problems... Graphics card memory problems... CMOS... Corrupted hard disk system files... Corrupted System Files... Missing Windows Updates... Drivers... Antivirus software...
  4. Possible causes are Memory problems... Corrupted hard disk system files... Drivers... corrupted SCSI or IDE Drivers...
  5. Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Drivers...

Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.
My System SpecsSystem Spec
Reply

 BSOD Testing GPU




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD when Stress Testing, MEMORY_MANAGEMENT 0x0000001a
Hello, I have recently been stress testing my system to ensure that it is 100% stable before i proceed to overclocking. I first ran P-95 a couple of times and each time i got a BSOD after about 10 minutes. I thought i fresh install of windows would fix the problem, so i tried that. No luck, i...
BSOD Help and Support
BSOD while testing CPU on Windows Index Experience
Hey, I have a problem (though I think it is minor because my system recovers quite well from it after restarting). Basically, I overclocked my CPU to 4.19 gHz and everything is running smoothly (also got a Radeon 7770 HD graphics card) so I decided to redo my WEI score and close to the end of the...
BSOD Help and Support
BSOD Torture Testing w/ Prime95 v227
I was stressing my laptop using Prime95 v227 then it just automatically restarted. I also attach my result. Would anyone please take a look at it and explain it to me? What should I do next to pass this test? Thank you so much :rolleyes:
BSOD Help and Support
BSOD during stress testing on new computer
I recently built a PC with the following Specs: MOBO:P8P67 Deluxe 3.0 1850 BIOS CPU:Intel Core i7-2600K RAM:G.SKILL Ripjaws X Series 8GB (2 x 4GB) 240-Pin SDRAM DDR3 1600 (PC3 12800) Graphics cards:Dual EVGA GeForce GTX 570 HD Superclocked 1280 MB GDDR5 with SLI Link Enabled PSU:Rosewill...
BSOD Help and Support
Before I send my mobo and amd chip in for testing, here's my BSOD !
On average about 70% of the time on boot I get a blue screen at the windows log in as you can clearly hear in the background the welcome music. I've tried all sorts of things at first suspecting my USB 7 port hub, then testing my 4 sticks of memory, then changing out my BFG video card for BFG...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 19:09.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App