Frequent Random Crashes Win7 X64- Very frustrating

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 7 Ultimate x64,
       #1

    Frequent Random Crashes Win7 X64- First post


    First post

    Hi,

    I am building a new PC. I am seeing a BSOD every 5 minutes. The system boots ok but crashes with in 5 min.

    I have run a memtest on my RAM up till 2 passes and see no errors.

    I have a monitor connected through VGA port and have a USB receiver for wireless mouse and keyboard.

    Processor: Phenom II 560 BE
    MB: MSI 785GM-p45 latest BIOS
    RAM. Patriot 6GB DDR3.
    Power supply: 450W

    I have no clue about what is failing. Please help.

    I have attached a dump file.


    BR,
    Vic
    Last edited by vikas02121; 25 Jan 2011 at 02:03.
      My Computer


  2. Posts : 507
    Windows 7 Ultimate x64 SP1
       #2

    Test your RAM for at least 7 passes.
    RAM - Test with Memtest86+

    Update or remove this driver:
    FLASHSYS64.sys Fri Feb 15 00:00:23 2008 → MSI driver

    Code:
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02816000 PsLoadedModuleList = 0xfffff800`02a53e50
    Debug session time: Sat Jan 22 22:48:05.456 2011 (GMT-8)
    System Uptime: 0 days 0:23:12.814
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    ................................................................
    ............
    Loading User Symbols
    Loading unloaded module list
    ....................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {41287, 73, 0, 0}
    
    Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+42ba5 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041287, The subtype of the bugcheck.
    Arg2: 0000000000000073
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_41287
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  control.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88005432ee0 -- (.trap 0xfffff88005432ee0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000073 rbx=0000000000000000 rcx=00000000000008d6
    rdx=0000000000000200 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8000285ab62 rsp=fffff88005433070 rbp=fffff70001080c20
     r8=fffffa8000acc6b0  r9=00000000000000bd r10=00000000773aa000
    r11=fffff70001080000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac po cy
    nt!MiDeleteAddressesInWorkingSet+0x246:
    fffff800`0285ab62 0000            add     byte ptr [rax],al ds:000b:00000000`00000073=??
    Resetting default scope
    
    MISALIGNED_IP: 
    nt!MiDeleteAddressesInWorkingSet+246
    fffff800`0285ab62 0000            add     byte ptr [rax],al
    
    LAST_CONTROL_TRANSFER:  from fffff80002832b7a to fffff80002886740
    
    STACK_TEXT:  
    fffff880`05432d78 fffff800`02832b7a : 00000000`0000001a 00000000`00041287 00000000`00000073 00000000`00000000 : nt!KeBugCheckEx
    fffff880`05432d80 fffff800`0288482e : 00000000`00000001 0000000f`ffffffff 00000000`00001000 fffff800`029babfe : nt! ?? ::FNODOBFM::`string'+0x42ba5
    fffff880`05432ee0 fffff800`0285ab62 : 00000003`00000000 8f300000`37aae025 fffff700`01080c20 fffff683`ff7f4378 : nt!KiPageFault+0x16e
    fffff880`05433070 fffff800`0285968a : fffffa80`043e2470 fffffa80`00000000 fffff8a0`0000001d fffff880`00000000 : nt!MiDeleteAddressesInWorkingSet+0x246
    fffff880`05433920 fffff800`02b6bdcf : fffff8a0`0b8c1450 fffff880`05433c20 00000000`00000000 fffffa80`04359060 : nt!MmCleanProcessAddressSpace+0x96
    fffff880`05433970 fffff800`02b44635 : 00000000`00000001 fffffa80`039b4101 000007ff`fffae000 00000000`00000000 : nt!PspExitThread+0x92f
    fffff880`05433a30 fffff800`028631db : 00000000`0029b900 00000000`00000001 fffff880`009e9180 fffff800`02b447a8 : nt!PsExitSpecialApc+0x1d
    fffff880`05433a60 fffff800`02863620 : 00000000`773a8490 fffff880`05433ae0 fffff800`02b4474c 00000000`00000001 : nt!KiDeliverApc+0x2eb
    fffff880`05433ae0 fffff800`02885a37 : fffffa80`04359060 00000000`002e5348 fffffa80`00000000 fffffa80`038cca40 : nt!KiInitiateUserApc+0x70
    fffff880`05433c20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+42ba5
    fffff800`02832b7a cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42ba5
    
    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
    ---------
      My Computer


  3. Posts : 7
    Windows 7 Ultimate x64,
    Thread Starter
       #3

    Hi Wish,
    Thanks for the reply.
    I will test the memory.
    How can I remove the FLASHSYS64.sys driver?by uninstalling MSI Live update?

    Regards,
    Vic
      My Computer


  4. Posts : 507
    Windows 7 Ultimate x64 SP1
       #4

    You're welcome..
    Yes uninstall MSI live update , then search for FLASHSYS64.sys in your Hardrive. You may delete it manually or rename into FLASHSYS64.old to make it wont load in the next reboot.
      My Computer


  5. Posts : 7
    Windows 7 Ultimate x64,
    Thread Starter
       #5

    I uninstall MSI live update and searched for the flash..sys file..could not find it. But before I could restart I got a BSOD. I am running a MEMTEST86+ with one of my sticks....will keep you posted....thanks v much..

    BTW I am just curious...what are the chances that BSODs are coming off of bad memory?
      My Computer


  6. Posts : 7
    Windows 7 Ultimate x64,
    Thread Starter
       #6

    Hi Wish,

    I ran MEMTEST on 2 GB stick and I got 2 errors in the 11 and 12th pass. I am attaching a picture of the test screen. Is my DDR3 bad?

    Please help.

    Thanks,
    Vic
      My Computer


  7. Posts : 507
    Windows 7 Ultimate x64 SP1
       #7

    vikas02121 said:
    Hi Wish,

    I ran MEMTEST on 2 GB stick and I got 2 errors in the 11 and 12th pass. I am attaching a picture of the test screen. Is my DDR3 bad?

    Please help.

    Thanks,
    Vic
    Yes, the stick might be bad.
    Also test the other stick individually, after you find a good stick then test it on each slot. Because it is also possible that you have bad motherboard's slot.
      My Computer


  8. Posts : 7
    Windows 7 Ultimate x64,
    Thread Starter
       #8

    Hi Wish,
    Thanks
    Bad news. The second stick passed 24 passes I used that to start the system,now I see even more crashes.
    Can't even get the dump file? Do you think reinstalling windows will help?

    Br, vic
      My Computer


  9. Posts : 507
    Windows 7 Ultimate x64 SP1
       #9

    Hi Vikas,
    Can you login safe mode?
    If the problems persist in safe mode then you may try clean install.
    Clean Install Windows 7
      My Computer


  10. Posts : 7
    Windows 7 Ultimate x64,
    Thread Starter
       #10

    Hi Wish,
    I was able to log in through safe mode. Though it crashed once in safe mode. But it has not crashed the second time.
    I am attaching dump files.
    How can I troubleshoot in safe mode?
    Thanks,
    vikas
      My Computer


 
Page 1 of 2 12 LastLast

  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 11:38.
Find Us