Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Random freezes and crash


  • Please log in to reply
14 replies to this topic

#1 amuroray

amuroray

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:34 AM

Posted 17 September 2014 - 08:07 PM

Help guys, my computer frequntly freezes and often leads up to bsod. It started a month ago everytime I use firefox or any browser.

 

 

here is the diagnosis of the windbg to the crash dump

 

 

Loading Dump File [C:\Windows\Minidump\080914-18720-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0x83011000 PsLoadedModuleList = 0x83151310
Debug session time: Sat Aug  9 18:32:22.442 2014 (UTC + 8:00)
System Uptime: 0 days 0:27:51.519
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
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: 00000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 80dc6120, The PRCB address of the hung processor.
Arg4: 00000001, 0.

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

Unable to load image \SystemRoot\system32\DRIVERS\aswNdisFlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswNdisFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswNdisFlt.sys
Unable to load image Rtlh86.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rtlh86.sys
*** ERROR: Module load completed but symbols could not be loaded for Rtlh86.sys

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  1c

STACK_TEXT:  
80d8a2b4 830405e0 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e
80d8a2f0 83069ed3 00002710 00000000 0001a200 nt!KeAccumulateTicks+0x242
80d8a330 83069d80 830b0fc8 8313558c 00000000 nt!KeUpdateRunTime+0x145
80d8a388 83069583 8c2e041b 8c2e041b 000000d1 nt!KeUpdateSystemTime+0x613
80d8a388 830b0fc8 8c2e041b 8c2e041b 000000d1 nt!KeUpdateSystemTimeAssist+0x13
80d8a420 8307330b c030b110 84a8a498 00000001 nt!KxFlushEntireTb+0xf4
80d8a440 830a19e0 00000003 00000001 c030b110 nt!KeFlushTb+0x22a
80d8a464 830f19cb 00045c31 c030b110 45c31963 nt!MiInitializePfnAndMakePteValid+0x7f
80d8a4c0 830b9af5 00000114 6e6e6e4e 000000c0 nt!MmAllocateSpecialPool+0x4e8
80d8a4e8 83338cba 000000c0 00000114 6e6e6e4e nt!ExAllocatePoolWithTagPriority+0x32
80d8a51c 833388be 000000c0 00000114 6e6e6e4e nt!VeAllocatePoolWithTagPriority+0x1a7
80d8a538 85e21e01 00000000 00000110 6e6e6e4e nt!VerifierExAllocatePoolWithTagPriority+0x1f
80d8a550 85e20ecc 00000000 00000100 6e6e6e4e ndis!ndisAllocateFromNPagedPool+0x1d
80d8a578 85e20fe7 893d4c80 00000040 80d8a5a0 ndis!ndisPplAllocate+0x65
80d8a598 85eef145 00000001 00000000 00000000 ndis!NdisAllocateNetBufferAndNetBufferList+0x53
80d8a5c8 860c930c 95b0cf00 860d050f 00000000 NETIO!NetioAllocateAndReferenceCopyNetBufferListEx+0x25
80d8a5e0 8604feef 95b0cf00 00000000 8c678230 tcpip!NetioAllocateAndReferenceCopyNetBufferList+0x17
80d8a664 860be0f7 8c38adf8 80d8a694 80d8a698 tcpip!TcpCovetNetBufferList+0x38
80d8a684 860abfea 8c38adf8 8c38aef0 95b0cf00 tcpip!TcpInspectReceive+0x1b
80d8a71c 860aa5a5 8c6a2008 8c38adf8 80d8a744 tcpip!TcpTcbCarefulDatagram+0x171b
80d8a788 8608da38 8c6a2008 8c38adf8 00d8a7fc tcpip!TcpTcbReceive+0x22d
80d8a7f0 8608e26a 8c678f70 8c697000 00000000 tcpip!TcpMatchReceive+0x237
80d8a840 8608e2ab 8c6a2008 8c697000 00005000 tcpip!TcpPreValidatedReceive+0x293
80d8a85c 860885cf 8c6a2008 8c697000 80d8a898 tcpip!TcpReceive+0x2d
80d8a86c 86090814 80d8a880 c000023e 00000000 tcpip!TcpNlClientReceiveDatagrams+0x12
80d8a898 86090156 86109f90 80d8a8ec c000023e tcpip!IppDeliverListToProtocol+0x49
80d8a8b8 8608e518 86109da0 00000006 80d8a8ec tcpip!IppProcessDeliverList+0x2a
80d8a910 8608ffff 86109da0 00000006 00000000 tcpip!IppReceiveHeaderBatch+0x1fb
80d8a9a4 8609e515 931bd7b8 00000000 00000001 tcpip!IpFlcReceivePackets+0xbe5
80d8aa20 86098a9d 930d0408 95b0cf00 00000000 tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x746
80d8aa54 83065098 95b0cf00 9c4bcb23 8c6a6c38 tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x11e
80d8aabc 86098c0b 8609897f 80d8aae4 00000000 nt!KeExpandKernelStackAndCalloutEx+0x132
80d8aaf8 85e8518d 930d0402 95b0cf00 00000000 tcpip!FlReceiveNetBufferListChain+0x7c
80d8ab30 85e735be 97e9eaa8 95b0cf00 00000000 ndis!ndisMIndicateNetBufferListsToOpen+0x188
80d8ab58 85e734b2 00000000 930d0b70 95b0cf00 ndis!ndisIndicateSortedNetBufferLists+0x4a
80d8acd4 85e1ec1d 9303c0e0 00000000 00000000 ndis!ndisMDispatchReceiveNetBufferLists+0x129
80d8acf0 85e4f56a 9303c0e0 95b0cf00 00000000 ndis!ndisMTopReceiveNetBufferLists+0x2d
80d8ad0c 85e4f504 97e5ae00 95b0cf00 00000000 ndis!ndisFilterIndicateReceiveNetBufferLists+0x46
80d8ad28 8619d3ab 97e5ae00 95b0cf00 00000000 ndis!NdisFIndicateReceiveNetBufferLists+0x2f
WARNING: Stack unwind information not available. Following frames may be wrong.
80d8ad58 8619d491 930d0b70 00000000 00000004 aswNdisFlt+0x33ab
80d8ad78 85e73553 930d0b70 95b0cf00 00000000 aswNdisFlt+0x3491
80d8ada0 85e1ec78 9303c0e0 95b0cf00 00000000 ndis!ndisMIndicateReceiveNetBufferListsInternal+0x62
80d8adc8 93c3bada 9303c0e0 95b0cf00 00000000 ndis!NdisMIndicateReceiveNetBufferLists+0x52
80d8aeb8 93c304cb 930a0488 00000000 00000000 Rtlh86+0xfada
80d8aee0 85e73892 930a0000 00000000 930a0000 Rtlh86+0x44cb
80d8af20 85e1ea0f 97cc6f44 00cc6e70 00000000 ndis!ndisMiniportDpc+0xda
80d8af48 83066975 97cc6f44 97cc6e70 00000000 ndis!ndisInterruptDpc+0xaf
80d8afa4 830667d8 83133d20 885be710 00000000 nt!KiExecuteAllDpcs+0xf9
80d8aff4 83065f9c 91a0e634 00000000 00000000 nt!KiRetireDpcList+0xd5
80d8aff8 91a0e634 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
83065f9c 00000000 0000001a 00d6850f bb830000 0x91a0e634


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:  CLOCK_WATCHDOG_TIMEOUT_2_PROC_VRF_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_2_PROC_VRF_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner

 

sorry I can't upload the crash dump. It looks like it was deleted when I run the diskcleanup.

Attached Files



BC AdBot (Login to Remove)

 


#2 sflatechguy

sflatechguy

  • BC Advisor
  • 2,191 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:34 PM

Posted 17 September 2014 - 10:10 PM

The 0x101 bugcheck error occurs when the CPU becomes unresponsive. http://msdn.microsoft.com/en-us/library/windows/hardware/ff557211%28v=vs.85%29.aspx

 

This can either be because of a faulty core inside the CPU, or a faulty driver is making the CPU unresponsive. Downloading and running a CPU diagnostic test for your particular CPU is probably a good idea.

 

You may want to uninstall and reinstall both Chrome and Firefox. Did you upgrade to this version of Windows 7 from Vista? You may want to ensure all your drivers are up to date and compatible with Windows 7.



#3 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,230 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:02:34 AM

Posted 17 September 2014 - 11:37 PM

my 2c...

 

Re-install Avast

 

I think that will fix it.



#4 sflatechguy

sflatechguy

  • BC Advisor
  • 2,191 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:34 PM

Posted 17 September 2014 - 11:48 PM

Given that there appears to be a problem with the Avast driver, that's a good suggestion. You may also want to focus on the Realtek 8101/8168/8169 PCI adapter driver, as there looks like there's an issue with that as well. Make sure it is up to date, and possibly even reinstall it.



#5 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,230 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:02:34 AM

Posted 17 September 2014 - 11:54 PM

I think Avast is killing the adapter driver also...



#6 amuroray

amuroray
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:34 AM

Posted 18 September 2014 - 04:09 AM

thanks for the advise guys

 

I will try it now.

 

I really wish this is not a hardware issue X(


Edited by amuroray, 18 September 2014 - 04:09 AM.


#7 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:04:34 PM

Posted 18 September 2014 - 06:47 PM

To find the source of the problem I'll need a Kernel dump file.

 

Go the Start
Right click My Computer
Select Properties
Click Advanced system settings
Click on the Advanced tab
Select Settings under Startup and Recovery
Then under Write debugging information select Kernel memory dump.

Once a dump is created go to:
 

C:\Windows\memory.dmp

Copy the file to the desktop, zip it up and upload it to a file sharing site like Onedrive. After the upload is done post the download link in your next reply.

 

Do note that 0x101s don't always mean a CPU is faulty, a driver can be holding up the processor and prevent it from responding to the clock interrupt etc.

 

Do note this:

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC

This 2 in this bugcheck string indicates the amount of cores in the CPU so in this case it's 2. Processors #0 and #1.

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: 00000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 80dc6120, The PRCB address of the hung processor.
Arg4: 00000001, 0.

The 4th parameter is 1, this indicates processor #1 is the one not responding, the processor that called the bugcheck was the primary processor #0 so the routines that are being executed by processor #0 are probably unrelated to processor #1 not responding to the clock interrupt.

 

The last thing I'd like to point out is:

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

Driver Verifier is enabled, this is giving me a hint that the CPU is failing, if a driver is performing illegal operations then DV will bugcheck. That being said I've seen lots of cases where a driver is misbehaving yet DV fails to catch it so without the Kernel dump it's hard to say.


Edited by Jared44, 18 September 2014 - 07:02 PM.


#8 amuroray

amuroray
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:34 AM

Posted 18 September 2014 - 07:56 PM

thanks,

 

now every time I open firefox it gives me bsods.

 

But other browser like operma mini is fine @_@

 

gonna wait for the bsod to strike again


Edited by amuroray, 18 September 2014 - 07:57 PM.


#9 amuroray

amuroray
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:34 AM

Posted 18 September 2014 - 08:15 PM

here is the file

 

 

https://onedrive.live.com/redir?resid=2302B472840D7C84!104&authkey=!AGlayA5pfZvWczM&ithint=file%2cdmp



#10 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,230 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:02:34 AM

Posted 18 September 2014 - 08:32 PM

Avast is still causing the issue...

 

edit: and I have noted other Avast users with DriverVerifier suddenly enabled also... it would pay to turn it off after re-installing Avast.


Edited by TsVk!, 18 September 2014 - 09:13 PM.


#11 amuroray

amuroray
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:34 AM

Posted 18 September 2014 - 09:18 PM

thanks I will also try that.

 

I'm using opera mini right now, can't open firefox even in safe mode



#12 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:04:34 PM

Posted 19 September 2014 - 03:51 AM

Okay, it's a Kernel memory dump but then again it's not a 0x101.

BugCheck C4, {e3, 86b7c282, 7f0008, 0}

We have a 0xC4 bugcheck, this indicates Driver Verifier crashed the system, the first parameter is e3 meaning a Kernel native system service was called using a user mode address as a parameter, probably the return address.

c33cc910 83b6aee1 000000c4 000000e3 86b7c282 nt!KeBugCheckEx+0x1e
c33cc930 83b78b63 86b7c282 007f0008 c33cc9c8 nt!VerifierBugCheckIfAppropriate+0x30
c33cc944 83b78bcd 86b7c282 c33cc9a8 86b7c282 nt!ViZwCheckAddress+0x30
c33cc958 83b78b8a 86b7c282 83b78eef 00000000 nt!ViZwCheckUnicodeString+0x22
c33cc960 83b78eef 00000000 00000000 c33cc9d0 nt!ViZwCheckObjectAttributes+0x15
c33cc970 86b7c282 c33cc9ec 80000000 c33cc9a8 nt!VfZwCreateFile+0x24
WARNING: Stack unwind information not available. Following frames may be wrong.
c33cc9d0 86b81f2f 007f0008 80000000 00000001 aswSP+0x22282
c33cc9f0 86b82630 007f0008 c33cca2c c33cca1c aswSP+0x27f2f
c33cca90 86b827f4 007f0008 00000000 00000002 aswSP+0x28630
c33ccaac 86b637c9 007f0008 00000000 45863dad aswSP+0x287f4
c33ccb18 86b60ecd 0027a440 00000000 0027c35a aswSP+0x97c9
c33ccb48 86b61787 949ccca8 01a3ef68 8d3855e0 aswSP+0x6ecd
c33ccb60 86b61854 949ccca8 baa3ef68 baa3ef68 aswSP+0x7787
c33ccb74 86b61e55 949ccca8 baa3ef68 45863d69 aswSP+0x7854
c33ccbdc 83b656c3 949ccca8 baa3ef68 b6baff80 aswSP+0x7e55
c33ccc00 8386dfe1 00000000 baa3ef68 949ccca8 nt!IovCallDriver+0x258
c33ccc14 83a43bbc b6baff80 baa3ef68 baa3efd8 nt!IofCallDriver+0x1b
c33ccc34 83a45f9f 949ccca8 b6baff80 00000000 nt!IopSynchronousServiceTail+0x1f8
c33cccd0 83a4cf71 949ccca8 baa3ef68 00000000 nt!IopXxxControlFile+0x6aa
c33ccd04 83874856 0000020c 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
c33ccd04 773170f4 0000020c 00000000 00000000 nt!KiSystemServicePostCall
0058ed08 00000000 00000000 00000000 00000000 0x773170f4

We can clearly see Avast making I/O calls and creating files, it creates a file with the wrong parameter and therefore we bugcheck.

 

As already stated you need to remove Avast.


Edited by Jared44, 19 September 2014 - 03:51 AM.


#13 amuroray

amuroray
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:34 AM

Posted 19 September 2014 - 05:26 AM

Thanks

I will try that thank you sirs for all your help.

I swear I almost called a technician for this.

Anyway, can you recommended me any free anti virus?

Edited by amuroray, 19 September 2014 - 05:29 AM.


#14 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:04:34 PM

Posted 19 September 2014 - 06:14 AM

If you're on Windows 7 or before then Microsoft Security Essentials is good enough.
If you're on Windows 8 or above then you can just use the Windows Defender as it is just MSE built in.

#15 amuroray

amuroray
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:12:34 AM

Posted 19 September 2014 - 06:48 AM

thanks gonna try that






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users