Windows 7: BSOD while using Internet Explorer 9 on Windows 7 Ultimate x64

ourao · 27 Nov 2012

Hello everyone,

I made a clean install of Windows 7 Ultimate x64 and installed all my usual software (the same i used on Windows Vista) but now i keep getting BSOD all the time.

I noticed it started happening when i installed Kaspersky Internet Security 2013 and Internet Download Manager 6.12.

I used to BSOD when i started downloading anything.

I uninstalled IDM and installed other download managers but kept getting BSOD but now the BSOD happened while using internet explorer, so i reinstalled IDM but downgraded KIS 2013 to KIS 2012.

Now i get a lot less BSOD but still i get one like every 20 minutes and it ONLY happens when im using internet explorer with several tabs open.

I hope anyone can help me.

Arc · 27 Nov 2012

Welcome aboard.

All your today's crashes are clock watchdog timeout.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {60, 0, fffff880009e9180, 1}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000060, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009e9180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`03dc3468 fffff800`02aedd5a : 00000000`00000101 00000000`00000060 00000000`00000000 fffff880`009e9180 : nt!KeBugCheckEx
fffff880`03dc3470 fffff800`02aa0ad7 : fffff880`00000000 fffff800`00000001 00000000`00002626 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`03dc3500 fffff800`030141c0 : 00000000`00000000 fffff880`03dc36b0 fffff800`03030460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`03dc3600 fffff800`02a93513 : fffff800`02c09e80 fffff800`03030460 00000000`00000000 00001f80`00000c00 : hal!HalpRtcClockInterrupt+0x130
fffff880`03dc3630 fffff800`02a6bd47 : fffffa80`0a5ceb30 00000000`00000000 fffff800`02aa0e85 fffff800`02c09e80 : nt!KiInterruptDispatchNoLock+0x163
fffff880`03dc37c0 fffff800`02d9c9cf : 00000000`00000000 fffff880`03dc3ca0 00000000`00000000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x6b
fffff880`03dc3830 fffff800`02d9d029 : 00000000`0020bb30 fffff800`02d8907a 00000000`00000000 fffff800`00000001 : nt!ExpQuerySystemInformation+0x13af
fffff880`03dc3be0 fffff800`02a96253 : 000007fe`fbe50000 fffff880`03dc3ca0 ffffffff`fffe828e 000007fe`fbe60b48 : nt!NtQuerySystemInformation+0x4d
fffff880`03dc3c20 00000000`77c1167a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00cfefd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c1167a


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

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

In such a situation, it is the best you follow the guide: STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

ourao · 27 Nov 2012

I followed the instructions on the other post and after using the verifier like they said i couldnt even reboot...as soon as i get to desktop i get a blue screen with a FNETURPX.sys error.

So i logged on Safe Mode and remove the Verifier settings...i was able to reboot normally but im back to the old Blue Screens.

I read here http://www.w7forums.com/bsod-problem-t13674.html that deleting the file could solve the problem...any comments on that? Is it safe to delete that file?

Here is the error description:

Quote:

Assinatura do problema:
Nome do Evento de Problema: BlueScreen
Versão do SO: 6.1.7601.2.1.0.256.1
ID de Região: 2070
Informações adicionais sobre o problema:
BCCode: f7
BCP1: 00000B992DDFA232
BCP2: 00002B992DDFA232
BCP3: FFFFD466D2205DCD
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Ficheiros que ajudam a descrever o problema:
C:\Windows\Minidump\112712-37203-01.dmp
C:\Users\Bruno\AppData\Local\Temp\WER-55640-0.sysdata.xml
Leia a nossa declaração de privacidade online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0816
Se a declaração de privacidade online não estiver disponível, leia a declaração de privacidade offline:
C:\Windows\system32\pt-PT\erofflps.txt

And here is the updated dump file:

Arc · 27 Nov 2012

This is FNet Turbo HDD USB Driver - Also part of AsRock XFastUSB package.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D5, {fffff98012cf4f10, 0, fffff88004385740, 0}

*** WARNING: Unable to verify timestamp for FNETURPX.SYS
*** ERROR: Module load completed but symbols could not be loaded for FNETURPX.SYS

Could not read faulting driver name
Probably caused by : FNETURPX.SYS ( FNETURPX+1740 )

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

And it is very old.

Code:

lmvm FNETURPX
start             end                 module name
fffff880`04384000 fffff880`0438d000   FNETURPX T (no symbols)           
    Loaded symbol image file: FNETURPX.SYS
    Image path: \SystemRoot\System32\drivers\FNETURPX.SYS
    Image name: FNETURPX.SYS
    Timestamp:        Sat Oct 04 07:57:02 2008 (48E6D476)
    CheckSum:         00010F39
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Try to update it from www.pqi.com.tw/download.asp or FNet Corporation - or ASRock XFast USB.

Let us know the results.

ourao · 27 Nov 2012

Im going to try to update it but that one only happened when i tryed to reboot after using Verifier to test the drivers...

The usual Blue Screen i get is not related to FNET or at least it doesnt say so.

The one i usually get is this one:

Quote:

Assinatura do problema:
Nome do Evento de Problema: BlueScreen
Versão do SO: 6.1.7601.2.1.0.256.1
ID de Região: 2070
Informações adicionais sobre o problema:
BCCode: f7
BCP1: 00000B992DDFA232
BCP2: 00002B992DDFA232
BCP3: FFFFD466D2205DCD
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Ficheiros que ajudam a descrever o problema:
C:\Windows\Minidump\112712-37203-01.dmp
C:\Users\Bruno\AppData\Local\Temp\WER-55640-0.sysdata.xml
Leia a nossa declaração de privacidade online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0816
Se a declaração de privacidade online não estiver disponível, leia a declaração de privacidade offline:
C:\Windows\system32\pt-PT\erofflps.txt

Arc · 27 Nov 2012

What I am getting in the zip:
27.11.2012.
PM 3:30 = stop 0xD5
PM 3:27 = stop 0xD5
PM 1:34 = stop 0x101
AM 11:58 = stop 0x101 Checked earlier ...
All the subsequent dumps I am seeing are Stop 0x101.

I am not seeing any usually occurred stop 0xF7.

ourao · 27 Nov 2012

Quote: Originally Posted by Arc

What I am getting in the zip:
27.11.2012.
PM 3:30 = stop 0xD5
PM 3:27 = stop 0xD5
PM 1:34 = stop 0x101
AM 11:58 = stop 0x101 Checked earlier ...
All the subsequent dumps I am seeing are Stop 0x101.

I am not seeing any usually occurred stop 0xF7.

Thats weird...the last ones i got it said 0x00...000F7 on the bluescreen error

Arc · 27 Nov 2012

STOP 0x000000F7: DRIVER_OVERRAN_STACK_BUFFER

Usual causes: Device driver, Malware (source: Carrona.org)

► Scan the system for possible virus infection.

► Enable Driver Verifier.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

ourao · 27 Nov 2012

Now im crashing a lot...every 5 minutes...cant even update drivers because i keep getting BSOD

FILE:

Arc · 27 Nov 2012

27/11/2012
6:37 - Stop 0x101 - unknown image
6:32 - stop 0x101 - unknown image
6:28 - stop 0x101 - unknown image
5:56 - stop 0x3B - luafv.sys; a windows driver, cannot be the real cause. A deeper search in the dump showed

Code:

fffff880`0ce85440  fffff880`058ccfacUnable to load image \??\C:\Program Files\Folder Guard\FGUARD64.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for FGUARD64.SYS
*** ERROR: Module load completed but symbols could not be loaded for FGUARD64.SYS
 FGUARD64+0xbfac

WinAbility Folder Guard Device Driver. You need to uninstall it.
It also shows a historic nForce, nvstor64.sys.

Code:

lmvm nvstor64
start             end                 module name
fffff880`018ab000 fffff880`018ea000   nvstor64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\nvstor64.sys
    Image name: nvstor64.sys
    Timestamp:        Wed Jul 01 05:51:51 2009 (4A4AAC1F)
    CheckSum:         0003C24D
    ImageSize:        0003F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

As nforce controls a big part of the chipset drivers, you must to update it. But you may temporarily get rid of nForce and see what happens.
Get rid of nvstor.

Right click on "my computer" icon and click "manage" on the context menu.
It will open the "computer management" window.
Select "Device Manager" in the left pane, It will list all the existing devices up.
Expand "Disc Drives" by clicking on the triangle in front of it.
Select one item under it, right click, uninstall.
Continue the process for all items under "Disc Drives"
Now restart the computer. At restart, windows will auto configure the appropriate system driver, msahci.sys.

It also says, you need to check the storage discs.

Update your SSD's Firmware (skip it, if it is not a SSD)
Re-seat the sata and power.
Run chkdsk /f/r, following the option two of the tutorial Disk Check
Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

And, you Scan the system for possible virus infection.

4:41 - stop 0xF7, ultimately

Code:

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F7, {b992ddfa232, 2b992ddfa232, ffffd466d2205dcd, 0}

Probably caused by : nvlddmkm.sys ( nvlddmkm+18eea6 )

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

The version of the display driver is a bit problematic, IMO.

Code:

lmvm nvlddmkm
start             end                 module name
fffff880`0f899000 fffff880`1058d000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue Oct 02 23:51:13 2012 (506B3099)
    CheckSum:         00CD4613
    ImageSize:        00CF4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Download and install Driver Fusion.
Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
Boot normally now. Go to Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for GeForce 306.23 Driver, dated 13.9.2012 and install it.

Seeing the overall situation, I would suggest you to take three hardware tests, too.

► Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

► Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

► Stress test the CPU.
Hardware - Stress Test With Prime95

Checked the other dumps earlier ... so

Let us know the results, when you are done. If it is problematic to do these stuff in the normal situation, boot into Advanced Boot Options, safe mode with networking, and do these.

Windows 7: BSOD while using Internet Explorer 9 on Windows 7 Ultimate x64

BSOD while using Internet Explorer 9 on Windows 7 Ultimate x64 problems?