locked
Win 7 BSOD caused by Ntoskrnl RRS feed

  • Question

  • I occasionally got this BSOD then when I look at the Bluescreen Viewer it said the BSOD was caused by ntoskrnl.exe.

    My computer is working fine except times when I was watching video or even leaving it idle; it will give me BSOD. 

    It is a Lenovo computer Ideapad Z575

    Window 7 64 Bit with AMD A6-3400M APU with Radeon(tm) HD Graphics 1.40 GHz

    6.00 GB Ram 

     

    Here is the information from BSV and attached minidump files 

    https://skydrive.live.com/redir.aspx?cid=466f424bf48b2753&resid=466F424BF48B2753!165

     

    091311-28563-01.dmp 13/09/2011 11:31:27 PM 0x00000101 00000000`00000031 00000000`00000000 fffff880`03164180 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\windows\Minidump\091311-28563-01.dmp  4 15 7601 275,384

     


    091211-46145-01.dmp 12/09/2011 10:13:57 PM 0x00000101 00000000`00000031 00000000`00000000 fffff880`031d5180 00000000`00000003 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\windows\Minidump\091211-46145-01.dmp  4 15 7601 275,440

     


    091111-46878-01.dmp 11/09/2011 8:49:32 PM 0x00000101 00000000`00000031 00000000`00000000 fffff880`03164180 00000000`00000002 atikmdag.sys atikmdag.sys+e844e x64 ntoskrnl.exe+7cc40 C:\windows\Minidump\091111-46878-01.dmp 4 15  7601 275,496

     

     


    080511-92945-01.dmp 05/08/2011 1:44:45 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff880`04bf099a fffff880`02d92e40 00000000`00000000 kbdclass.sys kbdclass.sys+199a x64 ntoskrnl.exe+80640 C:\windows\Minidump\080511-92945-01.dmp  4 15 7601 272,256

     

    Thursday, September 15, 2011 3:58 AM

Answers

  • and so it happened again after clean install.. with the same cause.. 

    Like I already said, this is a problem with your processor => hardware problems and clean install will not solve the problem.

    Contact your manufacturer Technical Support or replace the faulty processor.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator 

    • Marked as answer by Miya Yao Friday, October 7, 2011 2:38 AM
    Saturday, September 24, 2011 2:46 PM

