Hi everyone,
My system crashes and a blue screen appears. I tried changing RAM from one slot to other. Installed a latest driver for my Netgear wireless usb adaptor. Tried installing each and every driver. But no use. I've attached the mini dump file. Please someone help me what's wrong.
A million Thanks
This one was caused by your video driver. I would un-install it with their un-install tool and re-install a fresh copy let us know if you need help ken
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Users\K\Desktop\041810-44397-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*f:\Symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.x86fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0x82845000 PsLoadedModuleList = 0x8298d810 Debug session time: Sun Apr 18 02:03:35.009 2010 (GMT-4) System Uptime: 0 days 12:31:08.116 Loading Kernel Symbols ............................................................... ................................................................ .................................... Loading User Symbols Loading unloaded module list ........... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {0, 2, 8, 0} 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 *** WARNING: Unable to verify timestamp for dxgkrnl.sys *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+4b0639 ) Followup: MachineOwner --------- 1: 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: 00000000, memory referenced Arg2: 00000002, IRQL Arg3: 00000008, value 0 = read operation, 1 = write operation Arg4: 00000000, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 829ad718 Unable to read MiSystemVaType memory at 8298d160 00000000 CURRENT_IRQL: 2 FAULTING_IP: +636c952f0295daf0 00000000 ?? ??? PROCESS_NAME: ccsvchst.exe CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 TRAP_FRAME: 807e8ca0 -- (.trap 0xffffffff807e8ca0) ErrCode = 00000010 eax=00000000 ebx=847ce3d8 ecx=847ce660 edx=847ce3d8 esi=847d22d0 edi=00000001 eip=00000000 esp=807e8d14 ebp=807e8d30 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 00000000 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from 00000000 to 8288b82b FAILED_INSTRUCTION_ADDRESS: +636c952f0295daf0 00000000 ?? ??? STACK_TEXT: 807e8ca0 00000000 badb0d00 847ce3d8 8e765679 nt!KiTrap0E+0x2cf WARNING: Frame IP not in any known module. Following frames may be wrong. 807e8d10 8eadd639 847d22d0 847ce6ec 847ce6c0 0x0 807e8d30 8e8f09e1 00000000 00000000 00000000 nvlddmkm+0x4b0639 807e8d78 8e8f0d89 847d22d0 847ce3d8 00000026 nvlddmkm+0x2c39e1 807e8dbc 8e982d2a 00000000 00000001 ffffffff nvlddmkm+0x2c3d89 807e8dd4 8ea7d180 847d22d0 858ea000 00000000 nvlddmkm+0x355d2a 807e8e5c 8e8c6687 00000000 86f8ad68 86f8ad68 nvlddmkm+0x450180 807e8e78 8e7426f2 847d22d0 86f8ad68 85c0c000 nvlddmkm+0x299687 807e8ef0 8e6949c7 85c0c000 00000000 85c071e8 nvlddmkm+0x1156f2 807e8f10 8e63a5b0 85be6518 807e8f28 8e6ec0b7 nvlddmkm+0x679c7 807e8f1c 8e6ec0b7 8e63a57f 807e8f48 8ef418c1 nvlddmkm+0xd5b0 807e8f28 8ef418c1 85c0c000 85be6850 870c9dcc nvlddmkm+0xbf0b7 807e8f48 828ad3b5 85be6850 85be6460 00000000 dxgkrnl+0x18c1 807e8fa4 828ad218 807c8120 870c9d48 00000000 nt!KiExecuteAllDpcs+0xf9 807e8ff4 828ac9dc b47c1ce4 00000000 00000000 nt!KiRetireDpcList+0xd5 807e8ff8 b47c1ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c 828ac9dc 00000000 0000001a 00d6850f bb830000 0xb47c1ce4 STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+4b0639 8eadd639 ?? ??? SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nvlddmkm+4b0639 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4abfff9d FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nvlddmkm+4b0639 BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nvlddmkm+4b0639 Followup: MachineOwner --------- 1: 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: 00000000, memory referenced Arg2: 00000002, IRQL Arg3: 00000008, value 0 = read operation, 1 = write operation Arg4: 00000000, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 829ad718 Unable to read MiSystemVaType memory at 8298d160 00000000 CURRENT_IRQL: 2 FAULTING_IP: +636c952f0295daf0 00000000 ?? ??? PROCESS_NAME: ccsvchst.exe CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 TRAP_FRAME: 807e8ca0 -- (.trap 0xffffffff807e8ca0) ErrCode = 00000010 eax=00000000 ebx=847ce3d8 ecx=847ce660 edx=847ce3d8 esi=847d22d0 edi=00000001 eip=00000000 esp=807e8d14 ebp=807e8d30 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 00000000 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from 00000000 to 8288b82b FAILED_INSTRUCTION_ADDRESS: +636c952f0295daf0 00000000 ?? ??? STACK_TEXT: 807e8ca0 00000000 badb0d00 847ce3d8 8e765679 nt!KiTrap0E+0x2cf WARNING: Frame IP not in any known module. Following frames may be wrong. 807e8d10 8eadd639 847d22d0 847ce6ec 847ce6c0 0x0 807e8d30 8e8f09e1 00000000 00000000 00000000 nvlddmkm+0x4b0639 807e8d78 8e8f0d89 847d22d0 847ce3d8 00000026 nvlddmkm+0x2c39e1 807e8dbc 8e982d2a 00000000 00000001 ffffffff nvlddmkm+0x2c3d89 807e8dd4 8ea7d180 847d22d0 858ea000 00000000 nvlddmkm+0x355d2a 807e8e5c 8e8c6687 00000000 86f8ad68 86f8ad68 nvlddmkm+0x450180 807e8e78 8e7426f2 847d22d0 86f8ad68 85c0c000 nvlddmkm+0x299687 807e8ef0 8e6949c7 85c0c000 00000000 85c071e8 nvlddmkm+0x1156f2 807e8f10 8e63a5b0 85be6518 807e8f28 8e6ec0b7 nvlddmkm+0x679c7 807e8f1c 8e6ec0b7 8e63a57f 807e8f48 8ef418c1 nvlddmkm+0xd5b0 807e8f28 8ef418c1 85c0c000 85be6850 870c9dcc nvlddmkm+0xbf0b7 807e8f48 828ad3b5 85be6850 85be6460 00000000 dxgkrnl+0x18c1 807e8fa4 828ad218 807c8120 870c9d48 00000000 nt!KiExecuteAllDpcs+0xf9 807e8ff4 828ac9dc b47c1ce4 00000000 00000000 nt!KiRetireDpcList+0xd5 807e8ff8 b47c1ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c 828ac9dc 00000000 0000001a 00d6850f bb830000 0xb47c1ce4 STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+4b0639 8eadd639 ?? ??? SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nvlddmkm+4b0639 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4abfff9d FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nvlddmkm+4b0639 BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nvlddmkm+4b0639 Followup: MachineOwner --------- 1: 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: 00000000, memory referenced Arg2: 00000002, IRQL Arg3: 00000008, value 0 = read operation, 1 = write operation Arg4: 00000000, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 829ad718 Unable to read MiSystemVaType memory at 8298d160 00000000 CURRENT_IRQL: 2 FAULTING_IP: +636c952f0295daf0 00000000 ?? ??? PROCESS_NAME: ccsvchst.exe CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 TRAP_FRAME: 807e8ca0 -- (.trap 0xffffffff807e8ca0) ErrCode = 00000010 eax=00000000 ebx=847ce3d8 ecx=847ce660 edx=847ce3d8 esi=847d22d0 edi=00000001 eip=00000000 esp=807e8d14 ebp=807e8d30 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 00000000 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from 00000000 to 8288b82b FAILED_INSTRUCTION_ADDRESS: +636c952f0295daf0 00000000 ?? ??? STACK_TEXT: 807e8ca0 00000000 badb0d00 847ce3d8 8e765679 nt!KiTrap0E+0x2cf WARNING: Frame IP not in any known module. Following frames may be wrong. 807e8d10 8eadd639 847d22d0 847ce6ec 847ce6c0 0x0 807e8d30 8e8f09e1 00000000 00000000 00000000 nvlddmkm+0x4b0639 807e8d78 8e8f0d89 847d22d0 847ce3d8 00000026 nvlddmkm+0x2c39e1 807e8dbc 8e982d2a 00000000 00000001 ffffffff nvlddmkm+0x2c3d89 807e8dd4 8ea7d180 847d22d0 858ea000 00000000 nvlddmkm+0x355d2a 807e8e5c 8e8c6687 00000000 86f8ad68 86f8ad68 nvlddmkm+0x450180 807e8e78 8e7426f2 847d22d0 86f8ad68 85c0c000 nvlddmkm+0x299687 807e8ef0 8e6949c7 85c0c000 00000000 85c071e8 nvlddmkm+0x1156f2 807e8f10 8e63a5b0 85be6518 807e8f28 8e6ec0b7 nvlddmkm+0x679c7 807e8f1c 8e6ec0b7 8e63a57f 807e8f48 8ef418c1 nvlddmkm+0xd5b0 807e8f28 8ef418c1 85c0c000 85be6850 870c9dcc nvlddmkm+0xbf0b7 807e8f48 828ad3b5 85be6850 85be6460 00000000 dxgkrnl+0x18c1 807e8fa4 828ad218 807c8120 870c9d48 00000000 nt!KiExecuteAllDpcs+0xf9 807e8ff4 828ac9dc b47c1ce4 00000000 00000000 nt!KiRetireDpcList+0xd5 807e8ff8 b47c1ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c 828ac9dc 00000000 0000001a 00d6850f bb830000 0xb47c1ce4 STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+4b0639 8eadd639 ?? ??? SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nvlddmkm+4b0639 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4abfff9d FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nvlddmkm+4b0639 BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nvlddmkm+4b0639 Followup: MachineOwner ---------