locked
BSOD on Shutdown RRS feed

  • Question

  • Hi! Ive been using my PC for 1 1/2 years without prob until i shut it down earlier:

    here is prob:

    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7600.2.0.0.256.1
      Locale ID: 13321

    Additional information about the problem:
      BCCode: 4a
      BCP1: 0000000075092DD9
      BCP2: 0000000000000002
      BCP3: 0000000000000000
      BCP4: FFFFF88006188C60
      OS Version: 6_1_7600
      Service Pack: 0_0
      Product: 256_1

    Files that help describe the problem:
      C:\Windows\Minidump\090713-35427-01.dmp
      C:\Users\TheLims\AppData\Local\Temp\WER-112679-0.sysdata.xml

    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt

    im not really technical so, pls help me the easiest way to fix this pls? Thanks!

    PC is i3 intel, Windows 7, 4gb ram 64 bit

    Saturday, September 7, 2013 7:04 AM

Answers

  • Hi disrupjon,

    Please try the following methods to solve this issue:

    Method 1: Safe mode and clean boot

    1. Safe mode starts Windows with a limited set of files and drivers. Startup programs do not  run in safe mode, and only the basic drivers needed to start Windows are installed. Safe mode is useful for troubleshooting problems with programs and drivers that might not start correctly, or  that might prevent Windows from starting correctly. As for how to start into safe mode, please review this KB article Start your computer in safe mode.
    2. Perform a clean boot.

    A clean boot helps to verify if any third party application services or startup item is causing this issue. For your information, please review this KB article to put the computer in clean boot:

    How to troubleshoot a problem by performing a clean boot in Windows 8, Windows 7, or Windows Vista

    Note: Make sure you put the computer back to Normal Startup once you are done with the troubleshooting.

    Method 2: Run SFC scan.

    System File Checker (SFC) scan can troubleshoot missing or corrupted system files on your computer. For your information, please review the KB article to use SFC scan:

    Use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

    Method 3: Run check disk

    1. Type cmd in the Start, and right-click the Command Prompt, and then click Run as administrator in the below of screen.
    2. Type chkdsk /r /f, and press Enter.

    For your information, please refer to this article Resolving stop (blue screen) errors in Windows 7 to get more help.

    Regards,

    Lany Zhang

    Sunday, September 8, 2013 3:14 PM
  • Update Avast:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)
    Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL.
    Arguments:
    Arg1: 0000000075092dd9, Address of system function (system call routine)
    Arg2: 0000000000000002, Current IRQL
    Arg3: 0000000000000000, 0
    Arg4: fffff88006188c60, 0
    
    Debugging Details:
    ------------------
    
    
    PROCESS_NAME:  AvastSvc.exe
    
    BUGCHECK_STR:  RAISED_IRQL_FAULT
    
    FAULTING_IP: 
    +9a52108f67e
    00000000`75092dd9 ??              ???
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff800030bd5a9 to fffff800030be040
    
    STACK_TEXT:  
    fffff880`06188a28 fffff800`030bd5a9 : 00000000`0000004a 00000000`75092dd9 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`06188a30 fffff800`030bd4e0 : 00000000`00001910 fffffa80`057ad340 00000000`00000000 0000007f`ffffffff : nt!KiBugCheckDispatch+0x69
    fffff880`06188b70 00000000`75092dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
    00000000`0293eba8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75092dd9
    
    
    
    IMAGE_VERSION:  6.1.7600.17017
    
    FAILURE_BUCKET_ID:  X64_RAISED_IRQL_FAULT_AvastSvc.exe_nt!KiSystemServiceExit+245
    
    BUCKET_ID:  X64_RAISED_IRQL_FAULT_AvastSvc.exe_nt!KiSystemServiceExit+245
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_raised_irql_fault_avastsvc.exe_nt!kisystemserviceexit+245
    
    

    Also install the Windows 7 SP1. You don't get any new updates for Windows 7 RTM.


    "A programmer is just a tool which converts caffeine into code"

    Sunday, September 8, 2013 7:07 PM

All replies

  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  
    **
    WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.
    **
    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you dont know what it is you probably are not overclocking.
    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
    If you are overclocking stop.  (chances are if you dont know if you are, you are not)

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    **

    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy (compress them)

    *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.

    **

    Link for how to  upload below.
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.

    * Reboot if changes have been made.

    **

    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    System specs are extremely useful so please include whatever you know.

    **

    Blue Screen View & Who Crashed are often wrong and should only be used in an emergency...

    **

    You can read more about BSODS here
    You can learn how to test your memory here


    Advice offered in good faith. It is your decision to implement same.


    Saturday, September 7, 2013 7:38 AM
  • Thanks for replying!

    I uploaded my dump file here:

    https://skydrive.live.com/redir?resid=ED7D3DDF11552A3C!215&authkey=!AKn8TFH4msxPPzI

    Thanks!

    Saturday, September 7, 2013 8:58 AM
  • Hi disrupjon,

    Please try the following methods to solve this issue:

    Method 1: Safe mode and clean boot

    1. Safe mode starts Windows with a limited set of files and drivers. Startup programs do not  run in safe mode, and only the basic drivers needed to start Windows are installed. Safe mode is useful for troubleshooting problems with programs and drivers that might not start correctly, or  that might prevent Windows from starting correctly. As for how to start into safe mode, please review this KB article Start your computer in safe mode.
    2. Perform a clean boot.

    A clean boot helps to verify if any third party application services or startup item is causing this issue. For your information, please review this KB article to put the computer in clean boot:

    How to troubleshoot a problem by performing a clean boot in Windows 8, Windows 7, or Windows Vista

    Note: Make sure you put the computer back to Normal Startup once you are done with the troubleshooting.

    Method 2: Run SFC scan.

    System File Checker (SFC) scan can troubleshoot missing or corrupted system files on your computer. For your information, please review the KB article to use SFC scan:

    Use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

    Method 3: Run check disk

    1. Type cmd in the Start, and right-click the Command Prompt, and then click Run as administrator in the below of screen.
    2. Type chkdsk /r /f, and press Enter.

    For your information, please refer to this article Resolving stop (blue screen) errors in Windows 7 to get more help.

    Regards,

    Lany Zhang

    Sunday, September 8, 2013 3:14 PM
  • Update Avast:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)
    Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL.
    Arguments:
    Arg1: 0000000075092dd9, Address of system function (system call routine)
    Arg2: 0000000000000002, Current IRQL
    Arg3: 0000000000000000, 0
    Arg4: fffff88006188c60, 0
    
    Debugging Details:
    ------------------
    
    
    PROCESS_NAME:  AvastSvc.exe
    
    BUGCHECK_STR:  RAISED_IRQL_FAULT
    
    FAULTING_IP: 
    +9a52108f67e
    00000000`75092dd9 ??              ???
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff800030bd5a9 to fffff800030be040
    
    STACK_TEXT:  
    fffff880`06188a28 fffff800`030bd5a9 : 00000000`0000004a 00000000`75092dd9 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`06188a30 fffff800`030bd4e0 : 00000000`00001910 fffffa80`057ad340 00000000`00000000 0000007f`ffffffff : nt!KiBugCheckDispatch+0x69
    fffff880`06188b70 00000000`75092dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
    00000000`0293eba8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75092dd9
    
    
    
    IMAGE_VERSION:  6.1.7600.17017
    
    FAILURE_BUCKET_ID:  X64_RAISED_IRQL_FAULT_AvastSvc.exe_nt!KiSystemServiceExit+245
    
    BUCKET_ID:  X64_RAISED_IRQL_FAULT_AvastSvc.exe_nt!KiSystemServiceExit+245
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_raised_irql_fault_avastsvc.exe_nt!kisystemserviceexit+245
    
    

    Also install the Windows 7 SP1. You don't get any new updates for Windows 7 RTM.


    "A programmer is just a tool which converts caffeine into code"

    Sunday, September 8, 2013 7:07 PM