locked
Blue screen - BCCODE 9f - your advice would be greatly appreciated RRS feed

  • Question

  • Dear experts,

    My desktop is having very frequent BSOD since a few weeks (BCCODE 9f), and unfortunately I don't have the competences to detect and fix the cause of these freezes and restarts.

    Would you be so kind to have a look at my minidump files, and help me understand and fix this ?

    Most recent minidump files are copied here : https://onedrive.live.com/redir?resid=E0F18A10DD11E788!136&authkey=!ACgoxyULFapW_Pw&ithint=folder%2c.dmp

    Thanks a lot in advance for your help !!

    Cheers,

    Florian

    Wednesday, April 9, 2014 7:11 PM

Answers

  • Waw, this is great you have found it :-)

    I'll follow your instructions and let you know about it.

    A huge thank for your kind help and expertise, really really nice !

    Cheers,

    Florian

    • Marked as answer by ZigZag3143x Monday, April 14, 2014 11:29 AM
    Monday, April 14, 2014 8:22 AM

All replies

  • Florian

    These were related to memory corruption.  Please run driver verifier to find the underlying driver.  This may also be caused by a disk controller error so I would also suggest running chkdsk.

    These crashes were related to memory corruption (probably caused by a driver). 

    Please run this test to find which driver is causing the problem.  

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.


    Driver verifier (for complete directions see our wiki here)

    Co-Authored by  JMH3143

    CHKDSK /R /F
    Chkdsk disclaimer: While performing chkdsk on the hard drive if any bad sectors are found  any data available on that sector might be lost so as usual backup your data.
    Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.
    Do this for each hard drive on your system.
    When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.
    
    Then reboot and let the test run.
    It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.
    http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/
    
    
     See "CHKDSK LogFile" below in order to check the results of the test.
    
    CHKDSK LogFile:
    Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
    Expand the Windows logs heading, then select the Application log file entry.
    Double click on the Source column header.
    Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
    Copy/paste the results into your next post. 

    Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\040114-23212-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
    Machine Name:
    Kernel base = 0x82838000 PsLoadedModuleList = 0x829814d0
    Debug session time: Tue Apr  1 08:10:49.379 2014 (UTC - 4:00)
    System Uptime: 0 days 2:45:52.172
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7A, {c0414fa8, c0000185, 4bb95860, 829f5dfb}
    
    GetPointerFromAddress: unable to read from 829a1834
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KERNEL_DATA_INPAGE_ERROR (7a)
    The requested page of kernel data could not be read in.  Typically caused by
    a bad block in the paging file or disk controller error. Also see
    KERNEL_STACK_INPAGE_ERROR.
    If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
    it means the disk subsystem has experienced a failure.
    If the error status is 0xC000009A, then it means the request failed because
    a filesystem failed to make forward progress.
    Arguments:
    Arg1: c0414fa8, lock type that was held (value 1,2,3, or PTE address)
    Arg2: c0000185, error status (normally i/o status code)
    Arg3: 4bb95860, current process (virtual address for lock type 3, or PTE)
    Arg4: 829f5dfb, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    
    Debugging Details:
    ------------------
    
    
    ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
    
    DISK_HARDWARE_ERROR: There was error with disk hardware
    
    BUGCHECK_STR:  0x7a_c0000185
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    TRAP_FRAME:  89593c68 -- (.trap 0xffffffff89593c68)
    ErrCode = 00000010
    eax=851fbce8 ebx=00000000 ecx=00000009 edx=00000000 esi=00000314 edi=8690c5b0
    eip=829f5dfb esp=89593cdc ebp=89593d00 iopl=0         nv up ei ng nz na po cy
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010283
    nt!PiProcessReenumeration:
    829f5dfb 0000            add     byte ptr [eax],al          ds:0023:851fbce8=??
    Resetting default scope
    
    LOCK_ADDRESS:  8299ebe0 -- (!locks 8299ebe0)
    
    Resource @ nt!PiEngineLock (0x8299ebe0)    Available
    
    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
    
    
    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
    
    1 total locks
    
    PNP_TRIAGE: 
    	Lock address  : 0x8299ebe0
    	Thread Count  : 0
    	Thread address: 0x00000000
    	Thread wait   : 0x0
    
    LAST_CONTROL_TRANSFER:  from 828db187 to 82916bfc
    
    STACK_TEXT:  
    89593ad4 828db187 0000007a c0414fa8 c0000185 nt!KeBugCheckEx+0x1e
    89593b44 828dea69 89593b98 829a2300 89593bb8 nt!MiWaitForInPageComplete+0x302
    89593bd4 828c8180 829a2300 829f5dfb 869814d0 nt!MiIssueHardFault+0x3b3
    89593c50 82878aa8 00000008 829f5dfb 00000000 nt!MmAccessFault+0x29fc
    89593c50 829f5dfb 00000008 829f5dfb 00000000 nt!KiTrap0E+0xdc
    89593d00 828b514b 00000000 00000000 8454bd48 nt!PiProcessReenumeration
    89593d50 82a4113d 00000001 9338ccb1 00000000 nt!ExpWorkerThread+0x10d
    89593d90 828e8559 828b503e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
        829f5000-829f500a  11 bytes - nt!PipProcessDevNodeTree+281
    	[ fe ff ff 74 16 f7 05 cc:00 00 00 00 00 00 00 00 ]
        829f500e-829f5017  10 bytes - nt!PipProcessDevNodeTree+28f (+0x0e)
    	[ 80 75 0a c7 85 58 fe ff:00 00 00 00 00 00 00 00 ]
        829f501b-829f5025  11 bytes - nt!PipProcessDevNodeTree+29c (+0x0d)
    	[ 8b 85 58 fe ff ff 48 0f:00 00 00 00 00 00 00 00 ]
        829f5028-829f502c  5 bytes - nt!PipProcessDevNodeTree+2a9 (+0x0d)
    	[ 48 0f 85 9d 02:00 00 00 00 00 ]
        829f502f-829f5037  9 bytes - nt!PipProcessDevNodeTree+2b0 (+0x07)
    	[ 8b 47 04 3b c2 0f 84 37:00 00 00 00 00 00 00 00 ]
        829f503a-829f503e  5 bytes - nt!PipProcessDevNodeTree+2bb (+0x0b)
    	[ 8b f8 e9 8b 02:00 00 00 00 00 ]
        829f5041-829f504b  11 bytes - nt!PipProcessDevNodeTree+2c2 (+0x07)
    	[ 85 c9 79 0f c7 85 58 fe:00 00 00 00 00 00 00 00 ]
        829f504f-829f5080  50 bytes - nt!PipProcessDevNodeTree+2d0 (+0x0e)
    	[ e9 e3 fe ff ff 33 c0 83:00 00 00 00 00 00 00 00 ]
        829f5082-829f5088  7 bytes - nt!PipProcessDevNodeTree+303 (+0x33)
    	[ c7 85 58 fe ff ff 02:00 00 00 00 00 00 00 ]
        829f508c-829f50a8  29 bytes - nt!PipProcessDevNodeTree+30d (+0x0a)
    	[ 0f 85 a5 fe ff ff f6 c1:00 00 00 00 00 00 00 00 ]
        829f50ab-829f50b0  6 bytes - nt!PipProcessDevNodeTree+32c (+0x1f)
    	[ 8b f0 81 fe 03 01:00 00 00 00 00 00 ]
        829f50b3-829f50bc  10 bytes - nt!PipProcessDevNodeTree+334 (+0x08)
    	[ 75 0b 89 9d 54 fe ff ff:00 00 00 00 00 00 00 00 ]
        829f50c0-829f50c4  5 bytes - nt!PipProcessDevNodeTree+33e (+0x0d)
    	[ 85 f6 0f 8d d3:00 00 00 00 00 ]
        829f50c8-829f50ce  7 bytes - nt!PipProcessDevNodeTree+346 (+0x08)
    	[ e9 6a fe ff ff e9 c9:00 00 00 00 00 00 00 ]
        829f50d2-829f50d6  5 bytes - nt!PipProcessDevNodeTree+34b (+0x0a)
    	[ 8b c7 e8 22 0f:00 00 00 00 00 ]
        829f50d9-829f50e1  9 bytes - nt!PipProcessDevNodeTree+352 (+0x07)
    	[ 8b f0 c7 85 58 fe ff ff:00 00 00 00 00 00 00 00 ]
        829f50e5-829f50f3  15 bytes - nt!PipProcessDevNodeTree+35e (+0x0c)
    	[ e9 4d fe ff ff 39 9d 54:00 00 00 00 00 00 00 00 ]
        829f50f6 - nt!PipProcessDevNodeTree+36f (+0x11)
    	[ 40:00 ]
        829f50f8-829f50fc  5 bytes - nt!PipProcessDevNodeTree+371 (+0x02)
    	[ 74 07 be 2d 02:00 00 00 00 00 ]
        829f50fe-829f5110  19 bytes - nt!PipProcessDevNodeTree+377 (+0x06)
    	[ c0 eb 42 ff 75 1c 33 db:00 00 00 00 00 00 00 00 ]
        829f5117-829f5126  16 bytes - nt!PipProcessDevNodeTree+390 (+0x19)
    	[ 01 8b f0 74 12 8b 47 10:00 00 00 00 00 00 00 00 ]
        829f512a-829f5131  8 bytes - nt!PipProcessDevNodeTree+3a3 (+0x13)
    	[ ff ff ff fe 81 fe 03 01:00 00 00 00 00 00 00 00 ]
        829f5134-829f5150  29 bytes - nt!PipProcessDevNodeTree+3ad (+0x0a)
    	[ 75 0b 89 9d 54 fe ff ff:00 00 00 00 00 00 00 00 ]
        829f5154-829f515f  12 bytes - nt!PipProcessDevNodeTree+3cd (+0x20)
    	[ 8b f7 85 db 7d 2d 33 c0:00 00 00 00 00 00 00 00 ]
        829f5161-829f5168  8 bytes - nt!PipProcessDevNodeTree+3da (+0x0d)
    	[ c0 0f 94 c0 8d 04 85 0a:00 00 00 00 00 00 00 00 ]
        829f516c-829f5172  7 bytes - nt!PipProcessDevNodeTree+3e5 (+0x0b)
    	[ 50 32 c0 e8 b5 1c 10:00 00 00 00 00 00 00 ]
        829f5174-829f5177  4 bytes - nt!PipProcessDevNodeTree+3ed (+0x08)
    	[ 83 bf 3c 01:00 00 00 00 ]
        829f517b-829f5189  15 bytes - nt!PipProcessDevNodeTree+3f4 (+0x07)
    	[ 74 14 ff 77 10 e8 9e e3:00 00 00 00 00 00 00 00 ]
        829f518c-829f51a0  21 bytes - nt!PipProcessDevNodeTree+405 (+0x11)
    	[ e8 14 7d e5 ff 8b f3 85:00 00 00 00 00 00 00 00 ]
        829f51a2-829f51ac  11 bytes - nt!PipProcessDevNodeTree+41b (+0x16)
    	[ e9 90 fd ff ff 83 a5 3c:00 00 00 00 00 00 00 00 ]
        829f51ae-829f51bb  14 bytes - nt!PipProcessDevNodeTree+427 (+0x0c)
    	[ 33 ff 47 57 57 8d b5 48:00 00 00 00 00 00 00 00 ]
        829f51be-829f51c3  6 bytes - nt!PipProcessDevNodeTree+437 (+0x10)
    	[ 83 a5 54 fe ff ff:00 00 00 00 00 00 ]
        829f51c5-829f51f3  47 bytes - nt!PipProcessDevNodeTree+43e (+0x07)
    	[ 57 ff 75 1c ff 75 18 ff:00 00 00 00 00 00 00 00 ]
        829f51f5-829f522a  54 bytes - nt!PipProcessDevNodeTree+46e (+0x30)
    	[ 56 ff 71 18 8d 85 5c fe:00 00 00 00 00 00 00 00 ]
        829f522c-829f5230  5 bytes - nt!PipProcessDevNodeTree+4a5 (+0x37)
    	[ 57 e8 b4 fe 01:00 00 00 00 00 ]
        829f5232-829f524e  29 bytes - nt!PipProcessDevNodeTree+4ab (+0x06)
    	[ 8d 85 5c fe ff ff 50 8d:00 00 00 00 00 00 00 00 ]
        829f5250-829f5254  5 bytes - nt!PipProcessDevNodeTree+4c9 (+0x1e)
    	[ 85 c0 0f 84 9d:00 00 00 00 00 ]
        829f5258-829f525a  3 bytes - nt!PipProcessDevNodeTree+4d1 (+0x08)
    	[ 8b 80 b0:00 00 00 ]
        829f525e-829f52c8  107 bytes - nt!PipProcessDevNodeTree+4d7 (+0x06)
    	[ 8b 78 14 89 bd 50 fe ff:00 00 00 00 00 00 00 00 ]
        829f52cc-829f52dd  18 bytes - nt!PipProcessDevNodeTree+545 (+0x6e)
    	[ 39 95 30 fe ff ff 0f 85:00 00 00 00 00 00 00 00 ]
        829f52df-829f52f0  18 bytes - nt!PipProcessDevNodeTree+558 (+0x13)
    	[ 74 1b 8b b5 34 fe ff ff:00 00 00 00 00 00 00 00 ]
        829f52f2-829f52f6  5 bytes - nt!PipProcessDevNodeTree+56b (+0x13)
    	[ fb ff ff b8 01:00 00 00 00 00 ]
        829f52f9-829f52fe  6 bytes - nt!PipProcessDevNodeTree+572 (+0x07)
    	[ c0 eb 1a 83 7d 20:00 00 00 00 00 00 ]
        829f5300-829f5325  38 bytes - nt!PipProcessDevNodeTree+579 (+0x07)
    	[ 75 0e 8b 85 40 fe ff ff:00 00 00 00 00 00 00 00 ]
        829f5327-829f539c  118 bytes - nt!PipProcessDevNodeTree+5a0 (+0x27)
    	[ 90 99 4e 9f 82 cb 4e 9f:00 00 00 00 00 00 00 00 ]
        829f539f-829f53a1  3 bytes - nt!PnpDeviceCompletionProcessCompletedRequests+3e (+0x78)
    	[ 3d ce 02:00 00 00 ]
        829f53a3-829f53ab  9 bytes - nt!PnpDeviceCompletionProcessCompletedRequests+42 (+0x04)
    	[ c0 75 03 89 45 fc c7 06:00 00 00 00 00 00 00 00 ]
        829f53af-829f53be  16 bytes - nt!PnpDeviceCompletionProcessCompletedRequests+4e (+0x0c)
    	[ e8 5b 7b e5 ff 85 c0 74:00 00 00 00 00 00 00 00 ]
        829f53c0-829f53ca  11 bytes - nt!PnpDeviceCompletionProcessCompletedRequests+5f (+0x11)
    	[ 90 90 90 90 90 8b 49 10:00 00 00 00 00 00 00 00 ]
        829f53ce-829f53f5  40 bytes - nt!PiCheckForActiveDependencies+9 (+0x0e)
    	[ 32 c0 83 c1 34 8b 11 eb:00 00 00 00 00 00 00 00 ]
    WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
    3549 errors : !nt (829f5000-829f5fff)
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  LARGE_4096
    
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE_4096
    
    BUCKET_ID:  MEMORY_CORRUPTION_LARGE_4096
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:memory_corruption_large_4096
    
    FAILURE_ID_HASH:  {8d7aaa06-783f-2252-c9f3-768cf1e213bd}
    
    Followup: memory_corruption
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    Wednesday, April 9, 2014 10:18 PM
  • is there any beeping sound comes recently, if no, please also check your HDD health, if freeze and restart also happen before windows logo, I suspected this is HW issue


    • Edited by britishdhez Thursday, April 10, 2014 2:11 AM
    Thursday, April 10, 2014 2:10 AM
  • Thank you very much for this swift response!

    I'll run the driver test and chkdsk and let you know asap the results.

    I also fear that this is  a HW problem...

    Thursday, April 10, 2014 8:22 PM
  • Hi Team Zigzag !

    I followed the whole wiki for the driver verifier, but when rebooting it couldn't start anymore. So I had to accept a restore, and since then no bsod or freeze anymore. Strange.

    Regarding the chkdsk, here's the log file for my C: drive hereunder.

    Don't know if this means any bad news for my drive ?

    Thank you and have a nice day,

    FLORIAN

    Nom du journal :Application
    Source :       Microsoft-Windows-Wininit
    Date :         12/04/2014 19:59:44
    ID de l’événement :1001
    Catégorie de la tâche :Aucun
    Niveau :       Information
    Mots clés :    Classique
    Utilisateur :  N/A
    Ordinateur :   FlorianetAudrey
    Description :


    Checking file system on C:
    The type of the file system is NTFS.
    Volume label is WIN7.

    A disk check has been scheduled.
    Windows will now check the disk.                         

    CHKDSK is verifying files (stage 1 of 5)...
    Cleaning up instance tags for file 0x8dd9.
      277760 file records processed.                                         

    File verification completed.
      970 large file records processed.                                   

      0 bad file records processed.                                     

      2 EA records processed.                                           

      139 reparse records processed.                                      

    CHKDSK is verifying indexes (stage 2 of 5)...
      359770 index entries processed.                                        

    Index verification completed.
      0 unindexed files scanned.                                        

      0 unindexed files recovered.                                      

    CHKDSK is verifying security descriptors (stage 3 of 5)...
      277760 file SDs/SIDs processed.                                        

    Cleaning up 3706 unused index entries from index $SII of file 0x9.
    Cleaning up 3706 unused index entries from index $SDH of file 0x9.
    Cleaning up 3706 unused security descriptors.
    Security descriptor verification completed.
      41006 data files processed.                                           

    CHKDSK is verifying Usn Journal...
      36711800 USN bytes processed.                                            

    Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
      277744 files processed.                                                

    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
      5268201 free clusters processed.                                        

    Free space verification is complete.
    CHKDSK discovered free space marked as allocated in the
    master file table (MFT) bitmap.
    CHKDSK discovered free space marked as allocated in the volume bitmap.
    Windows has made corrections to the file system.

      83891634 KB total disk space.
      62297548 KB in 180015 files.
        134924 KB in 41007 indexes.
             0 KB in bad sectors.
        386354 KB in use by the system.
         65536 KB occupied by the log file.
      21072808 KB available on disk.

          4096 bytes in each allocation unit.
      20972908 total allocation units on disk.
       5268202 allocation units available on disk.

    Internal Info:
    00 3d 04 00 69 5f 03 00 96 78 06 00 00 00 00 00  .=..i_...x......
    c7 07 00 00 8b 00 00 00 00 00 00 00 00 00 00 00  ................
    b0 5b 20 00 50 01 1e 00 f0 17 1e 00 00 00 1e 00  .[ .P...........

    Windows has finished checking your disk.
    Please wait while your computer restarts.

    XML de l’événement :
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
        <EventID Qualifiers="16384">1001</EventID>
        <Version>0</Version>
        <Level>4</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-04-12T17:59:44.000000000Z" />
        <EventRecordID>2345</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>Application</Channel>
        <Computer>FlorianetAudrey</Computer>
        <Security />
      </System>
      <EventData>
        <Data>

    Checking file system on C:
    The type of the file system is NTFS.
    Volume label is WIN7.

    A disk check has been scheduled.
    Windows will now check the disk.                         

    CHKDSK is verifying files (stage 1 of 5)...
    Cleaning up instance tags for file 0x8dd9.
      277760 file records processed.                                         

    File verification completed.
      970 large file records processed.                                   

      0 bad file records processed.                                     

      2 EA records processed.                                           

      139 reparse records processed.                                      

    CHKDSK is verifying indexes (stage 2 of 5)...
      359770 index entries processed.                                        

    Index verification completed.
      0 unindexed files scanned.                                        

      0 unindexed files recovered.                                      

    CHKDSK is verifying security descriptors (stage 3 of 5)...
      277760 file SDs/SIDs processed.                                        

    Cleaning up 3706 unused index entries from index $SII of file 0x9.
    Cleaning up 3706 unused index entries from index $SDH of file 0x9.
    Cleaning up 3706 unused security descriptors.
    Security descriptor verification completed.
      41006 data files processed.                                           

    CHKDSK is verifying Usn Journal...
      36711800 USN bytes processed.                                            

    Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
      277744 files processed.                                                

    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
      5268201 free clusters processed.                                        

    Free space verification is complete.
    CHKDSK discovered free space marked as allocated in the
    master file table (MFT) bitmap.
    CHKDSK discovered free space marked as allocated in the volume bitmap.
    Windows has made corrections to the file system.

      83891634 KB total disk space.
      62297548 KB in 180015 files.
        134924 KB in 41007 indexes.
             0 KB in bad sectors.
        386354 KB in use by the system.
         65536 KB occupied by the log file.
      21072808 KB available on disk.

          4096 bytes in each allocation unit.
      20972908 total allocation units on disk.
       5268202 allocation units available on disk.

    Internal Info:
    00 3d 04 00 69 5f 03 00 96 78 06 00 00 00 00 00  .=..i_...x......
    c7 07 00 00 8b 00 00 00 00 00 00 00 00 00 00 00  ................
    b0 5b 20 00 50 01 1e 00 f0 17 1e 00 00 00 1e 00  .[ .P...........

    Windows has finished checking your disk.
    Please wait while your computer restarts.
    </Data>
      </EventData>
    </Event>


    Sunday, April 13, 2014 2:34 PM
  • Just forgot 1 thing : I have uploaded the last minidump file I had, before the restore but after having carried out the wiki for the driver verifier (it crashed a last time indeed).

    Same Onedrive link as in my previous post, filename : 041214-16910-01

    Just in case it can bring additional info.

    Thank you very much again,

    FLORIAN

    Sunday, April 13, 2014 2:41 PM
  • Blgnflp

    BINGO.  Verified and related to asacpi.sys.  Yours is from 2004!!!!

    The pre 2009 version of this driver is a known BSOD cause.

    Please visit Asus tek computer inc. -support- drivers and download p7p55d le
    http://support.asus.com/download.aspx?slanguage=en&m=p7p55d%20le&p=1&s=32&os=29&hashedid=e7zic83pvqsr80lm

    Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).
    Download and install it.
    Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (not before).  If you are using Win 8 there is at least a 2012 version which is needed for that.  If you cant find it on the ASUS site you can download it using windows update.  Read about it  here

    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\041214-16910-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
    Machine Name:
    Kernel base = 0x8284a000 PsLoadedModuleList = 0x829934d0
    Debug session time: Sat Apr 12 09:50:50.392 2014 (UTC - 4:00)
    System Uptime: 0 days 0:00:11.185
    Loading Kernel Symbols
    ...............................................................
    ........................................................
    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C9, {23b, 8ccda37c, 8e958e70, 0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\ASACPI.sys, Win32 error 0n2
    *** ERROR: Module load completed but symbols could not be loaded for ASACPI.sys
    Probably caused by : ASACPI.sys ( ASACPI+37c )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    Arguments:
    Arg1: 0000023b, The caller has changed the status field of an IRP it does not understand.
    Arg2: 8ccda37c, The address in the driver's code where the error was detected.
    Arg3: 8e958e70, IRP address.
    Arg4: 00000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc9_23b
    
    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23b
    
    FAULTING_IP: 
    ASACPI+37c
    8ccda37c 8bf8            mov     edi,eax
    
    FOLLOWUP_IP: 
    ASACPI+37c
    8ccda37c 8bf8            mov     edi,eax
    
    IRP_ADDRESS: 8e958e70
    
    DEVICE_OBJECT: 8a3f8258
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    
    LOCK_ADDRESS:  829b0be0 -- (!locks 829b0be0)
    
    Resource @ nt!PiEngineLock (0x829b0be0)    Available
    
    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
    
    
    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
    
    1 total locks
    
    PNP_TRIAGE: 
    	Lock address  : 0x829b0be0
    	Thread Count  : 0
    	Thread address: 0x00000000
    	Thread wait   : 0x0
    
    LAST_CONTROL_TRANSFER:  from 82b80f03 to 82928bfc
    
    STACK_TEXT:  
    87185784 82b80f03 000000c9 0000023b 8ccda37c nt!KeBugCheckEx+0x1e
    871857a4 82b832cd 8ccda37c 871857dc 8ccda37c nt!VerifierBugCheckIfAppropriate+0x30
    871857bc 82b8332a 0000023b 8ccda37c 00000000 nt!ViErrorFinishReport+0xc9
    87185810 82b8a667 0000023b 8e958e70 8e958fb8 nt!VfErrorReport1+0x4d
    87185844 82b82ef7 8e958fb8 8e958fb8 8a23b948 nt!ViGenericVerifyIrpStackDownward+0x103
    87185860 82b81426 8c27ba40 8a3f8820 8e958fb8 nt!VfMajorVerifyIrpStackDownward+0x5a
    871858c0 82b80d33 8c3cf338 8e958e70 871858f0 nt!IovpCallDriver1+0x468
    871858d0 82b7b670 8a3f8820 8a3f87a8 8a3f8820 nt!VfBeforeCallDriver+0xe7
    871858f0 82880bd5 8e958fb8 8e958e70 8a3f8820 nt!IovCallDriver+0x206
    87185904 8ccda37c 8c2819f0 8e958e70 82b7b6c3 nt!IofCallDriver+0x1b
    WARNING: Stack unwind information not available. Following frames may be wrong.
    87185934 82880bd5 00000000 8e958ff8 8a3f86f0 ASACPI+0x37c
    87185948 82b8d4d0 8c3d03b0 8e958e70 8a3f8258 nt!IofCallDriver+0x1b
    87185960 82b7b6c3 8a3f8310 8e958e70 8e959000 nt!ViFilterDispatchGeneric+0x5e
    87185984 82880bd5 00000000 87185a0c 8a3f8258 nt!IovCallDriver+0x258
    87185998 82b80bcc 00000004 00000017 00000000 nt!IofCallDriver+0x1b
    871859c4 82b8a4f7 89f27b90 871859e8 00000001 nt!VfIrpSendSynchronousIrp+0xa5
    87185a10 82b8311f 89f28b58 87185a9c 829fb803 nt!VfWmiTestStartedPdoStack+0x48
    87185a1c 829fb803 89f27b90 89f28b58 00000000 nt!VfMajorTestStartedPdoStack+0x48
    87185a9c 82a07065 00000001 00000000 8a3d2008 nt!PipProcessStartPhase3+0x427
    87185c94 829d2e5c 85141d58 8a3d2008 87185cc8 nt!PipProcessDevNodeTree+0x2e6
    87185cd4 8285ed09 8a3d2008 829aeb00 845f8020 nt!PiProcessStartSystemDevices+0x6d
    87185d00 828c714b 00000000 00000000 845f8020 nt!PnpDeviceActionWorker+0x241
    87185d50 82a5313d 00000001 9bf045bb 00000000 nt!ExpWorkerThread+0x10d
    87185d90 828fa559 828c703e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    SYMBOL_STACK_INDEX:  a
    
    SYMBOL_NAME:  ASACPI+37c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: ASACPI
    
    IMAGE_NAME:  ASACPI.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  411c2d04
    
    FAILURE_BUCKET_ID:  0xc9_23b_VRF_ASACPI+37c
    
    BUCKET_ID:  0xc9_23b_VRF_ASACPI+37c
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0xc9_23b_vrf_asacpi+37c
    
    FAILURE_ID_HASH:  {022a9a24-11a5-d5e8-5405-697dfad3ae8b}
    
    Followup: MachineOwner
    ---------
    


    Wanikiya and Dyami--Team Zigzag


    Sunday, April 13, 2014 2:47 PM
  • Waw, this is great you have found it :-)

    I'll follow your instructions and let you know about it.

    A huge thank for your kind help and expertise, really really nice !

    Cheers,

    Florian

    • Marked as answer by ZigZag3143x Monday, April 14, 2014 11:29 AM
    Monday, April 14, 2014 8:22 AM
  • FLorian

    Good luck


    Wanikiya and Dyami--Team Zigzag

    Monday, April 14, 2014 11:29 AM