BSOD/Auto restat pc(random times), is this a memory problem?


  1. Posts : 13
    Windows XP Professional 32bit
       #1

    BSOD/Auto restat pc(random times), is this a memory problem?


    I tried many ways but i can't fix this problem, system always restarting at random time, i cleaned my ram stick and fan but nothing changed.. then BSOD cames up once. I look up the event viewer, in the system i found this:

    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009c (0x00000000, 0xf7723050, 0xb2000000, 0x1040080f). A dump was saved in: C:\WINDOWS\Minidump\Mini072611-06.dmp.


    Please someone help me to fix this problem thanks!
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2
      My Computer


  3. Posts : 13
    Windows XP Professional 32bit
    Thread Starter
       #3

    Re: BSOD/Auto restat pc(random times), is this a memory problem?


    Thanks!
      My Computer


  4. Posts : 13
    Windows XP Professional 32bit
    Thread Starter
       #4

    @yowanvista: i run the exe file as administrator but it says that a password is needed
      My Computer


  5. Posts : 13
    Windows XP Professional 32bit
    Thread Starter
       #5

    Is Windows 7 . . .
    - x86 (32-bit) or x64 ? 32-bit
    - the original installed OS on the system? windows xp professional
    - an OEM or full retail version? OEM
    - OEM = came pre-installed on system
    - Full Retail = you purchased it from retailer

    - What is the age of system (hardware)? almost 1 year
    - What is the age of OS installation (have you re-installed the OS?) i re-install the OS in different vesion, but its also windows xp professional
      My Computer


  6. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #6

    Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that caused BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
    You can use MagicDisc as an alternative.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MACHINE_CHECK_EXCEPTION (9c)
    A fatal Machine Check Exception has occurred.
    KeBugCheckEx parameters;
        x86 Processors
            If the processor has ONLY MCE feature available (For example Intel
            Pentium), the parameters are:
            1 - Low  32 bits of P5_MC_TYPE MSR
            2 - Address of MCA_EXCEPTION structure
            3 - High 32 bits of P5_MC_ADDR MSR
            4 - Low  32 bits of P5_MC_ADDR MSR
            If the processor also has MCA feature available (For example Intel
            Pentium Pro), the parameters are:
            1 - Bank number
            2 - Address of MCA_EXCEPTION structure
            3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
            4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
        IA64 Processors
            1 - Bugcheck Type
                1 - MCA_ASSERT
                2 - MCA_GET_STATEINFO
                    SAL returned an error for SAL_GET_STATEINFO while processing MCA.
                3 - MCA_CLEAR_STATEINFO
                    SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
                4 - MCA_FATAL
                    FW reported a fatal MCA.
                5 - MCA_NONFATAL
                    SAL reported a recoverable MCA and we don't support currently
                    support recovery or SAL generated an MCA and then couldn't
                    produce an error record.
                0xB - INIT_ASSERT
                0xC - INIT_GET_STATEINFO
                      SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
                0xD - INIT_CLEAR_STATEINFO
                      SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
                0xE - INIT_FATAL
                      Not used.
            2 - Address of log
            3 - Size of log
            4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
        AMD64 Processors
            1 - Bank number
            2 - Address of MCA_EXCEPTION structure
            3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
            4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    Arguments:
    Arg1: 00000000
    Arg2: f7723050
    Arg3: b2000000
    Arg4: 1040080f
    
    Debugging Details:
    ------------------
    
       NOTE:  This is a hardware error.  This error was reported by the CPU
       via Interrupt 18.  This analysis will provide more information about
       the specific error.  Please contact the manufacturer for additional
       information about this error and troubleshooting assistance.
    
       This error is documented in the following publication:
    
          - IA-32 Intel(r) Architecture Software Developer's Manual 
            Volume 3: System Programming Guide
    
       Bit Mask:
    
           MA                           Model Specific       MCA
        O  ID      Other Information      Error Code     Error Code
       VV  SDP ___________|____________ _______|_______ _______|______
       AEUECRC|                        |               |              |
       LRCNVVC|                        |               |              |
       ^^^^^^^|                        |               |              |
          6         5         4         3         2         1
       3210987654321098765432109876543210987654321098765432109876543210
       ----------------------------------------------------------------
       1011001000000000000000000000000000010000010000000000100000001111
    
    
    VAL   - MCi_STATUS register is valid
            Indicates that the information contained within the IA32_MCi_STATUS
            register is valid.  When this flag is set, the processor follows the
            rules given for the OVER flag in the IA32_MCi_STATUS register when
            overwriting previously valid entries.  The processor sets the VAL 
            flag and software is responsible for clearing it.
    
    UC    - Error Uncorrected
            Indicates that the processor did not or was not able to correct the 
            error condition.  When clear, this flag indicates that the processor
            was able to correct the error condition.
    
    EN    - Error Enabled
            Indicates that the error was enabled by the associated EEj bit of the
            IA32_MCi_CTL register.
    
    PCC   - Processor Context Corrupt
            Indicates that the state of the processor might have been corrupted
            by the error condition detected and that reliable restarting of the
            processor may not be possible.
    
    BUSCONNERR - Bus and Interconnect Error   BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
            These errors match the format 0000 1PPT RRRR IILL
    
    
    
       Concatenated Error Code:
       --------------------------
       _VAL_UC_EN_PCC_BUSCONNERR_F
    
       This error code can be reported back to the manufacturer.
       They may be able to provide additional information based upon
       this error.  All questions regarding STOP 0x9C should be
       directed to the hardware manufacturer.
    
    BUGCHECK_STR:  0x9C_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  7
    
    DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
    
    PROCESS_NAME:  chrome.exe
    
    LAST_CONTROL_TRANSFER:  from 80705bf7 to 805376ba
    
    SYMBOL_ON_RAW_STACK:  1
    
    STACK_ADDR_RAW_STACK_SYMBOL: fffffffff7723268
    
    STACK_COMMAND:  dds FFFFFFFFF7723268-0x20 ; kb
    
    STACK_TEXT:  
    f7723248  0000ffff
    f772324c  00009200
    f7723250  97908887
    f7723254  8003984d
    f7723258  0000ffff
    f772325c  00009200
    f7723260  7000ffff
    f7723264  f740934e sptd+0xb334e
    f7723268  7000ffff
    f772326c  f740934e sptd+0xb334e
    f7723270  7000ffff
    f7723274  f740934e sptd+0xb334e
    f7723278  8003f120
    f772327c  00000000
    f7723280  8003f128
    f7723284  00000000
    f7723288  8003f130
    f772328c  00000000
    f7723290  8003f138
    f7723294  00000000
    f7723298  8003f140
    f772329c  00000000
    f77232a0  8003f148
    f77232a4  00000000
    f77232a8  8003f150
    f77232ac  00000000
    f77232b0  8003f158
    f77232b4  00000000
    f77232b8  8003f160
    f77232bc  00000000
    f77232c0  8003f168
    f77232c4  00000000
    
    
    FOLLOWUP_IP: 
    sptd+b334e
    f740934e ??              ???
    
    SYMBOL_NAME:  sptd+b334e
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: sptd
    
    IMAGE_NAME:  sptd.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ceba9a1
    
    FAILURE_BUCKET_ID:  0x9C_GenuineIntel_sptd+b334e
    
    BUCKET_ID:  0x9C_GenuineIntel_sptd+b334e
    
    Followup: MachineOwner
    ---------
      My Computer


  7. Posts : 13
    Windows XP Professional 32bit
    Thread Starter
       #7

    Thanks sir
    I deleted the Ultra ISO and nero in my drive C and run the duplexsecure.exe
    hoping for the good result..
    Last edited by px01; 26 Jul 2011 at 21:46. Reason: wrong send
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:45.
Find Us