Windows 7 64 Bits BSOD

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Kaynos, Jul 5, 2010.

  1. Kaynos

    Kaynos New Member

    Joined:
    Jul 5, 2010
    Messages:
    10
    Likes Received:
    0
    Just had a blue screen of death while playing WOW. This is what i gathered from the Even viewer, anyone can help me figure out what's caused this ?

    Log Name: System
    Source: Microsoft-Windows-Kernel-Power
    Date: 05/07/2010 2:10:19 PM
    Event ID: 41
    Task Category: (63)
    Level: Critical
    Keywords: (2)
    User: SYSTEM
    Computer: Y-PC
    Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
    <EventID>41</EventID>
    <Version>2</Version>
    <Level>1</Level>
    <Task>63</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000002</Keywords>
    <TimeCreated SystemTime="2010-07-05T18:10:19.005211400Z" />
    <EventRecordID>6712</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>Y-PC</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    <EventData>
    <Data Name="BugcheckCode">59</Data>
    <Data Name="BugcheckParameter1">0xc0000005</Data>
    <Data Name="BugcheckParameter2">0xfffff80002898c23</Data>
    <Data Name="BugcheckParameter3">0xfffff8800615f840</Data>
    <Data Name="BugcheckParameter4">0x0</Data>
    <Data Name="SleepInProgress">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
    </EventData>
    </Event>
     
  2. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Hi.

    Please navigate to C:\Windows\Minidump to copy the .dmp files in there to any other folder. Then zip them up and attach to a post using the paperclip above where you type, in advanced mode reply. We will have a look at the errors for you this way and should be on to fixing this up for ya.
     
  3. Kaynos

    Kaynos New Member

    Joined:
    Jul 5, 2010
    Messages:
    10
    Likes Received:
    0
    Ok thanks, i just attached the file to this reply.
     

    Attached Files:

  4. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [E:\Temp\Rar$DI00.304\070510-13946-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02819000 PsLoadedModuleList = 0xfffff800`02a56e50
    Debug session time: Mon Jul  5 14:09:32.237 2010 (UTC - 4:00)
    System Uptime: 0 days 3:18:15.186
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff80002898c23, fffff8800615f840, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff80002898c23, Address of the instruction which caused the bugcheck
    Arg3: fffff8800615f840, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nt!IoGetRelatedDeviceObject+43
    fffff800`02898c23 488b4038        mov     rax,qword ptr [rax+38h]
    
    CONTEXT:  fffff8800615f840 -- (.cxr 0xfffff8800615f840)
    rax=0000000000000000 rbx=0000000000000045 rcx=fffffa80045cb4a0
    rdx=fffffa80045cb4a0 rsi=fffff880061605d0 rdi=0000000000000000
    rip=fffff80002898c23 rsp=fffff88006160218 rbp=fffff80002b8d1d0
     r8=fffffa80044d2010  r9=fffff80002a03e80 r10=fffffa80039fb090
    r11=0000000000000001 r12=fffffa80045cb3e0 r13=fffffa80045cb4a0
    r14=0000000000000001 r15=fffffa8004a11040
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    nt!IoGetRelatedDeviceObject+0x43:
    fffff800`02898c23 488b4038        mov     rax,qword ptr [rax+38h] ds:002b:00000000`00000038=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  explorer.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002898c23
    
    STACK_TEXT:  
    fffff880`0615ef78 fffff800`02888b69 : 00000000`0000003b 00000000`c0000005 fffff800`02898c23 fffff880`0615f840 : nt!KeBugCheckEx
    fffff880`0615ef80 fffff800`028884bc : fffff880`0615f1c0 fffff800`02860e65 fffff800`029e7780 fffff880`06160580 : nt!KiBugCheckDispatch+0x69
    fffff880`0615f0c0 fffff800`028af2ed : fffff800`02aab82c 00000000`00000000 fffff800`02819000 fffff880`0615ffd8 : nt!KiSystemServiceHandler+0x7c
    fffff880`0615f100 fffff800`028b6950 : fffff800`029d91b0 fffff880`0615f178 fffff880`0615ffd8 fffff800`02819000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`0615f130 fffff800`028c38df : fffff880`0615ffd8 fffff880`0615f840 fffff880`00000000 00000000`00000000 : nt!RtlDispatchException+0x410
    fffff880`0615f810 fffff800`02888c42 : fffff880`0615ffd8 00000000`00000045 fffff880`06160080 fffff880`061605d0 : nt!KiDispatchException+0x16f
    fffff880`0615fea0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiSystemServiceHandler+7c
    fffff800`028884bc b801000000      mov     eax,1
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!KiSystemServiceHandler+7c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb
    
    FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c
    
    BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c
    
    Followup: MachineOwner
    ---------



    Alrighty. You have got yourself a 0x3b error. This is generally caused by two things, one being the video card driver and the other being the antivirus in use. Your video card driver is definitely not the problem because I see it is from June 7, 2010 and that's great.

    Please uninstall your Avast which has high probability of causing the problem. Here is a special tool to do so:

    AV Uninstallers - Windows 7 Forums

    I highly recommend installing MSE as a replacement because it's free, uses very low resources and never under any circumstances is the cause of bsod.

    -----

    I am guessing here that you have an Asus motherboard. This driver is known to cause problems occasionally and needs to be updated to latest from Asus' website for your motherboard.

    Code:
    ASACPI   ASACPI.sys   Sun Mar 27 22:30:36 2005
    What you need to look for is under downloads section, then utilities. The actual utility that needs an update goes by different names depending on the board.

    If you'd like help, please tell me which motherboard you have. You can use CPU-Z to find out if you don't know.

    It may be the ATK0110 Utility or even other.

    Good luck and please keep us updated.
     
  5. Kaynos

    Kaynos New Member

    Joined:
    Jul 5, 2010
    Messages:
    10
    Likes Received:
    0
    My Mobo is an Asus P5K-SE, however on the ASUS website they dont show any drivers for Windows 7... should i install the Vista 64 bits driver ? And what file i need to download to get the latest ASACPI.SYS file ?
     
  6. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Here attached to my post is what you need to install. It is for Windows 7 and was found on your motherboard site. It didn't have a Windows 7 section, true, but this actual driver says for Windows 7 so that's cool.

    Extract it then go into the MB Win7 ATK/64 folder. Double click on AsAcpiIns.exe to install the new driver.
     

    Attached Files:

  7. Kaynos

    Kaynos New Member

    Joined:
    Jul 5, 2010
    Messages:
    10
    Likes Received:
    0
    It doesnt work. When i click the installer i see a dos window flash on the screen then nothing, it doesnt ask to reboot or anything, so i did reboot anyway, go in device driver, mobo it still shows the 2006 driver. If i try to manually updating it by browsing to the driver directory and choosing the .INF file in the 64 bits folder i get a popup saying : The folder you specified doesnt contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based system.

    So it seems i cant get rid of that old 2006 driver....
     
  8. Captain Jack

    Captain Jack Extraordinary Member

    Joined:
    Mar 6, 2010
    Messages:
    1,952
    Likes Received:
    139
    Hello !!

    ASACPI.SYS is well known for BSOD and it belongs to Asus Utilities so i would recommend to uninstall all the Asus related utilities like PC Probe etc. then go to
    C:\Windows\System32\Drivers located ASACPI.SYS and rename it to ASACPI.old then reboot the System once. Because even in Asus website they mention that those utilities are not important for the working of the PC.

    Hope this helps,
    Captain
     
  9. Kaynos

    Kaynos New Member

    Joined:
    Jul 5, 2010
    Messages:
    10
    Likes Received:
    0
    Hi !
    I checked the directory you specified and i see the ASACPI.SYS file but i dont think it's the one currently loaded cause it shows a 2009 date, that file getting loaded on startup must be somewhere else, but doing a search found nothing.
     
  10. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    This is from the dump. ASACPI.SYS is at C:\Windows\System32\drivers with a date of March 27, 2005.

    Code:
    fffff880`03d4c000 fffff880`03d54000   ASACPI     (deferred)             
        Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
        Image name: ASACPI.sys
        Timestamp:        Sun Mar 27 22:30:36 2005 (42476C4C)
        CheckSum:         00003C77
        ImageSize:        00008000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    
     

Share This Page

Loading...