BSOD browsing Firefox

gullible1 · 08 Feb 2015

First time user here. I have suspicions the memory use by Mozilla Firefox is triggering this blue screen crashing.

Attachment 349092

koolkat77 · 09 Feb 2015

Welcome to the forum.

Please check for updates on the Intel Graphic Driver. Also go through this guide: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Code:

Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\HAL-08_02_2015_154725_74\020815-50497-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18700.amd64fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0xfffff800`03214000 PsLoadedModuleList = 0xfffff800`03457890
Debug session time: Sun Feb  8 21:24:16.296 2015 (UTC + 6:00)
System Uptime: 0 days 0:43:09.218
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 116, {fffffa800e5e1010, fffff88006025950, 0, d}

Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+1d950 )

Followup: MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800e5e1010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88006025950, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
igdkmd64+1d950
fffff880`06025950 4889542410      mov     qword ptr [rsp+10h],rdx

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

STACK_TEXT:  
fffff880`07305888 fffff880`106ea134 : 00000000`00000116 fffffa80`0e5e1010 fffff880`06025950 00000000`00000000 : nt!KeBugCheckEx
fffff880`07305890 fffff880`106e9ebb : fffff880`06025950 fffffa80`0e5e1010 00000000`00000000 fffffa80`0a962010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`073058d0 fffff880`10791f13 : fffffa80`0e5e1010 00000000`00000000 00000000`00000000 fffffa80`0a962010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`07305900 fffff880`107bbd50 : fffffa80`00000000 00000000`00028798 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`073059e0 fffff880`107ba437 : 00000000`00000102 00000000`00000000 00000000`00028798 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
fffff880`07305a10 fffff880`1078d2d2 : ffffffff`ff676980 fffffa80`0a962010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`07305ab0 fffff880`107b9ff6 : 00000000`00000000 fffffa80`0b793730 00000000`00000080 fffffa80`0a962010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`07305bc0 fffff800`035270ca : 00000000`fffffc32 fffffa80`0a9aab50 fffffa80`057da040 fffffa80`0a9aab50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`07305c00 fffff800`0327bbe6 : fffff800`03404e80 fffffa80`0a9aab50 fffff800`03412cc0 00000000`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`07305c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
igdkmd64+1d950
fffff880`06025950 4889542410      mov     qword ptr [rsp+10h],rdx

SYMBOL_NAME:  igdkmd64+1d950

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME:  igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ddb070c

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_igdkmd64.sys

BUCKET_ID:  X64_0x116_IMAGE_igdkmd64.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_igdkmd64.sys

FAILURE_ID_HASH:  {88759713-193a-fb8a-dab9-6846ea1a48f2}

Followup: MachineOwner
---------

4: kd> lmvm igdkmd64
start             end                 module name
fffff880`06008000 fffff880`06bb9180   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Tue May 24 07:17:00 2011 (4DDB070C)
    CheckSum:         00BB2D63
    ImageSize:        00BB1180
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Clean boot

Troubleshoot Application Conflicts by Performing a Clean Startup

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

How to Change, Add, or Remove Startup Programs in Windows 7

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

Click on the
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow

Full tutorial here:

SFC /SCANNOW Command - System File Checker

Make scans with the following:

Kaspersky TDSSKiller

Anti-rootkit utility TDSSKiller

ESET online scanner:

Free Online Virus Scanner | ESET

Run Disk Check on your Hard Drive for file system errors and bad sectors on it.

Hard Drive Diagnostics

Double click and open my computer.
Right click on desired drive and hit properties.
Click on tools tab and Check now.

Read complete instructions on the tutorial: Disk Check

Other Tests: