Questions

Blue screen BCCode: f4 problems

+
0 Votes
Locked

Blue screen BCCode: f4 problems

RobynRex
I have been having a blue screen restart my vista computer for a while know. It only mainly happens when I am not using it for a while. Sometimes it does do it when I am using it here is the info.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: f4
BCP1: 00000003
BCP2: 89D92D90
BCP3: 89D92EDC
BCP4: 82052400
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

BCCode: f4
BCP1: 00000003
BCP2: 8996C8B8
BCP3: 8996CA04
BCP4: 81A88400
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

BCCode: f4
BCP1: 00000003
BCP2: 898B4918
BCP3: 898B4A64
BCP4: 81A56400
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1
  • +
    0 Votes
    OH Smeg

    If it is a desktop system replace the BIOS Battery if it is a NB System leave it plugged in for 24 Hours to allow the Smart Socket to charge or if it is a older NB Replace the BIOS Battery.

    You could also try running some diagnostics with something like the Ultimate Boot CD available here to see if there are any other problems.

    http://www.ultimatebootcd.com/download.html

    If it's not related to the Hardware reinstall the OS.

    Col

    +
    0 Votes
    Jacky Howe

    or PM me the last couple of Minidumps. Minidump Files can be found here. C:\WINDOWS\Minidump\Mini******.dmp
    <br><br>
    How to read the small memory dump files that Windows creates for debugging
    <br>
    http://support.microsoft.com/kb/315263
    <br><br>
    To download and install the Windows debugging tools, visit the following Microsoft Web site:
    <br>
    http://www.microsoft.com/whdc/devtools/debugging/default.mspx
    <br><br>
    Instructions on using Windbg.
    <br>
    Open Windbg and select file, Symbol file path and brows to the Symbol folder that you have downloaded and installed Symbols to, select OK.
    <br>
    Close the workpage and save the Workspace information. This should lock in the Symbol path.
    <br>
    Open Windbg and select file and select Open Crash Dump then navigate to the minidump, highlight it and select Open.
    <br>
    There are two ways to use !analyze -v the easiest is to click on !analyze -v under Bugcheck Analysis.
    <br>
    When you have ran the initial dump if you look to the bottom of the screen you will see kd> to the right of that type in !analyze -v and press the Enter key.
    <br>
    Ctrl + a will let you copy the information and paste it into notepad.
    <br>
    Look to the bottom of the page for information like this. This was fixed by updating the Graphics Drivers.
    <br>
    FAULTING_THREAD: 864f6a98
    <br>
    DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
    <br>
    CUSTOMER_CRASH_COUNT: 1
    <br>
    BUGCHECK_STR: 0xEA
    <br>
    PROCESS_NAME: logon.scr
    <br>
    LAST_CONTROL_TRANSFER: from 00000000 to bfef0fea
    <br>
    STACK_TEXT: f6434e6c 00000000 00000000 00000000 00000000 sgiul50!DrvBitBlt+0x585
    <br>
    STACK_COMMAND: .thread 0xffffffff864f6a98 ; kb
    <br>
    FOLLOWUP_IP: sgiul50!DrvBitBlt+585 bfef0fea 75f9 jne sgiul50!DrvBitBlt+0x580 (bfef0fe5)
    <br>
    SYMBOL_STACK_INDEX: 0
    <br>
    SYMBOL_NAME: sgiul50!DrvBitBlt+585
    <br>
    FOLLOWUP_NAME: MachineOwner
    <br>
    MODULE_NAME: sgiul50
    <br>
    IMAGE_NAME: sgiul50.dll
    <br>
    DEBUG_FLR_IMAGE_TIMESTAMP: 3b7dfec7
    <br>
    FAILURE_BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18
    <br>
    BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18
    <br><br>
    <i>Keep us informed as to your progress if you require further assistance.</i>
    <br><br>
    <i>If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as <b>Helpful</b> so that others may benefit from the outcome.
    </i>

  • +
    0 Votes
    OH Smeg

    If it is a desktop system replace the BIOS Battery if it is a NB System leave it plugged in for 24 Hours to allow the Smart Socket to charge or if it is a older NB Replace the BIOS Battery.

    You could also try running some diagnostics with something like the Ultimate Boot CD available here to see if there are any other problems.

    http://www.ultimatebootcd.com/download.html

    If it's not related to the Hardware reinstall the OS.

    Col

    +
    0 Votes
    Jacky Howe

    or PM me the last couple of Minidumps. Minidump Files can be found here. C:\WINDOWS\Minidump\Mini******.dmp
    <br><br>
    How to read the small memory dump files that Windows creates for debugging
    <br>
    http://support.microsoft.com/kb/315263
    <br><br>
    To download and install the Windows debugging tools, visit the following Microsoft Web site:
    <br>
    http://www.microsoft.com/whdc/devtools/debugging/default.mspx
    <br><br>
    Instructions on using Windbg.
    <br>
    Open Windbg and select file, Symbol file path and brows to the Symbol folder that you have downloaded and installed Symbols to, select OK.
    <br>
    Close the workpage and save the Workspace information. This should lock in the Symbol path.
    <br>
    Open Windbg and select file and select Open Crash Dump then navigate to the minidump, highlight it and select Open.
    <br>
    There are two ways to use !analyze -v the easiest is to click on !analyze -v under Bugcheck Analysis.
    <br>
    When you have ran the initial dump if you look to the bottom of the screen you will see kd> to the right of that type in !analyze -v and press the Enter key.
    <br>
    Ctrl + a will let you copy the information and paste it into notepad.
    <br>
    Look to the bottom of the page for information like this. This was fixed by updating the Graphics Drivers.
    <br>
    FAULTING_THREAD: 864f6a98
    <br>
    DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
    <br>
    CUSTOMER_CRASH_COUNT: 1
    <br>
    BUGCHECK_STR: 0xEA
    <br>
    PROCESS_NAME: logon.scr
    <br>
    LAST_CONTROL_TRANSFER: from 00000000 to bfef0fea
    <br>
    STACK_TEXT: f6434e6c 00000000 00000000 00000000 00000000 sgiul50!DrvBitBlt+0x585
    <br>
    STACK_COMMAND: .thread 0xffffffff864f6a98 ; kb
    <br>
    FOLLOWUP_IP: sgiul50!DrvBitBlt+585 bfef0fea 75f9 jne sgiul50!DrvBitBlt+0x580 (bfef0fe5)
    <br>
    SYMBOL_STACK_INDEX: 0
    <br>
    SYMBOL_NAME: sgiul50!DrvBitBlt+585
    <br>
    FOLLOWUP_NAME: MachineOwner
    <br>
    MODULE_NAME: sgiul50
    <br>
    IMAGE_NAME: sgiul50.dll
    <br>
    DEBUG_FLR_IMAGE_TIMESTAMP: 3b7dfec7
    <br>
    FAILURE_BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18
    <br>
    BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18
    <br><br>
    <i>Keep us informed as to your progress if you require further assistance.</i>
    <br><br>
    <i>If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as <b>Helpful</b> so that others may benefit from the outcome.
    </i>