New
#1
Bsod driver irql not less or equal
Hi, please help, my computer always go to BSOD mode every 5-6 Min...
here are detail of report in attachment.
Thank you in advance.
Hi, please help, my computer always go to BSOD mode every 5-6 Min...
here are detail of report in attachment.
Thank you in advance.
Update this driver and see if that helps.Code:Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\KoolKat77\Downloads\Compressed\ANEP-PC-Thu_08_13_2015_111518_62\081315-71015-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18798.x86fre.win7sp1_gdr.150316-1654 Machine Name: Kernel base = 0x83207000 PsLoadedModuleList = 0x833515b0 Debug session time: Thu Aug 13 08:50:05.081 2015 (UTC + 6:00) System Uptime: 0 days 0:45:00.002 Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. .............................................................. ................................................................ ................................ Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {66a0000c, 2, 1, 9415dbcf} Unable to load image \SystemRoot\system32\DRIVERS\netr70.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for netr70.sys *** ERROR: Module load completed but symbols could not be loaded for netr70.sys Probably caused by : netr70.sys ( netr70+26bcf ) 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: 66a0000c, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, value 0 = read operation, 1 = write operation Arg4: 9415dbcf, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8337184c Unable to read MiSystemVaType memory at 83350f00 66a0000c CURRENT_IRQL: 2 FAULTING_IP: netr70+26bcf 9415dbcf c6400c01 mov byte ptr [eax+0Ch],1 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xD1 PROCESS_NAME: chrome.exe ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre DPC_STACK_BASE: FFFFFFFF8078B000 TRAP_FRAME: 8078ac9c -- (.trap 0xffffffff8078ac9c) ErrCode = 00000002 eax=66a00000 ebx=9007e7c0 ecx=9019b808 edx=66a00000 esi=9008f800 edi=9415dca0 eip=9415dbcf esp=8078ad10 ebp=8078ad24 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 netr70+0x26bcf: 9415dbcf c6400c01 mov byte ptr [eax+0Ch],1 ds:0023:66a0000c=?? Resetting default scope LAST_CONTROL_TRANSFER: from 9415dbcf to 83247b5f STACK_TEXT: 8078ac9c 9415dbcf badb0d00 66a00000 832358dc nt!KiTrap0E+0x1b3 WARNING: Stack unwind information not available. Following frames may be wrong. 8078ad24 9415dd8c 90188000 8078ad68 9415dcfe netr70+0x26bcf 8078ad30 9415dcfe 90188000 82340fb8 00000580 netr70+0x26d8c 8078ad68 83d87008 6ff707f8 6ff81838 93aac754 netr70+0x26cfe 8078ad90 83d82ed1 9008f6f0 9007e7c0 90091028 Wdf01000!FxRequestBase::CompleteSubmitted+0xf1 8078adbc 83d830ae 9007e7c0 9d56b0d8 8078adf4 Wdf01000!FxIoTarget::RequestCompletionRoutine+0x140 8078adcc 8328a652 00000000 9008f6f0 9008f800 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x33 8078adf4 8327f553 00000000 9008f6f0 9d56b0d8 nt!IopUnloadSafeCompletion+0x4a 8078ae38 8353ab64 8d4ba0f0 9d4f7468 8d4ba028 nt!IopfCompleteRequest+0x128 8078aea0 8e39930d 83241788 9d4f7468 00000000 nt!IovCompleteRequest+0x133 8078aed0 8e399f55 93a90640 9008f6f0 93aac7a0 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0 8078aefc 8e39a6f6 8d4ba028 8d4ba0f0 8d4baa98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b 8078af24 8e3969ce 8d4ba028 8d4baa98 8d4ba002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc 8078af48 8327edf5 8d4baaa4 8d4ba002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173 8078afa4 8327ec58 83332d20 aa8913c0 00000000 nt!KiExecuteAllDpcs+0xf9 8078aff4 8327e41c 896c7ce4 00000000 00000000 nt!KiRetireDpcList+0xd5 8078aff8 896c7ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c 8327e41c 00000000 0000001a 00d6850f bb830000 0x896c7ce4 STACK_COMMAND: kb FOLLOWUP_IP: netr70+26bcf 9415dbcf c6400c01 mov byte ptr [eax+0Ch],1 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: netr70+26bcf FOLLOWUP_NAME: MachineOwner MODULE_NAME: netr70 IMAGE_NAME: netr70.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4538beaa FAILURE_BUCKET_ID: 0xD1_VRF_netr70+26bcf BUCKET_ID: 0xD1_VRF_netr70+26bcf ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xd1_vrf_netr70+26bcf FAILURE_ID_HASH: {0bf4dd97-0a0a-82b1-d9aa-6b10773f4f47} Followup: MachineOwner --------- 0: kd> lmvm netr70 start end module name 94137000 94178000 netr70 T (no symbols) Loaded symbol image file: netr70.sys Image path: \SystemRoot\system32\DRIVERS\netr70.sys Image name: netr70.sys Timestamp: Fri Oct 20 18:18:50 2006 (4538BEAA) CheckSum: 0003DF84 ImageSize: 00041000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Sometimes drivers remain and do not get completely uninstalled.
Driver Removal Process:
Link to full tutorial: Drivers - Clean Left over Files after Uninstalling
- Download Driver Sweeper to the desired location.
- Extract the files from the zip.
- Uninstall the driver Program & Features - Control Panel.
- Run Driver Sweeper, check the drivers you want to uninstall or clean registry leftovers of.
Driver Reference Table