New
#1
random bsod usbport.sys ntoskrnl.exe related
i am having problems with bsods on my new pc. i had problems with my gpu's drivers. its solved now(using an old beta driver now) but still having bsods probably related with usbport.sys ntoskrnl.exe tunnel.sys(based on whocrashed reports).
usbport and ntoskrnl bsods are random but when it comes to tunnel.sys i think its about vuze. it always appears when i m using vuze.
i also tried verifier and furmark.
i d appreciate any sort of help. thank you all.
heres minidumps and whocrashed reports.
please debug my minidumps for hidden drivers or sth. maybe i am missing something can cause bsods.
Code:System Information (local) -------------------------------------------------------------------------------- computer name: SERDAR-PC windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 8546111488 total VM: 2147352576, free: 1953382400 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Sat 26.01.2013 22:46:16 GMT your computer crashed crash dump file: C:\Windows\Minidump\012713-4368-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190) Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sat 26.01.2013 22:46:16 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: usbport.sys (USBPORT!USBPORT_RegisterUSBPortDriver+0x1CE7) Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\drivers\usbport.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: USB 1.1 & 2.0 Port Driver Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Sat 26.01.2013 19:50:45 GMT your computer crashed crash dump file: C:\Windows\Minidump\012613-5491-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190) Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sat 26.01.2013 17:12:04 GMT your computer crashed crash dump file: C:\Windows\Minidump\012613-8455-01.dmp This was probably caused by the following module: tunnel.sys (tunnel+0xD581) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88003AFE581, 0xFFFFF8800278E8F8, 0xFFFFF8800278E150) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\tunnel.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Microsoft Tunnel Interface Driver Bug check description: This indicates that a system thread generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Sat 26.01.2013 12:14:34 GMT your computer crashed crash dump file: C:\Windows\Minidump\012613-5506-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xD1 (0xDF28A000, 0x2, 0x0, 0xFFFFF88003DACF00) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Last edited by curautvaleas; 28 Jan 2013 at 14:49.