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 - stop 0x1A & 0x101


08 Mar 2013   #1

Windows 7 Ultimate x64
 
 
BSOD - stop 0x1A & 0x101

Hi,

I've recently installed windows 7 and have a had a couple of bsod's today. Was browsing at the time, and the pc just froze the first time and I got no bsod so had to hold the power button to reboot. Then after rebooting a few minutes later I got the 1st bsod and then the 2nd. I've attached ur diagnostic tool dump below.

Any help would be appreciated.

Many thanks

My System SpecsSystem Spec
.

09 Mar 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff880009b3180, 4}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------
Follow this guide: STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg
My System SpecsSystem Spec
10 Mar 2013   #3

Windows 7 Ultimate x64
 
 

Thanks for your reply.
I've run Verifier and have had 2 more BSODs, dump file attached

I've pasted WinDbg info below which seems to suggest it's either my Hauppage TV pci card which is at fault or the Intel 82579V Gigabit driver, I have the latest drivers for both installed:

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D6, {fffff98008cc3003, 1, fffff8800648358d, 0}

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

Could not read faulting driver name
Probably caused by : hcw95bda.sys ( hcw95bda+158d )

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

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

DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (d6)
N bytes of memory was allocated and more than N bytes are being referenced.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff98008cc3003, memory referenced
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation
Arg3: fffff8800648358d, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb3100
GetUlongFromAddress: unable to read from fffff80002eb31c0
 fffff98008cc3003 

FAULTING_IP: 
hcw95bda+158d
fffff880`0648358d 40086903        or      byte ptr [rcx+3],bpl

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD6

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800a675fe0 -- (.trap 0xfffff8800a675fe0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000103 rbx=0000000000000000 rcx=fffff98008cc3000
rdx=fffffa800a414601 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800648358d rsp=fffff8800a676170 rbp=0000000000000001
 r8=fffffa800a414600  r9=0000000000000000 r10=fffff80003133640
r11=fffffa8009bd30d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
hcw95bda+0x158d:
fffff880`0648358d 40086903        or      byte ptr [rcx+3],bpl ds:fffff980`08cc3003=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cf8cb0 to fffff80002c7ac40

STACK_TEXT:  
fffff880`0a675e78 fffff800`02cf8cb0 : 00000000`00000050 fffff980`08cc3003 00000000`00000001 fffff880`0a675fe0 : nt!KeBugCheckEx
fffff880`0a675e80 fffff800`02c78d6e : 00000000`00000001 fffff980`08cc3003 fffffa80`0aa29d00 00000000`00000103 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`0a675fe0 fffff880`0648358d : fffff980`08cc2ea0 00000000`00000100 00000000`00000001 fffffa80`08458c00 : nt!KiPageFault+0x16e
fffff880`0a676170 fffff980`08cc2ea0 : 00000000`00000100 00000000`00000001 fffffa80`08458c00 fffffa80`092b9560 : hcw95bda+0x158d
fffff880`0a676178 00000000`00000100 : 00000000`00000001 fffffa80`08458c00 fffffa80`092b9560 fffff800`03125c16 : 0xfffff980`08cc2ea0
fffff880`0a676180 00000000`00000001 : fffffa80`08458c00 fffffa80`092b9560 fffff800`03125c16 fffff980`08cc2ea0 : 0x100
fffff880`0a676188 fffffa80`08458c00 : fffffa80`092b9560 fffff800`03125c16 fffff980`08cc2ea0 00000000`00000002 : 0x1
fffff880`0a676190 fffffa80`092b9560 : fffff800`03125c16 fffff980`08cc2ea0 00000000`00000002 fffffa80`08458ab0 : 0xfffffa80`08458c00
fffff880`0a676198 fffff800`03125c16 : fffff980`08cc2ea0 00000000`00000002 fffffa80`08458ab0 fffff800`0312137e : 0xfffffa80`092b9560
fffff880`0a6761a0 fffff800`03124c42 : fffff980`08cc2f70 00000000`00000002 fffffa80`084e2f50 fffffa80`092b9560 : nt!IovCallDriver+0x566
fffff880`0a676200 fffff800`03125c16 : fffff980`08cc2ea0 00000000`00000002 fffffa80`084e2e00 fffff980`08c54fc0 : nt!ViFilterDispatchGeneric+0x62
fffff880`0a676230 fffff880`06537ca8 : fffff980`08c54fc0 fffffa80`084e8a50 fffff980`08ddae50 fffffa80`09384b90 : nt!IovCallDriver+0x566
fffff880`0a676290 fffff980`08c54fc0 : fffffa80`084e8a50 fffff980`08ddae50 fffffa80`09384b90 fffff880`06549398 : hcw95rc+0xca8
fffff880`0a676298 fffffa80`084e8a50 : fffff980`08ddae50 fffffa80`09384b90 fffff880`06549398 00000000`00000005 : 0xfffff980`08c54fc0
fffff880`0a6762a0 fffff980`08ddae50 : fffffa80`09384b90 fffff880`06549398 00000000`00000005 fffff880`0a6763c0 : 0xfffffa80`084e8a50
fffff880`0a6762a8 fffffa80`09384b90 : fffff880`06549398 00000000`00000005 fffff880`0a6763c0 00000000`00000000 : 0xfffff980`08ddae50
fffff880`0a6762b0 fffff880`06549398 : 00000000`00000005 fffff880`0a6763c0 00000000`00000000 fffff980`08ddae50 : 0xfffffa80`09384b90
fffff880`0a6762b8 00000000`00000005 : fffff880`0a6763c0 00000000`00000000 fffff980`08ddae50 fffff880`0653956d : HIDCLASS!WPP_ThisDir_CTLGUID_HidClassTraceGuid+0xd8
fffff880`0a6762c0 fffff880`0a6763c0 : 00000000`00000000 fffff980`08ddae50 fffff880`0653956d fffffa80`084c4e40 : 0x5
fffff880`0a6762c8 00000000`00000000 : fffff980`08ddae50 fffff880`0653956d fffffa80`084c4e40 fffffa80`084e8bc0 : 0xfffff880`0a6763c0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
hcw95bda+158d
fffff880`0648358d 40086903        or      byte ptr [rcx+3],bpl

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  hcw95bda+158d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hcw95bda

