Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD when on internet (chrome)

19 Feb 2012   #1

Windows 7 64 bit (i think, how can i be sure?)
 
 
BSOD when on internet (chrome)

This is only the 3rd time this happened, but my computer also has been freezing completely... also 3 times. I just got this LENOVO, , it's great otherwise. I think I might have set up or installed something badly... please help.

Here is the info: ( I attached the dmp files too)



Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 101
BCP1: 0000000000000031
BCP2: 0000000000000000
BCP3: FFFFF880009E7180
BCP4: 0000000000000001
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\021912-18454-01.dmp
C:\Users\Minette\AppData\Local\Temp\WER-38969-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\windows\system32\en-US\erofflps.txt

My System SpecsSystem Spec
.

19 Feb 2012   #2

Windows 7 64 bit (i think, how can i be sure?)
 
 
dmp files

Here are the dmp files.
My System SpecsSystem Spec
19 Feb 2012   #3

Windows 7 64 bit (i think, how can i be sure?)
 
 
help please

how come no one can help me?
My System SpecsSystem Spec
.


19 Feb 2012   #4

Windows 7 Home Premium 64 Bit
 
 

Code:
Loading Dump File [F:\Kingston\BSODDmpFiles\Happy Kitty\021912-18454-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 Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03012000 PsLoadedModuleList = 0xfffff800`03257670
Debug session time: Sun Feb 19 11:50:28.070 2012 (GMT-7)
System Uptime: 0 days 0:50:01.849
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff880009e7180, 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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009e7180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`03b164e8 fffff800`030e68c9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009e7180 : nt!KeBugCheckEx
fffff880`03b164f0 fffff800`03099497 : 00000000`00000000 fffff800`00000001 00000000`00002710 00000000`0000000c : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`03b16580 fffff800`03605895 : fffff800`0362b460 fffff880`03b16730 fffff800`0362b460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`03b16680 fffff800`0308b173 : 00000000`8bfb2621 fffff800`03204e80 0000000a`00000122 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d
fffff880`03b166b0 fffff800`0309e782 : fffff800`03204e80 fffff800`00000000 fffff880`03b168f8 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`03b16840 fffff800`030948a2 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00004f5c : nt!KiIpiSendRequestEx+0xa2
fffff880`03b16880 fffff800`03079425 : 00000000`00000002 c9900000`959a5867 fffff880`03b16ba0 00000000`00001499 : nt!KeFlushMultipleRangeTb+0x362
fffff880`03b16950 fffff800`0310aac5 : fffffa80`03c29ec8 fffff800`00000001 00000000`00000001 fffff880`03b16bb0 : nt!MiAgeWorkingSet+0x37b
fffff880`03b16b00 fffff800`03079826 : 00000000`00000bb0 00000000`00000000 fffffa80`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x4d786
fffff880`03b16b80 fffff800`03079cd3 : 00000000`00000008 fffff880`03b16c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03b16bd0 fffff800`03329fee : fffffa80`036ce040 00000000`00000080 fffffa80`036a8840 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03b16d40 fffff800`030805e6 : fffff880`03764180 fffffa80`036ce040 fffff880`0376efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03b16d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


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
---------
If you are overclocking any hardware, please stop.


Your crash reports indicate a 0x101 crash. Refer to STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg and post back if you need further assistance.
My System SpecsSystem Spec
Reply

 BSOD when on internet (chrome)




Thread Tools




Our Sites

Site Links

About Us

Find 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 07:13 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33