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 while Patching ArcheAge, caused by driver ntoskrl.exe

12 Apr 2015   #121
Boozad

W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
 
 

I don't have time to post it up in full at the moment (I'm on my phone now) but I'm suspecting the CPU.


My System SpecsSystem Spec
.
12 Apr 2015   #122
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

OK, good suspect.
My System SpecsSystem Spec
12 Apr 2015   #123
Boozad

W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
 
 

I'll try to post up my reasoning when I get to work although I won't have the dumps to hand as I don't have administrative rights to install WinDBG there. Just leaving the house now.
My System SpecsSystem Spec
.

12 Apr 2015   #124
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

Sounds good. just whenever you have time. I'm not sure I have ever seen this before.

Code:
Use !analyze -v to get detailed debugging information.
BugCheck 101, {31, 0, fffff880009ec180, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
My System SpecsSystem Spec
13 Apr 2015   #125
Boozad

W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
 
 

I've seen that numerous times, not much help really is it?

If you look at the 0x1A and use !analyze -v then take a look at the Process ID listed in the readout. That process is the .NET Framework which notoriously uses one core, sometimes slowing peoples PCs right down during the update process. Given that the OP is running Windows Updates it doesn't sound like a false positive. Couple that up with the three 0x101 STOPs (Watchdog Timeouts) and the processor sounds very suspect. I could be wrong, it's just a hunch at the moment.
My System SpecsSystem Spec
13 Apr 2015   #126
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

here you go, Gav. I'm going to go to sleep.

Code:
 !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: fffff880009ec180, 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:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  d
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff880`035850d8 fffff800`02d29d0a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009ec180 : nt!KeBugCheckEx
fffff880`035850e0 fffff800`02cdc647 : 00000000`00000000 fffff800`00000001 00000000`00002711 fffff800`02cbf873 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`03585170 fffff800`02c1e895 : fffff800`02c44460 fffff880`03585320 fffff800`02c44460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`03585270 fffff800`02cce413 : 00000000`8e1c9adb fffff800`02e4ee80 00000000`001fa000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`035852a0 fffff800`02cd7966 : fffff800`02e4ee80 00000000`00000001 00000000`00000000 fffff880`03585528 : nt!KiInterruptDispatchNoLock+0x163
fffff880`03585430 fffff800`02d168ac : fffff880`03585b01 fffffa80`0923c1c0 fffff980`0f9a4000 00000000`00000002 : nt!KeFlushMultipleRangeTb+0x266
fffff880`03585500 fffff880`0165d64d : fffffa80`0c7c0b50 00000000`871549ea fffff880`03585b01 fffffa80`0923c1c0 : nt!MmSetAddressRangeModified+0x2b0
fffff880`03585600 fffff880`01708bb5 : fffff8a0`0020d9f0 00000000`871549c2 00000000`00000000 fffffa80`0c7c0b00 : Ntfs!LfsFlushLfcb+0x5ad
fffff880`03585770 fffff880`0170adf1 : fffff880`03585b18 00000000`871549c2 fffff880`03585b18 fffff8a0`0020a590 : Ntfs!LfsFlushToLsnPriv+0x155
fffff880`03585800 fffff800`02d14c61 : fffff8a0`0020a590 00000000`871549c2 00000000`871549c2 fffffa80`0caf9af0 : Ntfs!LfsFlushToLsn+0xa1
fffff880`03585830 fffff800`02d13402 : fffffa80`0caf9af0 fffffa80`0caf9af0 00000000`00000000 fffff880`03585968 : nt!CcAcquireByteRangeForWrite+0x7e7
fffff880`03585910 fffff800`02d17066 : fffffa80`0caf9f68 fffffa80`00000001 fffff880`00000001 00000000`00157000 : nt!CcFlushCache+0x2c2
fffff880`03585a10 fffff800`02d17a28 : fffff880`00000000 fffff880`03585b18 fffffa80`1170e220 fffffa80`0caf9af0 : nt!CcWriteBehind+0x1c6
fffff880`03585ac0 fffff800`02cdba95 : fffffa80`0c76ca70 fffff800`02fcab01 fffff800`02edaae0 00000000`00000003 : nt!CcWorkerThread+0x1c8
fffff880`03585b70 fffff800`02f70b8a : 00000000`00000000 fffffa80`0c7c0b50 00000000`00000080 fffffa80`0c6e19e0 : nt!ExpWorkerThread+0x111
fffff880`03585c00 fffff800`02cc38e6 : fffff880`03365180 fffffa80`0c7c0b50 fffff880`0336ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03585c40 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
IMAGE_VERSION:  
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_clock_watchdog_timeout_4_proc_analysis_inconclusive
FAILURE_ID_HASH:  {d61e255a-5a6a-8ac9-10f0-973c0c42bda6}
Followup: MachineOwner
My System SpecsSystem Spec
13 Apr 2015   #127
Boozad

W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
 
 

OK, back from work, time to elaborate. There are three of these bugchecks in the log (0x101):
Code:
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

STACK_TEXT:  
fffff880`035850d8 fffff800`02d29d0a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009ec180 : nt!KeBugCheckEx
fffff880`035850e0 fffff800`02cdc647 : 00000000`00000000 fffff800`00000001 00000000`00002711 fffff800`02cbf873 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`03585170 fffff800`02c1e895 : fffff800`02c44460 fffff880`03585320 fffff800`02c44460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`03585270 fffff800`02cce413 : 00000000`8e1c9adb fffff800`02e4ee80 00000000`001fa000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`035852a0 fffff800`02cd7966 : fffff800`02e4ee80 00000000`00000001 00000000`00000000 fffff880`03585528 : nt!KiInterruptDispatchNoLock+0x163
fffff880`03585430 fffff800`02d168ac : fffff880`03585b01 fffffa80`0923c1c0 fffff980`0f9a4000 00000000`00000002 : nt!KeFlushMultipleRangeTb+0x266
fffff880`03585500 fffff880`0165d64d : fffffa80`0c7c0b50 00000000`871549ea fffff880`03585b01 fffffa80`0923c1c0 : nt!MmSetAddressRangeModified+0x2b0
fffff880`03585600 fffff880`01708bb5 : fffff8a0`0020d9f0 00000000`871549c2 00000000`00000000 fffffa80`0c7c0b00 : Ntfs!LfsFlushLfcb+0x5ad
fffff880`03585770 fffff880`0170adf1 : fffff880`03585b18 00000000`871549c2 fffff880`03585b18 fffff8a0`0020a590 : Ntfs!LfsFlushToLsnPriv+0x155
fffff880`03585800 fffff800`02d14c61 : fffff8a0`0020a590 00000000`871549c2 00000000`871549c2 fffffa80`0caf9af0 : Ntfs!LfsFlushToLsn+0xa1
fffff880`03585830 fffff800`02d13402 : fffffa80`0caf9af0 fffffa80`0caf9af0 00000000`00000000 fffff880`03585968 : nt!CcAcquireByteRangeForWrite+0x7e7
fffff880`03585910 fffff800`02d17066 : fffffa80`0caf9f68 fffffa80`00000001 fffff880`00000001 00000000`00157000 : nt!CcFlushCache+0x2c2
fffff880`03585a10 fffff800`02d17a28 : fffff880`00000000 fffff880`03585b18 fffffa80`1170e220 fffffa80`0caf9af0 : nt!CcWriteBehind+0x1c6
fffff880`03585ac0 fffff800`02cdba95 : fffffa80`0c76ca70 fffff800`02fcab01 fffff800`02edaae0 00000000`00000003 : nt!CcWorkerThread+0x1c8
fffff880`03585b70 fffff800`02f70b8a : 00000000`00000000 fffffa80`0c7c0b50 00000000`00000080 fffffa80`0c6e19e0 : nt!ExpWorkerThread+0x111
fffff880`03585c00 fffff800`02cc38e6 : fffff880`03365180 fffffa80`0c7c0b50 fffff880`0336ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03585c40 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

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_clock_watchdog_timeout_4_proc_analysis_inconclusive

FAILURE_ID_HASH:  {d61e255a-5a6a-8ac9-10f0-973c0c42bda6}
Then we have this 0x1A. As it's a 0x1A_41287 the only way to get any more info out of it would be to obtain a Kernel dump, but the process name stood out:
Code:
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, An illegal page fault occurred while holding working set synchronization.
    Parameter 2 contains the referenced virtual address.
Arg2: 00000000022b1000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  mscorsvw.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
There is some pertinent info on mscorsvw.exe here and with that info it may point to why the CPU hung in the next three BSODs.
This may be a stretch and I could be completely wrong, with 0x101s it's obviously best to try and find a software fault causing the hang which is why I was glad you found the iaStor.sys Steve, I completely missed that (it was 4:30am, that's my excuse). Maybe that will sort the issue as it's notorious for causing BSODs, we'll see. Hopefully that was the problem.
My System SpecsSystem Spec
13 Apr 2015   #128
HikariChino

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