IMAGE_NAME:  hcw95bda.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ee661c9

FAILURE_BUCKET_ID:  X64_0xD6_hcw95bda+158d

BUCKET_ID:  X64_0xD6_hcw95bda+158d

Followup: MachineOwner
---------
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff88002f65180, 2}

*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002f65180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`03e27188 fffff800`02d19b0a : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`02f65180 : nt!KeBugCheckEx
fffff880`03e27190 fffff800`02ccc7e7 : 00000000`00000000 fffff800`00000002 00000000`00002710 00000000`00000246 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`03e27220 fffff800`02c0e895 : fffff800`02c34460 fffff880`03e273d0 fffff800`02c34460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`03e27320 fffff800`02cbf193 : 00000000`5f5e8ebb fffff800`02e3ee80 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`03e27350 fffff800`02cd1b12 : fffff800`02e3ee80 fffff880`00000001 00000000`00000000 fffff980`1cc36cd0 : nt!KiInterruptDispatchNoLock+0x163
fffff880`03e274e0 fffff800`02d71e16 : 00000000`00000000 fffff800`02e3ee80 fffff980`1cc36cd0 fffff880`03e22001 : nt!KiIpiSendRequestEx+0xb2
fffff880`03e27520 fffff800`02dcac49 : 00000000`00000001 fffff880`03e275e0 fffff6fc`c00e61b0 fffff980`1cc36cd0 : nt!KeFlushSingleTb+0x126
fffff880`03e275a0 fffff800`02df693b : fffff800`02c4d000 00000000`6264444e ffffffff`ffb3d080 fffff980`03ad6f80 : nt!MmFreeSpecialPool+0x349
fffff880`03e276f0 fffff800`0316b92b : fffff980`17b24e60 fffffa80`08042a80 fffff980`03acef60 fffffa80`080b74e8 : nt!ExDeferredFreePool+0xf33
fffff880`03e277a0 fffff880`016e58a7 : fffffa80`0807e860 fffff980`17b24e60 00000000`00000801 fffff880`03c24133 : nt!VerifierExFreePool+0x1b
fffff880`03e277d0 fffff880`03c1f344 : 00000000`00000000 fffffa80`080b74e8 00000000`00000000 fffff880`03c24228 : ndis!NdisMFreeNetBufferSGList+0xa7
fffff880`03e27810 00000000`00000000 : fffffa80`080b74e8 00000000`00000000 fffff880`03c24228 00000000`00000000 : e1c62x64+0x1f344


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_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------
I've also been running some stress testing but haven't had a crash as a result of it.

Thanks.
My System SpecsSystem Spec
.


10 Mar 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

You have rightly analyzed it. You need to update Hauppauge MOD7700 Tuner Driver. Search it in Hauppauge Computer Works Support Product Selector
Code:
fffff880`06482000 fffff880`06527000   hcw95bda T (no symbols)           
    Loaded symbol image file: hcw95bda.sys
    Image path: hcw95bda.sys
    Image name: hcw95bda.sys
    Timestamp:        Tue Dec 13 01:49:21 2011 (4EE661C9)
    CheckSum:         000A3C46
    ImageSize:        000A5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
10 Mar 2013   #5

Windows 7 Ultimate x64
 
 

All the BSODs/system freezes have occurred when I have NOT been using Windows Media Center to watch TV. How is that possible? Aren't the drivers in use only when i use the application?

Also there doesn't appear to be an updated driver, I'll ask on the Hauppage forum.
My System SpecsSystem Spec
04 Jul 2013   #6

Windows 7 Ultimate x64
 
 

An update for other users with the following error: STOP 0x101: CLOCK_WATCHDOG_TIMEOUT

I couldn't accurately diagnose the underlying problem so as suggested as a last resort on the link above I tried a fresh install and 4 months later I haven't had the error, I haven't had any BSODs, even without being able to update my Hauppage driver, which Hauppage support said was the latest version. I use my pc for several hours every single day for work and pleasure, and it's been trouble free since March.
My System SpecsSystem Spec
04 Jul 2013   #7
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Thanks for the update ... it will be really helpful
My System SpecsSystem Spec
Reply

 BSOD - stop 0x1A & 0x101




Thread Tools



Similar help and support threads for2: BSOD - stop 0x1A & 0x101
Thread Forum
Solved Stop 0x101 and 0x3B, completely random (Kind of) BSOD Help and Support
BSOD downloading heavy files / "stressing" Hard Drive error STOP 0x101 BSOD Help and Support
New Build, Bsod at randow. Stop:0x1a sub:41790 table page corrupted BSOD Help and Support
STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg Crash and lockup debug 'How To'
BSOD while idle,Stop 0x101 BSOD Help and Support
Windows 7 Pro x64 BSOD 0x101 Error BSOD Help and Support
Windows 7 x64 BSOD 0x101 BSOD Help and Support

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