New
#1
New Bluescreen
Bluescreen again. Can someone help??
Bluescreen again. Can someone help??
Hi apd and welcome
this one is pretty obvious. was probably caused by your video driver (specifically the dxgkrnl.sys which is the directx portion of it)
You should update the video driver and the other old ones listed below
also run a system file check to verify and repair you system files
type cmd in search>right click and run as admin>sfc /scannow
if you are overclocking stop
if you have a raid update the driver
Hope this helps
Ken
Code:secdrv.SYS fffff880`0492b000 fffff880`04936000 0x0000b000 0x4508052e 9/13/2006 8:18:38 AM ASMMAP64.sys fffff880`02b56000 fffff880`02b5d000 0x00007000 0x45c63998 2/4/2007 2:52:56 PM sncduvc.SYS fffff880`02211000 fffff880`02219a80 0x00008a80 0x495894f2 12/29/2008 4:14:26 AM
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\122009-22822-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c05000 PsLoadedModuleList = 0xfffff800`02e42e50 Debug session time: Sun Dec 20 14:59:18.682 2009 (GMT-5) System Uptime: 0 days 0:25:59.586 Loading Kernel Symbols ............................................................... ................................................................ .................................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {60, 2, 1, fffff80002c80de6} Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for dxgkrnl.sys *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys Probably caused by : dxgkrnl.sys ( dxgkrnl+111c ) 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: 0000000000000060, 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: fffff80002c80de6, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ead0e0 0000000000000060 CURRENT_IRQL: 2 FAULTING_IP: nt!ExpReleaseResourceForThreadLite+46 fffff800`02c80de6 f0480fba696000 lock bts qword ptr [rcx+60h],0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff880030bc640 -- (.trap 0xfffff880030bc640) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000000000000f rbx=0000000000000000 rcx=0000000000000000 rdx=fffffa8006c8db60 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002c80de6 rsp=fffff880030bc7d0 rbp=fffffa8006c8db60 r8=0000000000000000 r9=000000000000000f r10=0000000000000000 r11=fffff88002e86120 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up di pl zr na po nc nt!ExpReleaseResourceForThreadLite+0x46: fffff800`02c80de6 f0480fba696000 lock bts qword ptr [rcx+60h],0 ds:a768:00000000`00000060=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002c76469 to fffff80002c76f00 STACK_TEXT: fffff880`030bc4f8 fffff800`02c76469 : 00000000`0000000a 00000000`00000060 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`030bc500 fffff800`02c750e0 : fffffa80`05ee5000 00000000`00000000 0d002004`00001f80 0000ffff`0004c300 : nt!KiBugCheckDispatch+0x69 fffff880`030bc640 fffff800`02c80de6 : fffffa80`06c8db60 fffffa80`06c8db60 fffffa80`046d1000 00000000`00000000 : nt!KiPageFault+0x260 fffff880`030bc7d0 fffff880`046fb11c : 00000000`00000002 fffffa80`05ee5000 fffffa80`040ca000 00000000`00000000 : nt!ExpReleaseResourceForThreadLite+0x46 fffff880`030bc830 00000000`00000002 : fffffa80`05ee5000 fffffa80`040ca000 00000000`00000000 fffffa80`040ca000 : dxgkrnl+0x111c fffff880`030bc838 fffffa80`05ee5000 : fffffa80`040ca000 00000000`00000000 fffffa80`040ca000 fffff880`046fb6e6 : 0x2 fffff880`030bc840 fffffa80`040ca000 : 00000000`00000000 fffffa80`040ca000 fffff880`046fb6e6 fffffa80`05ee5000 : 0xfffffa80`05ee5000 fffff880`030bc848 00000000`00000000 : fffffa80`040ca000 fffff880`046fb6e6 fffffa80`05ee5000 fffffa80`040ca000 : 0xfffffa80`040ca000 STACK_COMMAND: kb FOLLOWUP_IP: dxgkrnl+111c fffff880`046fb11c ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: dxgkrnl+111c FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ac5509e FAILURE_BUCKET_ID: X64_0xA_dxgkrnl+111c BUCKET_ID: X64_0xA_dxgkrnl+111c Followup: MachineOwner ---------
What about your other topic and the question that you asked about the drivers?
I requested more info there so I could answer your question.