BSOD when browsing web, occurred many times

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 7 Pro 64bit
       #1

    BSOD when browsing web, occurred many times


    BSOD happened every few days when browsing websites, some of them caused by NTOSKRNL.exe and BOWSER.sys. I have uploaded the SF file.

    My machine specs are :
    Win 7 Pro 64bit,
    Lenovo Thinkpad T430s,
    16gb RAM,
    GPU: Intel HD4000,
    CPU: Intel i5 3320
    HDD:256gb samsung ssd

    Thanks!
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome

    For the bug check you are getting (a serious one) go through this thread:
    STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Yusra\Downloads\mikeuno\SF_14-09-2012\091412-7644-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Machine Name:
    Kernel base = 0xfffff800`0305b000 PsLoadedModuleList = 0xfffff800`0329f670
    Debug session time: Thu Sep 13 22:29:38.419 2012 (UTC + 6:00)
    System Uptime: 1 days 14:32:44.636
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 101, {31, 0, fffff88003365180, 2}
    
    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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffff88003365180, The PRCB address of the hung processor.
    Arg4: 0000000000000002, 0.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  ThunderPlatfor
    
    CURRENT_IRQL:  d
    
    STACK_TEXT:  
    fffff880`0de4d1d8 fffff800`03130efa : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`03365180 : nt!KeBugCheckEx
    fffff880`0de4d1e0 fffff800`030e3cd7 : 00000000`00000000 fffff800`00000002 00000000`00002710 fffffa80`1bc7bd64 : nt! ?? ::FNODOBFM::`string'+0x4e2e
    fffff880`0de4d270 fffff800`0301c895 : fffff800`03042460 fffff880`0de4d420 fffff800`03042460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
    fffff880`0de4d370 fffff800`030d6713 : fffff800`0324ce80 00000000`00000001 fffffa80`1bc71000 fffff800`03261580 : hal!HalpHpetClockInterrupt+0x8d
    fffff880`0de4d3a0 fffff800`030aeed1 : fffffa80`1bc4b630 00000000`176baa05 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
    fffff880`0de4d530 fffff800`0339134f : 00000000`00000000 fffff880`0de4db60 00000000`00000000 00000000`a000000c : nt!KeFlushProcessWriteBuffers+0x65
    fffff880`0de4d5a0 fffff800`033df686 : 00000000`0e37e4b0 fffffa80`00010400 fffff880`0de4d730 00000000`00000000 : nt!ExpGetProcessInformation+0x7f
    fffff880`0de4d6f0 fffff800`033e00d9 : 00000000`0e37e4b0 00000000`00000088 00000000`00000005 00000000`00000088 : nt!ExpQuerySystemInformation+0xfb4
    fffff880`0de4daa0 fffff800`030d9453 : fffffa80`18f24b50 fffff880`0de4db60 00000000`7ef94000 fffffa80`18ed2350 : nt!NtQuerySystemInformation+0x4d
    fffff880`0de4dae0 00000000`773d167a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0ca4e708 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773d167a
    
    
    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_4_PROC_ANALYSIS_INCONCLUSIVE
    
    BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
    
    Followup: MachineOwner
      My Computer


  3. Posts : 9
    Windows 7 Pro 64bit
    Thread Starter
       #3

    Thanks!

    Looks like a complicated issue. From Bluescreenview, it shows NToskrnl and bowser.sys caused the BSOD. I ran sfc.exe and everything is ok. This BSOD happens every 3 or 4 days. So do I need to reinstall the system or update all drivers?
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    I'm afraid that will not solve your issue, but did you look at the thread properly?
      My Computer


  5. Posts : 9
    Windows 7 Pro 64bit
    Thread Starter
       #5

    I will go through it and see what I can do about it.
      My Computer


  6. Posts : 15,026
    Windows 10 Home 64Bit
       #6

    Thanks.
    Take your time..also suggest you to do the stress tests mentioned in that thread and monitor your temps with Speccy.

    Let us know the status of warranty of your computer.
      My Computer


  7. Posts : 9
    Windows 7 Pro 64bit
    Thread Starter
       #7

    I just did some updates and uploaded new SF test file. Could you please look at it again and see if it's the same issue? Many thanks!
      My Computer


  8. Posts : 9
    Windows 7 Pro 64bit
    Thread Starter
       #8

    I bought the laptop in June this year. So everything is covered by warranty. But I'd like to verify the problem first.
      My Computer


  9. Posts : 15,026
    Windows 10 Home 64Bit
       #9

    The problem is with your processor.
    Are you having problems from the time you got this laptop or just recently?
      My Computer


  10. Posts : 9
    Windows 7 Pro 64bit
    Thread Starter
       #10

    The first time it occurred was about one month after I bought the laptop. Then it happens every few days. Even with warranty, it takes quite a while to replace processor.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 10:31.
Find Us