Random BSOD have no idea what is causing it

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 33
    Windows 7 Ultimate x64
    Thread Starter
       #11

    I have updated my bios and was wondering if this could solve my problems
      My Computer


  2. Posts : 13,354
    Windows 7 Professional x64
       #12

    Time will tell!
      My Computer


  3. Posts : 33
    Windows 7 Ultimate x64
    Thread Starter
       #13

    okay well it's gone a whole night without Bsoding
      My Computer


  4. Posts : 33
    Windows 7 Ultimate x64
    Thread Starter
       #14

    I have been told before that my ram is not compatible with my processor I sold my old ram for like $10 although I might be able to get it back would it be worth me getting it back could that possibly fix my problems
      My Computer


  5. Posts : 13,354
    Windows 7 Professional x64
       #15

    What motherboard do you have? If you get RAM that is on the motherboard manufacturer's CVL, it's your safest bet. You might also try down-clocking your RAM to 1333 MHz.
      My Computer


  6. Posts : 33
    Windows 7 Ultimate x64
    Thread Starter
       #16

    I have the G.skill Ripjaw I just found out that it takes a lower voltage than my old ram so I downed the voltage to the recomended setting from 1.65 to 1.5 but I'm still crashing I'll try the underclocking
      My Computer


  7. Posts : 33
    Windows 7 Ultimate x64
    Thread Starter
       #17

    I'm still having frequent crashes although less often I pulled one stick of ram and started noticing far less frequent crashes and also could a corrupt partition table cause problems I'm guessing it could so I'm backing up all my important data and am gonna try a full format and reinstall
      My Computer


  8. Posts : 13,354
    Windows 7 Professional x64
       #18

    Have you tried running Memtest86 on each of the sticks individually?
      My Computer


  9. Posts : 33
    Windows 7 Ultimate x64
    Thread Starter
       #19

    well my computer has started writing minidumps so here is a upload of them
      My Computer


  10. Posts : 13,354
    Windows 7 Professional x64
       #20

    It still looks like hardware is the problem, have you tested your RAM stick individually?

    ...Summary of the dumps:
    Code:
    
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Wed Sep 12 22:10:55.234 2012 (UTC - 4:00)
    System Uptime: 0 days 0:00:11.561
    Probably caused by : AuthenticAMD
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Tue Sep 11 19:05:17.959 2012 (UTC - 4:00)
    System Uptime: 0 days 14:22:44.910
    *** WARNING: Unable to verify timestamp for RTL8192su.sys
    *** ERROR: Module load completed but symbols could not be loaded for RTL8192su.sys
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : RTL8192su.sys ( RTL8192su+2291e )
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_0xD1_RTL8192su+2291e
    BiosReleaseDate = 08/08/2012
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Tue Sep 11 22:15:49.583 2012 (UTC - 4:00)
    System Uptime: 0 days 3:09:26.910
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    BUGCHECK_STR:  0x7f_8
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  explorer.exe
    FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    BiosReleaseDate = 08/08/2012
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Tue Sep 11 04:42:00.770 2012 (UTC - 4:00)
    System Uptime: 0 days 7:55:21.720
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    BUGCHECK_STR:  0x7f_8
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    BiosReleaseDate = 08/08/2012
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Mon Sep 10 16:40:28.769 2012 (UTC - 4:00)
    System Uptime: 0 days 0:02:49.080
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4534c )
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0xFC
    PROCESS_NAME:  Bitcasa.exe
    FAILURE_BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+4534c
    BiosReleaseDate = 08/08/2012
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Mon Sep 10 18:29:33.099 2012 (UTC - 4:00)
    System Uptime: 0 days 1:22:04.050
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : Ntfs.sys ( Ntfs!NtfsInitializeIrpContext+142 )
    BUGCHECK_STR:  0x1e_c000001d
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  explorer.exe
    FAILURE_BUCKET_ID:  X64_0x1e_c000001d_BAD_IP_Ntfs!NtfsInitializeIrpContext+142
    BiosReleaseDate = 08/08/2012
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Mon Sep 10 18:33:30.119 2012 (UTC - 4:00)
    System Uptime: 0 days 0:03:26.430
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : hardware ( win32k+880bb )
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  explorer.exe
    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
    BiosReleaseDate = 08/08/2012
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Mon Sep 10 20:39:25.143 2012 (UTC - 4:00)
    System Uptime: 0 days 1:16:07.470
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    BUGCHECK_STR:  0x1e_0
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1e_0_nt!KiKernelCalloutExceptionHandler+e
    BiosReleaseDate = 08/08/2012
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Debug session time: Mon Sep 10 20:45:33.543 2012 (UTC - 4:00)
    System Uptime: 0 days 0:05:03.854
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : win32k.sys ( win32k+18aa7c )
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  WerFault.exe
    FAILURE_BUCKET_ID:  X64_0x50_win32k+18aa7c
    BiosReleaseDate = 08/08/2012
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      My Computer


 
Page 2 of 3 FirstFirst 123 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 10:40.
Find Us