BSOD when I changed Graphic card

Page 1 of 2 12 LastLast

  1. Posts : 18
    Windos 7 x64
       #1

    BSOD when I changed Graphic card


    Hello,
    recently I changed my graphic card and I installed ASUS nv460 768 mb.
    Card works great and It pass all tests like unigine Heaven, Furmark etc...In games for exaple BFC2 it works well but in some other I have often freeze. I have the latest drivers for card. My configuration is

    amd x4 965
    4 gb of ram 1600mhz
    PSU 750 w
    GPU Asus Nvidia 460 768 mb
    Motherborad GIGABYTE UDP 4 790XT
    3 HDDs

    I am including minidump file and diagx I hope that someone can help me. I realy do not know what to do I tired new drivers, new MB Bios...
    Thanks for help,
    N
      My Computer


  2. Posts : 11,840
    64-bit Windows 8.1 Pro
       #2

    Im sorry, but the .dmp file is corrupt.. please repost the file, using the following instructions..

    https://www.sevenforums.com/crashes-d...tructions.html
      My Computer


  3. Posts : 18
    Windos 7 x64
    Thread Starter
       #3

    I added file generated by program from the link you gave me.

    Thank you,

    N

    edit if it means something on BSOD was message if I remeber correctly
    SYSTEM_SERVICE_EXCEPTION
    Last edited by niki999; 17 Oct 2010 at 13:55.
      My Computer


  4. Posts : 11,840
    64-bit Windows 8.1 Pro
       #4

    Still corrupt.. navigate to c:/windows/minidump and delete everything... then enable driver verifier to generate a new one..


    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
      My Computer


  5. Posts : 18
    Windos 7 x64
    Thread Starter
       #5

    I did what you said and after restart I got first BSOD before windows log on screen

    it was IRQL_NOT_LESS_OR_EQUAL at the end there was 0A error code

    then I restarted again and I went to logon screen when I hit to logon as user again BSOD but there was no message what so ever apart 1E...

    I got that loop two times in the row I am attaching mini dumps.

    Thank you,
    N
      My Computer


  6. Posts : 11,840
    64-bit Windows 8.1 Pro
       #6

    Im going to call in the real experts for this one... 2 .dmp files are blaming Pool Corruption, and 2 are blaming acedrv11.sys as the reason for the crash... I wasn't able to find any usefull information on acedrv11.sys ... It may take a bit for an answer, but hang in there!

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff800034c5e36, 0, 0}
    
    Unable to load image acedrv11.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for acedrv11.sys
    *** ERROR: Module load completed but symbols could not be loaded for acedrv11.sys
    Probably caused by : acedrv11.sys ( acedrv11+5363f )
    
    Followup: MachineOwner
    
    -------------
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Tom\Desktop\101710-22978-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`0341f000 PsLoadedModuleList = 0xfffff800`0365ce50
    Debug session time: Sun Oct 17 17:01:19.510 2010 (UTC - 4:00)
    System Uptime: 0 days 0:00:14.336
    Loading Kernel Symbols
    ...............................................................
    ..........................
    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {13c, 2, 1, fffff800034af448}
    
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+126d )
    
    Followup: Pool_corruption
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 000000000000013c, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff800034af448, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800036c70e0
     000000000000013c 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!IopCompleteRequest+c85
    fffff800`034af448 488908          mov     qword ptr [rax],rcx
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    IRP_ADDRESS:  fffff800037a539c
    
    TRAP_FRAME:  fffff88002f9ffb0 -- (.trap 0xfffff88002f9ffb0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000000013c rbx=0000000000000000 rcx=fffff800037a5414
    rdx=fffff88002fa0fb8 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800034af448 rsp=fffff88002fa0140 rbp=fffff88002fa0290
     r8=fffff88002fa0248  r9=fffff88002fa0240 r10=0000000000000002
    r11=fffff800034ae7d0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!IopCompleteRequest+0xc85:
    fffff800`034af448 488908          mov     qword ptr [rax],rcx ds:c440:00000000`0000013c=????????????????
    Resetting default scope
    
    LOCK_ADDRESS:  fffff80003693400 -- (!locks fffff80003693400)
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!ExDeferredFreePool+126d
    fffff800`035c267c 90              nop
    
    SYMBOL_STACK_INDEX:  e
    
    SYMBOL_NAME:  nt!ExDeferredFreePool+126d
    
    FOLLOWUP_NAME:  Pool_corruption
    
    IMAGE_NAME:  Pool_Corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: Pool_Corruption
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!ExDeferredFreePool+126d
    
    BUCKET_ID:  X64_0xA_nt!ExDeferredFreePool+126d
    
    Followup: Pool_corruption
    ---------
      My Computer


  7. Posts : 18
    Windos 7 x64
    Thread Starter
       #7

    I am hanging .

    Thank you,
    N

    btw I do have one program which utilize acedrv11.sys, on internet I found description. I can try to deinstall it.

    Company:Protect Software GmbH Operating System:Windows Vista Description:ProtectDisc x64/x86 Hybrid Driver Acedrv11.sys with description ProtectDisc x64/x86 Hybrid Driver is a driver file from company Protect Software GmbH belonging to product ProtectDisc x64/x86 Hybrid Driver.
    In total there are 1 launchpoints for this file .
    There are 8 different variations of the file in our database and the file is digitally signed from Protect Software GmbH - VeriSign Time Stamping Services Signer - G2
    We do not recommend removing digitally signed files from Protect Software GmbH
      My Computer


  8. Posts : 11,840
    64-bit Windows 8.1 Pro
       #8

    I saw that, but I couldn't find a specific program referenced... let us know how it comes out...
      My Computer


  9. Posts : 18
    Windos 7 x64
    Thread Starter
       #9

    It has something to do with copy protection. I guess it installed with some copy protected program.

    Welcome to Protect Software

    But the thing which eludes me is how come this influance on my GPU. With old GPU all was fine no bsods etc...In either case I will deinstall this. I also saw new NVidia drivers 260.89 tough my old beta drivers bear the same mark...I will notify you how it goes.

    Also what about that Pool_Corruption thing what can I do to solve that problem?

    Thank you,
    N
      My Computer


  10. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #10

    Niki, pool corruption can be caused by bad drivers, software conflicts, hardware conflicts, etc. I find a very outdated driver on your system. Generally speaking, Win 7 does not like older drivers. They can and do cause conflicts, memory corruption and crashes. Both of the pool corruption dumps indicate memory corruption.
    PxHlpa64.sys Mon Dec 10 18:49:01 2007 - Sonic CD/DVD driver (used by many different CD/DVD programs) pxHelp20.sys programs
    Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK
    This will break your CD/DVD program, but can easily be renamed after we've finished.
    I cannot determine the date of acedrv11.sys. If you would, please follow the instructions in this tutorial and upload the files. This will give us a peak into your system and will help us help you.

    https://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

    Tews is spot on in his assessment of
    acedrv11.sys. I suggest that you uninstall this software. Also rename the driver above. Reboot and let's see how your system does. These two actions may solve your problem. Please let us know.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About 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 20:01.
Find Us