Computer Rebooting BSOD

I have an ASUS Essentio CM5570-AP002.
Windows VistaIntel Pentium E5300 / 2.6 GHz Dual-Core.
I have a Dynex Model DX-400wps power supply (ATX12V) and I installed an AMD Athlon graphics card just over a year ago - not sure which one.
I have had the BSOD off and one for a few months now. The comp won't work one week and then does the next. Right now it is just rebooting over and over - I can't even get into anything. I did an F9 reboot on it about a week ago and it worked for like a day. Then it gave me the blue screen again when Windows was updating the service package from 1 to 2. Got that through the update and when it tried to update other windows things got the screen again. Decided not to update it for now.. not like that did me a lot of good.
I tried taking the AMD graphic card out, but then it wouldn't even turn on.. I'm assuming it turned off the int graphics card it has? And I couldn't figure out how to change that in the BIOS. Here is the recovered message I got previously.. for some reason couldn't find the files .. and well now I can't get to them. Any ideas would be appreciated! I'm in college and can't really afford to get it professionally looked at right now.

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

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC000001D
BCP2: FFFFF8000207A20A
BCP3: FFFFFA6008686A08
BCP4: FFFFFA60086863E0
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini112212-02.dmp
C:\Users\Lollz\AppData\Local\Temp\WER-36644-0.sysdata.xml
C:\Users\Lollz\AppData\Local\Temp\WERCA6F.tmp.version.txt
4 answers Last reply
More about computer rebooting bsod
  1. ejmosse said:
    I have an ASUS Essentio CM5570-AP002.
    Windows VistaIntel Pentium E5300 / 2.6 GHz Dual-Core.
    I have a Dynex Model DX-400wps power supply (ATX12V) and I installed an AMD Athlon graphics card just over a year ago - not sure which one.
    I have had the BSOD off and one for a few months now. The comp won't work one week and then does the next. Right now it is just rebooting over and over - I can't even get into anything. I did an F9 reboot on it about a week ago and it worked for like a day. Then it gave me the blue screen again when Windows was updating the service package from 1 to 2. Got that through the update and when it tried to update other windows things got the screen again. Decided not to update it for now.. not like that did me a lot of good.
    I tried taking the AMD graphic card out, but then it wouldn't even turn on.. I'm assuming it turned off the int graphics card it has? And I couldn't figure out how to change that in the BIOS. Here is the recovered message I got previously.. for some reason couldn't find the files .. and well now I can't get to them. Any ideas would be appreciated! I'm in college and can't really afford to get it professionally looked at right now.

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

    Additional information about the problem:
    BCCode: 1000007e
    BCP1: FFFFFFFFC000001D
    BCP2: FFFFF8000207A20A
    BCP3: FFFFFA6008686A08
    BCP4: FFFFFA60086863E0
    OS Version: 6_0_6001
    Service Pack: 1_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\Mini112212-02.dmp
    C:\Users\Lollz\AppData\Local\Temp\WER-36644-0.sysdata.xml
    C:\Users\Lollz\AppData\Local\Temp\WERCA6F.tmp.version.txt

    The auto restart on system error needs to be turned off. Can you get to safe mode, or have a Windows CD to startup repair ?
    http://pcsupport.about.com/od/fixtheproblem/ss/disable-auto-restart-vista.htm
  2. Sorry for the late reply.. I was on vacation. Just got back and got the auto restart on. I had the computer boot to the last safe boot or whatever its called. I got the minidump files. Seems its something with the hardware.. but I don't know how to figure out what. I really need to figure it out as I use this for school! Thanks for the help!

    I looked at the files in windbg.. here's what it showed me.. 2 different errors


    Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\Mini112412-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
    Machine Name:
    Kernel base = 0xfffff800`0204d000 PsLoadedModuleList = 0xfffff800`02211dd0
    Debug session time: Sat Nov 24 10:52:46.121 2012 (UTC - 5:00)
    System Uptime: 0 days 0:09:14.016
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {0, 8, 1, fffff800020a9c7b}

    Probably caused by : hardware ( nt!KiSwapContext+7b )

    Followup: MachineOwner
    ---------

    0: 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: 0000000000000000, memory referenced
    Arg2: 0000000000000008, 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: fffff800020a9c7b, address which referenced memory

    Debugging Details:
    ------------------


    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002274080
    GetUlongFromAddress: unable to read from fffff80002274160
    0000000000000000 Nonpaged pool

    CURRENT_IRQL: c

    FAULTING_IP:
    nt!KiSwapContext+7b
    fffff800`020a9c7b d102 rol dword ptr [rdx],1

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: chrome.exe

    TRAP_FRAME: fffffa6007b3e800 -- (.trap 0xfffffa6007b3e800)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000007ef6b000 rbx=0000000000000000 rcx=00000000c0000102
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800020a9c7b rsp=fffffa6007b3e990 rbp=fffffa80055db060
    r8=0000000000000000 r9=0000000000007e00 r10=0000000000000009
    r11=fffffa8004f14ca2 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na pe nc
    nt!KiSwapContext+0x7b:
    fffff800`020a9c7b d102 rol dword ptr [rdx],1 ds:00000000`00000000=????????
    Resetting default scope

    MISALIGNED_IP:
    nt!KiSwapContext+7b
    fffff800`020a9c7b d102 rol dword ptr [rdx],1

    LAST_CONTROL_TRANSFER: from fffff800020a722e to fffff800020a7490

    STACK_TEXT:
    fffffa60`07b3e6b8 fffff800`020a722e : 00000000`0000000a 00000000`00000000 00000000`00000008 00000000`00000001 : nt!KeBugCheckEx
    fffffa60`07b3e6c0 fffff800`020a610b : 00000000`00000001 fffffa80`05b2d890 fffffa60`00000000 fffff800`021c0680 : nt!KiBugCheckDispatch+0x6e
    fffffa60`07b3e800 fffff800`020a9c7b : fffffa80`05b2d890 fffffa60`00000000 fffffa60`07b3e9c0 fffffa60`00000150 : nt!KiPageFault+0x20b
    fffffa60`07b3e990 fffff800`020a96fa : 00000000`8000fbc0 00000000`00000000 00000000`00000000 fffffa60`02ccf4eb : nt!KiSwapContext+0x7b
    fffffa60`07b3ead0 fffff800`020afc05 : 00000001`00000000 fffffa80`055db060 00000000`00000000 00000000`0000000a : nt!KiSwapThread+0x13a
    fffffa60`07b3eb40 fffff800`02307c4d : fffffa80`055db060 fffffa80`055db060 00000000`00000001 00000000`00000020 : nt!KeDelayExecutionThread+0x575
    fffffa60`07b3ebf0 fffff800`020a6f33 : fffffa80`055db060 00000000`00000000 ffffffff`ffffd8f0 fffffa80`054f6730 : nt!NtDelayExecution+0x5c
    fffffa60`07b3ec20 00000000`754c3d09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0393ede8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x754c3d09


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiSwapContext+7b
    fffff800`020a9c7b d102 rol dword ptr [rdx],1

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: nt!KiSwapContext+7b

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MODULE_NAME: hardware

    FAILURE_BUCKET_ID: X64_IP_MISALIGNED

    BUCKET_ID: X64_IP_MISALIGNED

    Followup: MachineOwner
    ---------

    0: kd> lmvm hardware
    start end module name


    SECOND ERROR

    Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\Mini112212-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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6001.18538.amd64fre.vistasp1_gdr.101014-0432
    Machine Name:
    Kernel base = 0xfffff800`0205d000 PsLoadedModuleList = 0xfffff800`02222db0
    Debug session time: Thu Nov 22 10:07:30.276 2012 (UTC - 5:00)
    System Uptime: 0 days 0:14:27.155
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1A, {5003, fffff70001080000, 5b3e, 5b400000b678}

    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+14ab7 )

    Followup: MachineOwner
    ---------

    1: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000005003, The subtype of the bugcheck.
    Arg2: fffff70001080000
    Arg3: 0000000000005b3e
    Arg4: 00005b400000b678

    Debugging Details:
    ------------------


    BUGCHECK_STR: 0x1a_5003

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: chrome.exe

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff8000210db37 to fffff800020b2410

    STACK_TEXT:
    fffffa60`08b1e368 fffff800`0210db37 : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`00005b3e : nt!KeBugCheckEx
    fffffa60`08b1e370 fffff800`020c26c7 : 00000000`0016f94c fffffa80`0894ef00 fffffa80`044ebe40 fffffa80`054d6bb0 : nt! ?? ::FNODOBFM::`string'+0x14ab7
    fffffa60`08b1e3c0 fffff800`020b0f99 : 00000000`00000001 00000000`027b0780 fffffa80`054d6b01 00000000`07a0b918 : nt!MmAccessFault+0x26c7
    fffffa60`08b1e4b0 00000000`66e58954 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x119
    00000000`003bf548 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x66e58954


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+14ab7
    fffff800`0210db37 cc int 3

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+14ab7

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4cb71b96

    FAILURE_BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+14ab7

    BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+14ab7

    Followup: MachineOwner
    ---------
  3. Forgot to post this one!

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc000001d, The exception code that was not handled
    Arg2: fffff8000207a20a, The address that the exception occurred at
    Arg3: fffffa6008686a08, Exception Record Address
    Arg4: fffffa60086863e0, Context Record Address

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

    FAULTING_IP:
    nt!KeRemoveQueueEx+4fa
    fffff800`0207a20a 82 ???

    EXCEPTION_RECORD: fffffa6008686a08 -- (.exr 0xfffffa6008686a08)
    ExceptionAddress: fffff8000207a20a (nt!KeRemoveQueueEx+0x00000000000004fa)
    ExceptionCode: c000001d (Illegal instruction)
    ExceptionFlags: 00000000
    NumberParameters: 0

    CONTEXT: fffffa60086863e0 -- (.cxr 0xfffffa60086863e0)
    rax=fffffa8004ee14a0 rbx=0000000417375862 rcx=0000000000000000
    rdx=ffffffe0037e9faa rsi=fffffa800881a800 rdi=00000000000005c9
    rip=fffff8000207a20a rsp=fffffa6008686c40 rbp=fffff800021ab8a0
    r8=0000000000000000 r9=0000000000007e00 r10=000000000000000c
    r11=fffffa8004e9c9d6 r12=fffffa800881a8f8 r13=fffff8000218def0
    r14=fffffa6008686d58 r15=0000000000000001
    iopl=0 nv up ei ng nz na po nc
    cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010286
    nt!KeRemoveQueueEx+0x4fa:
    fffff800`0207a20a 82 ???
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x7E

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

    MISALIGNED_IP:
    nt!KeRemoveQueueEx+4fa
    fffff800`0207a20a 82 ???

    LAST_CONTROL_TRANSFER: from fffff8000207b02a to fffff8000207a20a

    FAILED_INSTRUCTION_ADDRESS:
    nt!KeRemoveQueueEx+4fa
    fffff800`0207a20a 82 ???

    STACK_TEXT:
    fffffa60`08686c40 fffff800`0207b02a : fffffa60`00d8a010 fffff800`02217801 fffff800`021ab800 fffffa80`00000001 : nt!KeRemoveQueueEx+0x4fa
    fffffa60`08686cf0 fffff800`02290403 : fffffa80`080a8120 fffffffe`9a5f4400 fffffa80`0881a800 00000000`00000080 : nt!ExpWorkerThread+0xee
    fffffa60`08686d50 fffff800`020a8572 : fffff800`0218d680 fffffa80`0881a800 fffffa80`04ed2bb0 00000000`00000001 : nt!PspSystemThreadStartup+0x57
    fffffa60`08686d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x12


    FOLLOWUP_IP:
    nt!KeRemoveQueueEx+4fa
    fffff800`0207a20a 82 ???

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!KeRemoveQueueEx+4fa

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    STACK_COMMAND: .cxr 0xfffffa60086863e0 ; kb

    MODULE_NAME: hardware

    FAILURE_BUCKET_ID: X64_IP_MISALIGNED

    BUCKET_ID: X64_IP_MISALIGNED

    Followup: MachineOwner
    ---------
  4. I had the same problem with restarts recently.

    Memory can also be the culprit here so I would test with one stick of ram or ram that works if you have any.

    Check there's not a short in the system somewhere. Check for loose bits of metal floating around the case near the motherboard.

    Disconnect case from pc and start it up with a screwdriver so you can make sure the case isnt the problem.

    Try the hard drive in another computer and see if it still restarts.

    If your card doesn't work, remove the card and reset your cmos. Then get the pc working with minimal hardware attached, and from there its a process of elimination as you add each new part (you're on the right track).

    The problem for me was a faulty case switch which I figured out after replacing the entire computer!
Ask a new question

Read More

Blue Screen Graphics Cards Windows Vista