Acpi.sys BSOD Please Help!

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by alecstheone, Jan 16, 2013.

  1. alecstheone

    alecstheone New Member

    Joined:
    Aug 1, 2011
    Messages:
    30
    Likes Received:
    0
    Hello guys!

    I recently got 2 BSOD referring to Acpi.sys. I couldn't found out what were causing these BSOD's and I'm asking for Your support. Just before the BSOD appears, the PC is sluggish.

    My computer is a DELL PRECISION T5500, hex core processor XEON 5675, video card: Quadro 4000, 12GB RAM ECC, 1.5 TB HDD and Im running Windows 7-64 bit

    I have the latest drivers.

    Here's the link of the uploaded BSOD's.

    Minidump.rar

    If someone can detect the cause I'll be very grateful!

    Thank You very much!
     
  2. jcgriff2

    jcgriff2 Honorable Member
    Microsoft MVP

    Joined:
    Sep 12, 2009
    Messages:
    195
    Likes Received:
    29
    Hi -

    Is this a fresh OS install?

    Windows 7 Service Pack 1 needs to be installed along with other outstanding Windows Updates -

    www.update.microsoft.com
    Learn how to install Windows 7 Service Pack 1 (SP1)

    One dump named "hardware" as the probable cause. Dumps are incapable of naming the exact piece of hardware that is failing.

    RAM is one possibility here - run memtest86+

    Memory Diagnostics

    Regards. . .

    jcgriff2


    BSOD SUMMARY

    Code:
    [font=lucida console]
    Debug session time: Sat Jan 12 18:08:30.507 2013 (GMT-5)
    Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\011213-48282-01.dmp]
    Built by: 7600.17118.amd64fre.win7_gdr.120830-0334
    System Uptime: 0 days 1:06:01.395
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
    BugCheck D1, {0, 2, 1, fffffa8006d336e0}
    BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000D1]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/url]
    Bugcheck code 000000d1
    Arguments: 
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffffa8006d336e0, address which referenced memory
    BUGCHECK_STR:  0xD1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID:  X64_0xD1_nt!KiPageFault+260
    BiosVersion = V3.11
    BiosReleaseDate = 05/24/2011
    SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
    SystemProductName = MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Debug session time: Sat Jan 12 17:01:01.679 2013 (GMT-5)
    Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\011213-29842-01.dmp]
    Built by: 7600.17118.amd64fre.win7_gdr.120830-0334
    System Uptime: 0 days 0:35:01.567
    Probably caused by : hardware ( nt!MiUnlinkPageFromLockedList+10e )
    BugCheck A, {fffff7ffe275a7c8, 2, 0, fffff80002cf136e}
    BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000000A]IRQL_NOT_LESS_OR_EQUAL (a)[/url]
    Bugcheck code 0000000A
    Arguments: 
    Arg1: fffff7ffe275a7c8, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, 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: fffff80002cf136e, address which referenced memory
    BUGCHECK_STR:  0xA
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
    BiosVersion = V3.11
    BiosReleaseDate = 05/24/2011
    SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
    SystemProductName = MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Debug session time: Fri Jan 11 15:41:49.257 2013 (GMT-5)
    Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\011113-32947-01.dmp]
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    System Uptime: 0 days 12:40:13.771
    Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_UsbMapDpc_Worker+53 )
    BugCheck D1, {fffff880241770c0, 2, 8, fffff880241770c0}
    BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000D1]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/url]
    Bugcheck code 000000d1
    Arguments: 
    Arg1: fffff880241770c0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffff880241770c0, address which referenced memory
    BUGCHECK_STR:  0xD1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_USBPORT!USBPORT_Core_UsbMapDpc_Worker+53
    BiosVersion = V3.11
    BiosReleaseDate = 05/24/2011
    SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
    SystemProductName = MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    
    
             
           [color=#000033]J. C. Griffith, Microsoft MVP (jcgriff2)[/color]   
                 
               [url=http://mvp.microsoft.com/profiles/Griffith][color=#000055][u][url]http://mvp.microsoft.com/profiles/Griffith[/url][/u][/color][/url]   
    
    [/font]
     
  3. alecstheone

    alecstheone New Member

    Joined:
    Aug 1, 2011
    Messages:
    30
    Likes Received:
    0
    It's not a fresh OS install.

    I have Service Pack 1 installed.

    I ran memtest a few months ago so I'm guessing its not from RAM...

    It only happened since 2 days, since I moved my pc in the guestroom and attached it to a LED TV. I changed the resolution from 1280x1024 to 1920x1080. So maybe it's from the graphic card, or (better) from the graphic card drivers.
    As I told You before it happened just after a small lag.

    Isn't there a possibility to extract more (detailed) information from those minidumps?


    Thank You for Your time!
     
  4. GeneralHiningII

    GeneralHiningII Honorable Member

    Joined:
    Sep 21, 2012
    Messages:
    745
    Likes Received:
    7
    May or may not be something wrong with your Graphics Card/Drivers, though for the first stage of debugging I'd blame the drivers (if I had to).

    Many people who post BSOD help threads don't read (and this is a little thing in the back of my mind almost every single time - not that I'm saying that you did the wrong thing) the first thread in the Sub-Forum --- "How to ask for help with a BSOD problem".
    http://windows7forums.com/blue-screen-death-bsod/38837-how-ask-help-bsod-problem.html
    Download the W7F Tool (and install it).
    Grab:
    -- Minidumps
    -- MSINFO 32
    -- SYSINFO
    -- DXDIAG
    Instead of grabbing all (or you could grab them all if you're lazy, but I barely read through the rest)

    Get them all, zip them up and upload it to your original post.
    Through the SYSINFO we can see -
    -- Amount of memory available
    -- Service Pack/Windows Version
    -- Amount of Windows Updates installed, and which ones
    -- Bunch of other stuff
    Through MSINFO32 we can see -
    -- How much space is available on each drive
    -- Possible hardware problems
    -- Possible problems with programs
    -- Bunch of other stuff
    Through DXDIAG we can see -
    -- Your Audio and Graphics Card
    - Name/Hardware Version
    - Driver Version
    - Problems with either/or

    And, of course, the minidumps. I don't have my minidump analyzer (as in the analyzer I usually use, I still have the basic Windows Debugger) with me (for another 8 or 9 days), but I may be able to help there.
     

Share This Page

Loading...