All replies

  • *******************************************************************************

    *                                                                             *

    *                        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: fffff88003164180, 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:  ccsvchst.exe

     

    CURRENT_IRQL:  d

     

    STACK_TEXT:  

    fffff880`0b646168 fffff800`030eb8c9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`03164180 : nt!KeBugCheckEx

    fffff880`0b646170 fffff800`0309e497 : 00000000`00000000 fffff800`00000002 00000000`00002711 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e2e

    fffff880`0b646200 fffff800`0360a895 : fffff800`03630460 fffff880`0b6463b0 fffff800`03630460 00000000`00000000 : nt!KeUpdateSystemTime+0x377

    fffff880`0b646300 fffff800`03090173 : 00000000`35677a51 fffff800`03209e80 fffff800`03209e80 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d

    fffff880`0b646330 fffff800`030997a0 : fffff800`03209e80 fffffa80`00000001 00000000`00000000 fffff880`0b6465c8 : nt!KiInterruptDispatchNoLock+0x163

    fffff880`0b6464c0 fffff800`030b4001 : 00000000`00000000 00000000`00000010 00000000`00000001 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x260

    fffff880`0b646590 fffff800`031bfb5e : 00000000`00000010 fffff880`0b646700 fffff6fd`40059060 fffff800`03010000 : nt!MiFlushTbAsNeeded+0x1d1

    fffff880`0b6466a0 fffff800`030b4760 : 00000000`00010000 fffff800`0321e340 00000000`0000000c 00000000`00000000 : nt!MiAllocatePoolPages+0x4de

    fffff880`0b6467e0 fffff800`031c290e : 00000000`00000000 00000000`00000040 fffff800`00000000 00000000`00010000 : nt!ExpAllocateBigPool+0xb0

    fffff880`0b6468d0 fffff800`030a7ab6 : 00000000`00000000 00000000`0000000c 00000000`00224000 00000000`00000001 : nt!ExAllocatePoolWithTag+0x82e

    fffff880`0b6469c0 fffff800`033aefad : fffffa80`0ad8d518 00000000`00000001 fffffa80`08aac070 00000000`c0000001 : nt!ExAllocatePoolWithQuotaTag+0x56

    fffff880`0b646a10 fffff800`033af2f6 : fffff880`0b646bf8 00000000`000022b4 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0xb1b

    fffff880`0b646b40 fffff800`03092ed3 : fffff880`0b646ca0 fffffa80`08af8680 fffff880`0b646bf8 fffff880`0b646c00 : nt!NtDeviceIoControlFile+0x56

    fffff880`0b646bb0 00000000`73692e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

    00000000`00b7f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73692e09

     

     

    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

    ---------

    -----------------------------------------------------------------------------------------------------
    I analyzed the last dump file.

    Cause

    The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.

    Please update your processor driver and check again.
    If this does not help then please contact your manufacturer Technical Support.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator

    Thursday, September 15, 2011 7:42 AM
  • I checked the Lenovo website for the most updated driver to download but no luck. I called Lenovo yesterday and they said it is not hardware issue... so I am not sure what to do now... 
    Friday, September 16, 2011 3:47 AM
  • Hi vvn13,

    I'm trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.

    Regards,

    Miya 


    This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Friday, September 16, 2011 8:18 AM
  • Hi,

    afte checking the dump files, I also suspected the hardware driver cuased this BSOD issue. Please refer to the following steps:

    1. Change the video driver, upgrade the BIOS, disable the Anti-virus software temporary for test.

    2. If the BSOD still occurs, boot the pc to clean boot for reproduce this issue, it can narrow down if 3th party component cused this issue.

    ------------

    1)    Log on to the computer by using an account that has administrator rights.
    2)    Click Start, type msconfig.exe in the Start Search box, and then press ENTER to start the System Configuration Utility.
    3)    On the General tab, click Selective Startup, and then click to clear the Load startup items check box. (The Use Original Boot.ini check box is unavailable.)
    4)    On the Services tab, click to select the Hide all Microsoft services check box, and then click Disable all.
    5)    Click OK, Choose Don’t show this message again and then click Restart.

    If you want to start Windows normally after you do the test, Click Start, type msconfig.exe in the Start Search box, and then press ENTER to start the System Configuration Utility. On the General tab, click Normal Startup. Click OK, Choose Don’t show this message again and then click Restart.

    Thansk.


    “Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.”
    Friday, September 16, 2011 9:21 AM
  • Sorry I do not understand what do you mean by change the video driver.... 
    Friday, September 16, 2011 3:53 PM
  • and so it happened again after clean install.. with the same cause.. 
    Friday, September 23, 2011 4:49 AM
  • I have the same problem with my laptop since 05.september.2011 and BSoD happens at least once everyday while using my computer and I think it is related to one of latest WINDOWS UPDATES because a lot of other people has begun to get BSoDs since last month!!!
     
     My OS on notebook is windows 7 ultimate edition 64bit !
     
     I had 18 times BSoD (blue screen of death) since 05.september.2011 and I debugged all crash dump files, files causing BSoD are :
     
     Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+22d ) ===> 10 times
     
     Probably caused by : win32k.sys ( win32k!PopThreadGuardedObject+19 )  ===> 2 times
     
     Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )  ===> 2 times
     
     Probably caused by : memory_corruption ( nt!MiUnsecureVirtualMemory+15f )  ===> 3 times
     
     Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 )  ===> 1 time
     
     As you can all see, these files causing BSoD are ALL WINDOWS 7 CORE FILES, they are not driver files, they are not virus related etc.
     
     I have another desktop machine with windows 7 professional 64bit and it has been getting BSoDs since last month!
     
     You can debug your crash dump files to find out why your computer is getting a BSoD by reading this page => http://blogs.technet.com/b/askcore/archive/2008/11/01/how-to-debug-kernel-mode-blue-screen-crashes-for-beginners.aspx
     
     Microsoft MUST correct this issue immediately ! >:(
     
    If anybody wants to look at my original crash dump files, here is the link:
     
    https://skydrive.live.com/?cid=b2801afcf1b8bc71&sc=documents&id=B2801AFCF1B8BC71%21961
    Saturday, September 24, 2011 1:45 PM
  • and so it happened again after clean install.. with the same cause.. 

    Like I already said, this is a problem with your processor => hardware problems and clean install will not solve the problem.

    Contact your manufacturer Technical Support or replace the faulty processor.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator 

    • Marked as answer by Miya Yao Friday, October 7, 2011 2:38 AM
    Saturday, September 24, 2011 2:46 PM
  • I have the same problem with my laptop since 05.september.2011 and BSoD happens at least once everyday while using my computer and I think it is related to one of latest WINDOWS UPDATES because a lot of other people has begun to get BSoDs since last month!!!
     
     My OS on notebook is windows 7 ultimate edition 64bit !
     
     I had 18 times BSoD (blue screen of death) since 05.september.2011 and I debugged all crash dump files, files causing BSoD are :
     
     Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+22d ) ===> 10 times
     
     Probably caused by : win32k.sys ( win32k!PopThreadGuardedObject+19 )  ===> 2 times
     
     Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )  ===> 2 times
     
     Probably caused by : memory_corruption ( nt!MiUnsecureVirtualMemory+15f )  ===> 3 times
     
     Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 )  ===> 1 time
     
     As you can all see, these files causing BSoD are ALL WINDOWS 7 CORE FILES, they are not driver files, they are not virus related etc.
     
     I have another desktop machine with windows 7 professional 64bit and it has been getting BSoDs since last month!
     
     You can debug your crash dump files to find out why your computer is getting a BSoD by reading this page => http://blogs.technet.com/b/askcore/archive/2008/11/01/how-to-debug-kernel-mode-blue-screen-crashes-for-beginners.aspx
     
     Microsoft MUST correct this issue immediately ! >:(
     
    If anybody wants to look at my original crash dump files, here is the link:
     
    https://skydrive.live.com/?cid=b2801afcf1b8bc71&sc=documents&id=B2801AFCF1B8BC71%21961

    Hello,

    Please create a new thread and then post a link to it so that I debug dump files for you.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator 

    Saturday, September 24, 2011 2:47 PM
  • Hello,

    This is not  a processor issue as I am also getting the same error on Intel i7 -2600 processor and it is giving this error when mostly the system is idle and not having load..

    Do not point to hardware directly when you know not more..

    If you have any reply always welcome...

    Sunday, February 19, 2012 2:18 PM