locked
DRIVER_VERIFIER_IOMANAGER_VIOLATION, PFN_LIST_CORRUPT, MEMORY_MANAGEMENT RRS feed

  • Question

  • So here we go, started having blue screens few days ago..

    It started after I had run a minecraft server and GTAV at the same time. 

    That bsod was Memory_Management and I been running minecraft server and Eve Online most of the day without problems, and then the memory_management problem started again. I tried reinstalling Java and updating Graphic drivers; none of this worked. 

    Then I used Windows Memory Diagnostic Tool (returned no errors). 
    Then I read that enabling driver verifier until next crash, will give out the culprit, if it was a driver. Funny enough the DRIVER_VERIFIER_IOMANAGER_VIOLATION bsod started right after this. 

    PFN_LIST_CORRUPT "links" to the same kernel as the MEMORY_MANAGEMENT dump file, this one happened when I started GTAV to test if anything would happen.

    With the dump files I will be giving the error files that forms in the minecraft server folder, if it can be to any help. 

    https://onedrive.live.com/?cid=0a12de85b5006344&id=A12DE85B5006344!1730&action=Share (Dump files, msinfo and minecraft server error files.)

    Sunday, May 3, 2015 8:48 PM

Answers

  • SI

    These were Related to IOMap64.sys Kernel Mode Driver for NT from ASUSTeK Computer Inc.  Yours is from 2010.  I would update to current or remove if it is not needed

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\New folder\050315-46421-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
    Machine Name:
    Kernel base = 0xfffff800`dc606000 PsLoadedModuleList = 0xfffff800`dc8df850
    Debug session time: Sun May  3 15:56:39.927 2015 (UTC - 4:00)
    System Uptime: 0 days 0:04:36.736
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C9, {226, fffff801991f4734, ffffcf825696eea0, 0}
    
    Unable to load image \??\C:\WINDOWS\system32\drivers\IOMap64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for IOMap64.sys
    *** ERROR: Module load completed but symbols could not be loaded for IOMap64.sys
    Probably caused by : IOMap64.sys ( IOMap64+1734 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    Arguments:
    Arg1: 0000000000000226, An IRP dispatch handler has returned without passing down or completing this IRP,
    	or someone forgot to return STATUS_PENDING.
    Arg2: fffff801991f4734, The address in the driver's code where the error was detected.
    Arg3: ffffcf825696eea0, IRP address.
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc9_226
    
    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  226
    
    FAULTING_IP: 
    IOMap64+1734
    fffff801`991f4734 4883ec28        sub     rsp,28h
    
    FOLLOWUP_IP: 
    IOMap64+1734
    fffff801`991f4734 4883ec28        sub     rsp,28h
    
    IRP_ADDRESS: ffffcf825696eea0
    
    DEVICE_OBJECT: ffffe0002c112680
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  aprp.exe
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff800dcc8b6b0 to fffff800dc756ca0
    
    STACK_TEXT:  
    ffffd000`22405378 fffff800`dcc8b6b0 : 00000000`000000c9 00000000`00000226 fffff801`991f4734 ffffcf82`5696eea0 : nt!KeBugCheckEx
    ffffd000`22405380 fffff800`dcc8e171 : fffff800`dcc7e470 fffff801`991f4734 ffffcf82`5696eea0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
    ffffd000`224053c0 fffff800`dcc84d34 : ffffe000`2b73a8d0 ffffd000`22405520 ffffe000`2b6ed150 00000000`00000000 : nt!ViErrorFinishReport+0x10d
    ffffd000`22405420 fffff800`dcc8abd5 : fffff800`dca2cb95 ffffe000`3332b001 ffffe000`2b73a8d0 fffff800`dca2cb95 : nt!IovpCallDriver2+0x4a0
    ffffd000`224057f0 fffff800`dcc7f928 : ffffcf82`5696eea0 00000000`00000002 ffffcf82`5696eea0 fffff800`dc6ae99d : nt!VfAfterCallDriver+0x289
    ffffd000`22405880 fffff800`dca2cc09 : ffffcf82`5696eea0 ffffe000`3332b0c0 00000000`00000000 ffffe000`2b73a8d0 : nt!IovCallDriver+0x3e4
    ffffd000`224058d0 fffff800`dca2d193 : ffffe000`2aefddc0 ffffd000`22405a19 00000000`00000000 00000000`00000000 : nt!IopCloseFile+0x12d
    ffffd000`22405960 fffff800`dc7624b3 : 00000000`00000008 00000000`0000017c 00000000`0008fdb0 00000000`0018f98c : nt!NtClose+0x1c3
    ffffd000`22405a80 00000000`77112352 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0008ee08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77112352
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    SYMBOL_NAME:  IOMap64+1734
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: IOMap64
    
    IMAGE_NAME:  IOMap64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b6b7a96
    
    FAILURE_BUCKET_ID:  0xc9_226_VRF_IOMap64+1734
    
    BUCKET_ID:  0xc9_226_VRF_IOMap64+1734
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0xc9_226_vrf_iomap64+1734
    
    FAILURE_ID_HASH:  {6fc2a713-6fd0-373e-6362-4ba2115370fb}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    Sunday, May 3, 2015 9:14 PM
  • Ah okey. Im doing the easy way out, Im doing full format on all my drives. Been wanting to do it for a long time anyway. Thanks for help. 
    • Marked as answer by Bruce Wooding Monday, May 11, 2015 10:48 PM
    Monday, May 4, 2015 11:39 AM
  • Haha, only if Windows wanted to be installed -facepalm-

    Error code: 0x80070570

    Got no OS installed at the moment.

    Using original bought copy of windows 8.

    Took out one of my ram sticks. Then windows wanted to be installed. I guess this is solved.
    • Marked as answer by Bruce Wooding Monday, May 11, 2015 10:46 PM
    Monday, May 4, 2015 2:39 PM

All replies

  • SI

    These were Related to IOMap64.sys Kernel Mode Driver for NT from ASUSTeK Computer Inc.  Yours is from 2010.  I would update to current or remove if it is not needed

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\New folder\050315-46421-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
    Machine Name:
    Kernel base = 0xfffff800`dc606000 PsLoadedModuleList = 0xfffff800`dc8df850
    Debug session time: Sun May  3 15:56:39.927 2015 (UTC - 4:00)
    System Uptime: 0 days 0:04:36.736
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C9, {226, fffff801991f4734, ffffcf825696eea0, 0}
    
    Unable to load image \??\C:\WINDOWS\system32\drivers\IOMap64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for IOMap64.sys
    *** ERROR: Module load completed but symbols could not be loaded for IOMap64.sys
    Probably caused by : IOMap64.sys ( IOMap64+1734 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    Arguments:
    Arg1: 0000000000000226, An IRP dispatch handler has returned without passing down or completing this IRP,
    	or someone forgot to return STATUS_PENDING.
    Arg2: fffff801991f4734, The address in the driver's code where the error was detected.
    Arg3: ffffcf825696eea0, IRP address.
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc9_226
    
    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  226
    
    FAULTING_IP: 
    IOMap64+1734
    fffff801`991f4734 4883ec28        sub     rsp,28h
    
    FOLLOWUP_IP: 
    IOMap64+1734
    fffff801`991f4734 4883ec28        sub     rsp,28h
    
    IRP_ADDRESS: ffffcf825696eea0
    
    DEVICE_OBJECT: ffffe0002c112680
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  aprp.exe
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff800dcc8b6b0 to fffff800dc756ca0
    
    STACK_TEXT:  
    ffffd000`22405378 fffff800`dcc8b6b0 : 00000000`000000c9 00000000`00000226 fffff801`991f4734 ffffcf82`5696eea0 : nt!KeBugCheckEx
    ffffd000`22405380 fffff800`dcc8e171 : fffff800`dcc7e470 fffff801`991f4734 ffffcf82`5696eea0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
    ffffd000`224053c0 fffff800`dcc84d34 : ffffe000`2b73a8d0 ffffd000`22405520 ffffe000`2b6ed150 00000000`00000000 : nt!ViErrorFinishReport+0x10d
    ffffd000`22405420 fffff800`dcc8abd5 : fffff800`dca2cb95 ffffe000`3332b001 ffffe000`2b73a8d0 fffff800`dca2cb95 : nt!IovpCallDriver2+0x4a0
    ffffd000`224057f0 fffff800`dcc7f928 : ffffcf82`5696eea0 00000000`00000002 ffffcf82`5696eea0 fffff800`dc6ae99d : nt!VfAfterCallDriver+0x289
    ffffd000`22405880 fffff800`dca2cc09 : ffffcf82`5696eea0 ffffe000`3332b0c0 00000000`00000000 ffffe000`2b73a8d0 : nt!IovCallDriver+0x3e4
    ffffd000`224058d0 fffff800`dca2d193 : ffffe000`2aefddc0 ffffd000`22405a19 00000000`00000000 00000000`00000000 : nt!IopCloseFile+0x12d
    ffffd000`22405960 fffff800`dc7624b3 : 00000000`00000008 00000000`0000017c 00000000`0008fdb0 00000000`0018f98c : nt!NtClose+0x1c3
    ffffd000`22405a80 00000000`77112352 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0008ee08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77112352
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    SYMBOL_NAME:  IOMap64+1734
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: IOMap64
    
    IMAGE_NAME:  IOMap64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b6b7a96
    
    FAILURE_BUCKET_ID:  0xc9_226_VRF_IOMap64+1734
    
    BUCKET_ID:  0xc9_226_VRF_IOMap64+1734
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0xc9_226_vrf_iomap64+1734
    
    FAILURE_ID_HASH:  {6fc2a713-6fd0-373e-6362-4ba2115370fb}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    Sunday, May 3, 2015 9:14 PM
  • I have no idea what "NT from ASUS" is, I know what asus is ofc. But no idea what "NT" is, tried googling and looking in my computer and find nothing, uninstalled the only asusrelated program I could find. The IOMap.sys is still there. I will keep looking while waiting for an answer.

    And I had some trouble so I restarted the pc, got another bluescreen with a new error caller (DRIVER_POWER_STATE_FAILURE)

    You will find the .rar file for that dmp in the same link as the others. 

    https://onedrive.live.com/?cid=0a12de85b5006344&id=A12DE85B5006344!1730&action=Share (linked again for convenience.)

    Monday, May 4, 2015 8:37 AM
  • SI

    The "NT" is unimportant.  What is important is the IOmap driver.  You need to remove it.

    The new dmp was not driver verified and Related to the Hamdrv.sys LogMeIn Hamachi Virtual Miniport Driver from LogMeIn Inc.


    Wanikiya and Dyami--Team Zigzag

    Monday, May 4, 2015 10:46 AM
  • Ah okey. Im doing the easy way out, Im doing full format on all my drives. Been wanting to do it for a long time anyway. Thanks for help. 
    • Marked as answer by Bruce Wooding Monday, May 11, 2015 10:48 PM
    Monday, May 4, 2015 11:39 AM
  • Si

    Smart move.  I am a big fan of them


    Wanikiya and Dyami--Team Zigzag

    Monday, May 4, 2015 11:43 AM
  • Haha, only if Windows wanted to be installed -facepalm-

    Error code: 0x80070570

    Got no OS installed at the moment.

    Using original bought copy of windows 8.

    • Edited by Siinrod Monday, May 4, 2015 2:05 PM
    Monday, May 4, 2015 2:03 PM
  • Haha, only if Windows wanted to be installed -facepalm-

    Error code: 0x80070570

    Got no OS installed at the moment.

    Using original bought copy of windows 8.

    Took out one of my ram sticks. Then windows wanted to be installed. I guess this is solved.
    • Marked as answer by Bruce Wooding Monday, May 11, 2015 10:46 PM
    Monday, May 4, 2015 2:39 PM