I can't upload the folder, it keeps giving me a 500 internal server error. Should i use a file hosting service instead?
My System SpecsSystem Spec
13 Apr 2015   #129
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

Yes. use one of those. We have a size limit, I guess that is your problem is the size. Make sure you are uploading a zip file.
My System SpecsSystem Spec
13 Apr 2015   #130
HikariChino

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

filehosting.org | Download | CBS.zip

Here's the link. I'm about to start Memtest, unless you need me for something.
My System SpecsSystem Spec
Reply

 BSOD while Patching ArcheAge, caused by driver ntoskrl.exe




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Bsod caused by USB3 driver
I have a weird problem with USB 3 drivers I think. This is my configuration: Motherboard: Gigabyte GA-B75M-D3V Cpu : Intel Core i5 3470 Ram : 8 Gb Corsair 1333 Mhz Video: Gigabyte GeForce GTX 660 2048MB DDR5 OC version Hdd : Western Digital 640 GB 7200 Rpm Case: Segotep SG-Z2
BSOD Help and Support
BSOD - ntoskrl.exe problem, error 0x0000009f
Hi Firstly, many thanks for running this amazing forum! Judging by the number of posts and responses you give, this is a vital service! So... I assembled PC a few weeks ago using a second hand intel motherboard and i3 but all all else new bits and all seemed ok for several weels but a couple...
BSOD Help and Support
BSOD caused by driver ndis.sys
I have rebooted into safe mode without networking, deleted all drivers for my RealTek network card (currently running Realtek PCIe GBE Driver Win7 7067 01/22/2013) and restarted the computer several times. This does not seem to alleviate the problem. I have spent hours researching this and can't...
BSOD Help and Support
BSOD caused by unknown driver?
I've been dealing with BSOD issues with my laptop for almost a year now, supposedly it was a hard drive issue and I had that replaced through my warranty in December. BSOD stopped... for about 36 days, just long enough for my warranty to have expired 15 days earlier. It's only gotten worse since...
BSOD Help and Support
BSOD 0D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL in ntoskrl.exe and ntkrnlmp.exe
Over the last month, whilst the PC is idle (mostly overnight) I have had a few system hangs/crashes. The specific crashes that have resulted in a system Dump all point to the above modules as the offending elements I have, I believe followed the sticky detailing the process and attach the...
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 23:03.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App