New
#1
windows 7 bsod while gaming
I get the bsod while I'm playing on line.
windows 7 ultimate x64 retail
system is about 2years old
just reinstalled windows about a month ago
I get the bsod while I'm playing on line.
windows 7 ultimate x64 retail
system is about 2years old
just reinstalled windows about a month ago
Hi, Bud; and welcome to the forum. I looked at four of your dumps. All of them indicate memory corruption. Unfortunately, they do not point directly to a cause.
Error code A, IRQL_NOT_LESS_OR_EQUAL. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.
Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control.
Error code 3B (2X), SYSTEM_SERVICE_EXCEPTION. Usual causes: System service, Device driver, graphics driver, ?memory.To begin your troubleshooting, completely uninstall McAfee using this removal tool: Tool. McAfee is a know cause of problems and crashes on many Win 7 system. It was involved in at least two of your crashes. Download and install Microsoft Security Essentials in its place. I suggest that you do not reinstall McAfee.Code:Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`0304d000 PsLoadedModuleList = 0xfffff800`0328ae50 Debug session time: Thu Nov 11 10:52:37.072 2010 (GMT-5) System Uptime: 0 days 0:27:21.820 Loading Kernel Symbols ............................................................... ................................................................ ....................................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {200000000, 2, 1, fffff800030fe0a2} Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000200000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff800030fe0a2, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f50e0 0000000200000000 CURRENT_IRQL: 2 FAULTING_IP: nt!KxWaitForLockOwnerShip+12 fffff800`030fe0a2 48890a mov qword ptr [rdx],rcx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: McSvHost.exe TRAP_FRAME: fffff8800b580380 -- (.trap 0xfffff8800b580380) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000000be9d000 rbx=0000000000000000 rcx=fffff8800b5805a8 rdx=0000000200000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800030fe0a2 rsp=fffff8800b580510 rbp=fffff8800b580580 r8=fffff80003237e80 r9=0000000000000000 r10=fffff800032f7840 r11=0000058000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!KxWaitForLockOwnerShip+0x12: fffff800`030fe0a2 48890a mov qword ptr [rdx],rcx ds:0202:00000002`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800030bcca9 to fffff800030bd740 STACK_TEXT: fffff880`0b580238 fffff800`030bcca9 : 00000000`0000000a 00000002`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`0b580240 fffff800`030bb920 : fffffa80`01a5c380 fffffa80`01f9e930 fffff800`030d0dbc fffff680`00006880 : nt!KiBugCheckDispatch+0x69 fffff880`0b580380 fffff800`030fe0a2 : 00000000`00000000 00000000`00000001 fffffa80`06d4bc68 00000000`00000001 : nt!KiPageFault+0x260 fffff880`0b580510 fffff800`030d6314 : fffffa80`01f9e930 00000000`00000000 fffff880`0b580580 fffffa80`06d4bb60 : nt!KxWaitForLockOwnerShip+0x12 fffff880`0b580540 fffff800`030a7929 : 00000000`00000000 fffffa80`01f9e930 00000000`00002001 80000000`a8a31882 : nt!MiInsertPageInFreeOrZeroedList+0x4e4 fffff880`0b580640 fffff800`033ae60f : fffffa80`0be9d010 fffff800`03235e00 fffffa80`0be9d010 00000000`00002001 : nt!MiDeleteSegmentPages+0x265 fffff880`0b5806f0 fffff800`030c28b4 : 00000000`00000000 fffff800`03235e30 fffffa80`06d6a8e0 fffffa80`06d6a8e0 : nt!MiSegmentDelete+0x7b fffff880`0b580730 fffff800`03363859 : fffff800`03235e30 fffff8a0`088b5580 00000000`00000000 00000000`00000146 : nt!ObfDereferenceObject+0xd4 fffff880`0b580790 fffff800`033bf068 : fffff8a0`088b5560 00000000`00000001 fffff8a0`07d4e7d0 fffffa80`074f1f10 : nt!AlpcpSectionDestroyProcedure+0x39 fffff880`0b5807c0 fffff800`033658b0 : fffff8a0`088b5580 fffff800`03235e30 00000000`ffffffff fffff800`03235e30 : nt!AlpcpDestroyBlob+0x28 fffff880`0b5807f0 fffff800`033bf068 : fffff8a0`0803df80 fffff800`03235e30 fffff800`69566c41 fffff8a0`07d4e770 : nt!AlpcpRegionDestroyProcedure+0xd0 fffff880`0b580820 fffff800`03365c2f : 00000000`00000000 00000000`00000000 fffff8a0`00000001 fffff8a0`086c6c80 : nt!AlpcpDestroyBlob+0x28 fffff880`0b580850 fffff800`03356596 : 00000000`00000000 fffff800`03235e30 fffff8a0`086c6c80 fffff8a0`0890dd00 : nt!AlpcpViewDestroyProcedure+0x30f fffff880`0b5808f0 fffff800`03357167 : 00000000`00000000 00000000`09b565c0 00000000`40000000 fffff880`0b580a80 : nt!AlpcpCaptureViewAttributeInternal+0x196 fffff880`0b580950 fffff800`0338c413 : 00000000`00000020 fffffa80`0aa65ce0 00000000`e0000000 fffff8a0`0890dd00 : nt!AlpcpCaptureViewAttribute+0x47 fffff880`0b5809a0 fffff800`033bd1f9 : fffffa80`0aa65ce0 00000000`00000000 fffff8a0`0890dd00 fffff8a0`0890dd00 : nt!AlpcpCaptureAttributes+0x320 fffff880`0b580a00 fffff800`033beed9 : 00000000`09b56500 fffffa80`00000001 00000000`0f8bf640 00000000`04a39901 : nt!AlpcpSendMessage+0x3c7 fffff880`0b580b00 fffff800`030bc993 : fffffa80`07ed97f0 fffff880`0b580ca0 00000000`0f8bef58 0000007f`ffffffff : nt!NtAlpcSendWaitReceivePort+0xb9 fffff880`0b580bb0 00000000`773d05aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0f8bef38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773d05aa STACK_COMMAND: kb FOLLOWUP_IP: nt!KxWaitForLockOwnerShip+12 fffff800`030fe0a2 48890a mov qword ptr [rdx],rcx SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KxWaitForLockOwnerShip+12 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0xA_nt!KxWaitForLockOwnerShip+12 BUCKET_ID: X64_0xA_nt!KxWaitForLockOwnerShip+12 Followup: MachineOwner --------- Debug session time: Mon Nov 15 19:31:39.294 2010 (GMT-5) System Uptime: 0 days 0:17:28.668 Loading Kernel Symbols ............................................................... ................................................................ ...................................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff800030c30a2, fffff880047f1dd0, 0} Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 ) Followup: MachineOwner --------- 2: 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: fffff800030c30a2, Address of the exception record for the exception that caused the bugcheck Arg3: fffff880047f1dd0, 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!KxWaitForLockOwnerShip+12 fffff800`030c30a2 48890a mov qword ptr [rdx],rcx CONTEXT: fffff880047f1dd0 -- (.cxr 0xfffff880047f1dd0) rax=0000000000000008 rbx=fffffa8001146630 rcx=fffff880047f2868 rdx=1000000000000000 rsi=0000000000000001 rdi=fffff880047f2868 rip=fffff800030c30a2 rsp=fffff880047f27a0 rbp=fffff880047f2840 r8=fffff88002f64180 r9=0000000000000000 r10=fffff800032bc840 r11=0000058000000000 r12=fffffa8006c02800 r13=0000000000175000 r14=0000000000000528 r15=0000000000000000 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!KxWaitForLockOwnerShip+0x12: fffff800`030c30a2 48890a mov qword ptr [rdx],rcx ds:002b:10000000`00000000=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: McSvHost.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800030c30a2 STACK_TEXT: fffff880`047f27a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip+0x12 FOLLOWUP_IP: nt!KxWaitForLockOwnerShip+12 fffff800`030c30a2 48890a mov qword ptr [rdx],rcx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KxWaitForLockOwnerShip+12 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff880047f1dd0 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!KxWaitForLockOwnerShip+12 BUCKET_ID: X64_0x3B_nt!KxWaitForLockOwnerShip+12 Followup: MachineOwner --------- Debug session time: Mon Nov 15 19:57:31.709 2010 (GMT-5) System Uptime: 0 days 0:15:34.457 Loading Kernel Symbols ............................................................... ................................................................ ...................................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff8000303db6c, fffff880031c3fd8, fffff880031c3840} Probably caused by : cng.sys ( cng!GatherRandomKey+294 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff8000303db6c, The address that the exception occurred at Arg3: fffff880031c3fd8, Exception Record Address Arg4: fffff880031c3840, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!ExpGetLookasideInformation+8c fffff800`0303db6c 0fb742c0 movzx eax,word ptr [rdx-40h] EXCEPTION_RECORD: fffff880031c3fd8 -- (.exr 0xfffff880031c3fd8) Cannot read Exception record @ fffff880031c3fd8 CONTEXT: fffff880031c3840 -- (.cxr 0xfffff880031c3840) rax=0000000000000090 rbx=0000000000000ff4 rcx=fffff8800a846390 rdx=effff8000320b640 rsi=0000000000000000 rdi=0000000000000001 rip=fffff8000303db6c rsp=fffff880031c4210 rbp=0000000000000011 r8=fffff80003234720 r9=0000000000000000 r10=0000000000000000 r11=0000fffffffff000 r12=fffff880031c42e0 r13=0000000000000000 r14=000000000001fe90 r15=fffff880031c4840 iopl=0 nv up ei ng nz na pe cy cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010283 nt!ExpGetLookasideInformation+0x8c: fffff800`0303db6c 0fb742c0 movzx eax,word ptr [rdx-40h] ds:002b:effff800`0320b600=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: NULL_DEREFERENCE PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c70e0 0000000000000000 FOLLOWUP_IP: cng!GatherRandomKey+294 fffff880`0115db04 85c0 test eax,eax BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff8000338d7bb to fffff8000303db6c STACK_TEXT: fffff880`031c4210 fffff800`0338d7bb : 00000000`00000000 fffff800`00000ff4 fffff880`031c42e0 00000000`00000000 : nt!ExpGetLookasideInformation+0x8c fffff880`031c42a0 fffff800`0338e1e5 : fffff8a0`0a14f170 00000000`00000000 00000000`00000004 00000000`00000000 : nt!ExpQuerySystemInformation+0x15bc fffff880`031c4640 fffff800`0308e993 : fffff8a0`0a160000 fffff800`0308d93d 00000000`00000041 fffffa80`07751a30 : nt!NtQuerySystemInformation+0x4d fffff880`031c4680 fffff800`0308af30 : fffff880`0115db04 00000000`00020000 fffff880`031c4844 fffff8a0`0a14f148 : nt!KiSystemServiceCopyEnd+0x13 fffff880`031c4818 fffff880`0115db04 : 00000000`00020000 fffff880`031c4844 fffff8a0`0a14f148 00000000`00000000 : nt!KiServiceLinkage fffff880`031c4820 fffff880`0115d56d : fffffa80`07751a30 00000000`00000000 fffff800`20206f49 fffff800`0309a2a1 : cng!GatherRandomKey+0x294 fffff880`031c4be0 fffff800`0338bc5d : 00000000`00000000 fffffa80`0b0e4bd0 fffffa80`0b0e4bd0 fffffa80`06d44040 : cng!scavengingWorkItemRoutine+0x3d fffff880`031c4c80 fffff800`0309c961 : fffff800`03234500 fffff800`0338bc20 fffffa80`06d44040 00000000`00000000 : nt!IopProcessWorkItem+0x3d fffff880`031c4cb0 fffff800`03333c06 : 00000560`00000000 fffffa80`06d44040 00000000`00000080 fffffa80`06d31040 : nt!ExpWorkerThread+0x111 fffff880`031c4d40 fffff800`0306dc26 : fffff880`02f64180 fffffa80`06d44040 fffff880`02f6efc0 00000560`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`031c4d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: cng!GatherRandomKey+294 FOLLOWUP_NAME: MachineOwner MODULE_NAME: cng IMAGE_NAME: cng.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc814 STACK_COMMAND: .cxr 0xfffff880031c3840 ; kb FAILURE_BUCKET_ID: X64_0x7E_cng!GatherRandomKey+294 BUCKET_ID: X64_0x7E_cng!GatherRandomKey+294 Followup: MachineOwner ---------
I also recommend that you uninstall Super AntiSpyware. Third party anti-malware programs are known to cause problems on some Win 7 systems. After you get your system running smoothly, you can try it again. As an alternative, you can try Malwarebytes which generally runs very well with Win 7.
I find an almost guaranteed BSOD maker on your system:Out of date drivers can and do cause memory corruptions and BSOD's. You have the following out of date drivers loading on your system. Update these drivers, especially those whose dates are in red font. Those are way obsolete.The 2005 version of this driver is a known BSOD cause.Code:ASACPI.sys Sun Mar 27 22:30:36 2005
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).
How to update drivers -Alpham164.sys Mon Jul 23 03:57:03 2007 - Ideazon ZBoard http://www.steelseries.com/download. Update these two drivers or upgrade your gaming keyboard.
Alpham264.sys Tue Mar 20 05:51:03 2007 - Ideazon ZBoard http://www.steelseries.com/download. See above
ASACPI.sys Sun Mar 27 22:30:36 2005 - This one you will have taken care of.
nvsmu.sys Mon Jun 29 03:36:37 2009 - nVidia nForce System Management Controller (nVidia nForce chipset driver) Drivers - Download NVIDIA Drivers. Update your chipset drivers.
RTCore64.sys Wed May 25 02:39:12 2005 - RivaTuner/EVGA Precision (known issues w/Win7) RivaTuner. Uninstall this tuner; it is not compatible with Win 7.Follow the above suggestions and let's see how your system runs. Update us and let us know. If you get another BSOD after you have done the above, please upload to us. We will take a look and go from there.- I have listed links to most of the drivers in the code box above. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
Last edited by CarlTR6; 16 Nov 2010 at 12:58.
thanks, for the quick response. updated all drivers, and everything is working fine for no. played cod black ops for 2 hrs no problems.
That is the news we like to hear!! Very good and a kudos to you for following suggestions. Post back in a couple of days and let us know how your system is doing. If you are still BSOD free, we will mark this thread as solved.
Can you tell me why my computer break down.??Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Aleksander\Desktop\112810-22671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03407000 PsLoadedModuleList = 0xfffff800`03644e50
Debug session time: Sun Nov 28 13:17:09.082 2010 (GMT+1)
System Uptime: 0 days 1:10:14.769
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {1, 2, 1, fffff800034b9c22}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000001, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800034b9c22, address which referenced memory
Debugging Details:
------------------
WORKER_ROUTINE:
+0
00000000`00000001 ?? ???
WORK_ITEM: fffff800034b9c22
CURRENT_IRQL: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880009a9950 -- (.trap 0xfffff880009a9950)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880009a9ba8
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800034b9c22 rsp=fffff880009a9ae0 rbp=fffff880009a9b80
r8=fffff800035f1e80 r9=0000000000000000 r10=fffff800036b1400
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KxWaitForLockOwnerShip+0x12:
fffff800`034b9c22 48890a mov qword ptr [rdx],rcx ds:5fd0:00000000`00000001=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003478469 to fffff80003478f00
STACK_TEXT:
fffff880`009a9808 fffff800`03478469 : 00000000`0000000a 00000000`00000001 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`009a9810 fffff800`034770e0 : 00000000`00000000 fffffa80`0216a080 00000000`00000348 00000000`00098b00 : nt!KiBugCheckDispatch+0x69
fffff880`009a9950 fffff800`034b9c22 : 00000000`00000000 00000000`00000003 00000000`00000000 fffff800`03486e2c : nt!KiPageFault+0x260
fffff880`009a9ae0 fffff800`03491af4 : fffffa80`0216a080 00000000`00000000 00000000`00000000 fffff800`03480052 : nt!KxWaitForLockOwnerShip+0x12
fffff880`009a9b10 fffff800`034c0346 : fffffa80`0216a080 00000000`000b2358 00000000`00000002 00000000`00000000 : nt!MiInsertPageInFreeOrZeroedList+0x4e4
fffff880`009a9c10 fffff800`0371c166 : fffffa80`03cd1b60 00000000`00000080 fffffa80`03cd1040 fffff800`03457479 : nt!MmZeroPageThread+0x895
fffff880`009a9d40 fffff800`03457486 : fffff800`035f1e80 fffffa80`03cd1b60 fffff800`035ffc40 00081a11`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`034770e0 440f20c0 mov rax,cr8
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiPageFault+260
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0xA_nt!KiPageFault+260
BUCKET_ID: X64_0xA_nt!KiPageFault+260
Followup: MachineOwner
Here is my last 4 minidump.
Files: Minidump
Hi oleczekk welcome to SF,
Follow this instruction and start your own thread.
Blue Screen of Death (BSOD) Posting Instructions
Sorry, but when i use BSOD Dump & System File Collection, My computer crash and restart. So if you can analize my minidump and tell where is the problem. Btw, Sorry for my English. :)
Start troubleshooting your problem by removing Avira and replace it with MSE.
http://www.microsoft.com/security_essentials/
Also remove Alcohol/Daemon software and uninstall its driver (sptd.sys) with this tools --> DuplexSecure - Downloads.
Because sptd.sys have some issue with windows 7. Then for alternative software you may use MagicISO.
These drivers must be updated:
Code:DB3G.sys Sun Nov 06 22:33:11 2005 -> Diamondback USB Optical Mouse Driver RTL8187.sys Sun Nov 18 23:00:48 2007 -> Realtek NIC driver ComproHID64.sys Sun Sep 30 18:56:11 2007 -> Compro Software Driver lirsgt.sys Tue Jun 17 08:17:08 2008 -> part of a Copy Protection platform developed by Tages SA sptd.sys Sun Oct 11 13:55:14 2009 -> Uninstall it with SPTDinst
OK I do it. I have problem with my RAM. Because when i testing my ram 2 GB memtest86+ all is ok and when a I test second 2 GB all is ok too but when i testing all ram 4 Gb memtest show problems. I update my bios to now version but problem don't lost. Can you tell what i can do it.
Specyfication:
Intel Core 2 Quad Q6600
ASRock P45R2000-Wifi
2 x 2GB DDR2 (PC8500) 533 MHz G.Skill
NVIDIA GeForce 8800 GT
Seagete 320 GB.
Test each stick individually and after you find a good stick, then test it with different slot.
The possibilities can be mismatch pair of RAM or bad motherboard slot.
Look at this tutor especially part 3:
RAM - Test with Memtest86+