New
#1
BSOD While Browsing Internet Using Google Chrome
past 2 week i am getting BSOD while browsing using google chrome
past 2 week i am getting BSOD while browsing using google chrome
i tried verifier after that i was getting continue 2 BSOD all the screen gets hang but no shutdown or autorestart i need to manually restart my computer after logging the BSOD error message was shown
this is the 2nd attachment when BSOD occurring after using Verifier
Based on the bugchecks, I would recommend you follow and complete the steps given below:
If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens.
Uninstall your current antivirus software. It can be a cause of BSOD very often. Please remove it with its removal tool and use Microsoft Security Essentials in its place. Malwarebytes is a great combination with it. Go through this thread for more info.Code:Start Menu\Programs\ASUS Public:Start Menu\Programs\ASUS Public Start Menu\Programs\ASUS\AI Suite II Public:Start Menu\Programs\ASUS\AI Suite II Public Start Menu\Programs\MSI Afterburner\SDK Licketh-PC\Licketh:Start Menu\Programs\MSI Afterburner\SDK Licketh-PC\Licketh
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
Run SFC /SCANNOW Command - System File Checker to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
Make scans with Kaspersky TDSskiller and ESET Online scanner.
Daemon Tools/Alchohol is known to cause BSODs:
How to remove sptd.sys from systemCode:Start Menu\Programs\Alcohol 120% Public:Start Menu\Programs\Alcohol 120% Public
Registry and SPTD problems | DAEMON Pro Help
Perform a Clean Start up, this will help avoid any problematic applications from bugging the system.
Use Revo Uninstaller Free to uninstall stubborn software. Opt for Advanced Mode and uninstall the software, delete the leftover registry entries.
Use Crystal Disk Info to upload a screenshot of your Hard Drives (s). Test your Hard Drives (s) running a Hard Drive Diag.
Test and Diagnose RAM issues with RAM - Test with Memtest86+. Pay close attention to Part 3 of the tutorial "If you have errors" Take the test for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.
Monitor hardware temperature for overheating issues with system monitoring software like Speccy or HWMonitor. Upload a screen shot of the Summary tab as well:
Please disable Verifier now as it did not give a beneficial output:Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000096, fffff800036e3a14, fffff8800732aff0, 0} Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+224 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000096, Exception code that caused the bugcheck Arg2: fffff800036e3a14, Address of the instruction which caused the bugcheck Arg3: fffff8800732aff0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION} Privileged instruction. FAULTING_IP: nt!KeWaitForSingleObject+224 fffff800`036e3a14 440f22c0 mov cr8,rax CONTEXT: fffff8800732aff0 -- (.cxr 0xfffff8800732aff0) rax=0000000000000031 rbx=0000000000000031 rcx=0000000000000000 rdx=0000000000000000 rsi=fffffa800a6e3930 rdi=fffffa800ac72060 rip=fffff800036e3a14 rsp=fffff8800732b9d0 rbp=0000000000000000 r8=fffff78000000008 r9=0000000000000000 r10=0000000000000001 r11=fffff88003365180 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=fffffa800ac72168 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 nt!KeWaitForSingleObject+0x224: fffff800`036e3a14 440f22c0 mov cr8,rax Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: chrome.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800036e3a14 STACK_TEXT: fffff880`0732b9d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x224 FOLLOWUP_IP: nt!KeWaitForSingleObject+224 fffff800`036e3a14 440f22c0 mov cr8,rax SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KeWaitForSingleObject+224 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 5147d9c6 STACK_COMMAND: .cxr 0xfffff8800732aff0 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!KeWaitForSingleObject+224 BUCKET_ID: X64_0x3B_nt!KeWaitForSingleObject+224 Followup: MachineOwner ---------
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, 1a, fffff88003768778, fffff88003767fd0} Probably caused by : netbt.sys ( netbt!NbtTdiOpenAddress+411 ) Followup: MachineOwner --------- 6: 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: 000000000000001a, The address that the exception occurred at Arg3: fffff88003768778, Exception Record Address Arg4: fffff88003767fd0, 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: +0 00000000`0000001a ?? ??? EXCEPTION_RECORD: fffff88003768778 -- (.exr 0xfffff88003768778) ExceptionAddress: 000000000000001a ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000008 Parameter[1]: 000000000000001a Attempt to execute non-executable address 000000000000001a CONTEXT: fffff88003767fd0 -- (.cxr 0xfffff88003767fd0) rax=fffff880037689b0 rbx=fffff88003768a70 rcx=0000000000000000 rdx=fffff88003768a78 rsi=fffff88003768a30 rdi=fffff88003768a78 rip=000000000000001a rsp=fffff880037689b0 rbp=fffffa8006d2b660 r8=fffff88003768a70 r9=0000000000000004 r10=0000000000000100 r11=fffff880037689b0 r12=0000000000000000 r13=0000000000000001 r14=fffffa8006d09040 r15=0000000000000004 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 00000000`0000001a ?? ??? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP 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: 0000000000000008 EXCEPTION_PARAMETER2: 000000000000001a WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800038c8100 GetUlongFromAddress: unable to read from fffff800038c81c0 000000000000001a Nonpaged pool FOLLOWUP_IP: netbt!NbtTdiOpenAddress+411 fffff880`047a3dc2 413bc6 cmp eax,r14d FAILED_INSTRUCTION_ADDRESS: +411 00000000`0000001a ?? ??? BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from 0000000000000001 to 000000000000001a SYMBOL_ON_RAW_STACK: 1 STACK_ADDR_RAW_STACK_SYMBOL: fffff88003768bb0 STACK_COMMAND: dps FFFFF88003768BB0-0x20 ; kb STACK_TEXT: fffff880`03768b90 fffffa80`096e12d0 fffff880`03768b98 00000000`00000000 fffff880`03768ba0 00000000`00000001 fffff880`03768ba8 fffff880`047a3dc2 netbt!NbtTdiOpenAddress+0x411 fffff880`03768bb0 00000000`00000120 fffff880`03768bb8 fffff800`0378012b nt!VfAvlLookupTreeNode+0x9b fffff880`03768bc0 fffff980`0bc94000 fffff880`03768bc8 fffff980`0bc94ee0 fffff880`03768bd0 00000000`00000001 fffff880`03768bd8 fffffa80`06d2b660 fffff880`03768be0 fffff980`0bc94ee0 fffff880`03768be8 00000000`00000120 fffff880`03768bf0 fffffa80`06d2b660 fffff880`03768bf8 fffff980`0bc94ee0 fffff880`03768c00 00000000`00000000 fffff880`03768c08 fffff800`03b2e9dc nt!VfRemLockDeleteMemoryRange+0x8c SYMBOL_NAME: netbt!NbtTdiOpenAddress+411 FOLLOWUP_NAME: MachineOwner MODULE_NAME: netbt IMAGE_NAME: netbt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79386 FAILURE_BUCKET_ID: X64_0x7E_VRF_BAD_IP_netbt!NbtTdiOpenAddress+411 BUCKET_ID: X64_0x7E_VRF_BAD_IP_netbt!NbtTdiOpenAddress+411 Followup: MachineOwner --------- 6: kd> lmvm netbt start end module name fffff880`0476d000 fffff880`047b2000 netbt (pdb symbols) c:\symbols\netbt.pdb\3D581F5A08614A7CB02D71638469228D2\netbt.pdb Loaded symbol image file: netbt.sys Mapped memory image file: c:\symbols\netbt.sys\4CE7938645000\netbt.sys Image path: \SystemRoot\System32\DRIVERS\netbt.sys Image name: netbt.sys Timestamp: Sat Nov 20 15:23:18 2010 (4CE79386) CheckSum: 00041134 ImageSize: 00045000 File version: 6.1.7601.17514 Product version: 6.1.7601.17514 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.7 Driver File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: netbt.sys OriginalFilename: netbt.sys ProductVersion: 6.1.7601.17514 FileVersion: 6.1.7601.17514 (win7sp1_rtm.101119-1850) FileDescription: MBT Transport driver LegalCopyright: © Microsoft Corporation. All rights reserved.