BSOD! *grrr*

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 9
    Windows 7 Ultimate 64-bit
    Thread Starter
       #11

    Ok,
    ASUS AI Suite V1.05.29 for Windows 32/64bit XP & 32/64bit Vista & 32/64bit Windows 7 - Installed

    btw i wasnt able to install the hotfix (http://support.microsoft.com/kb/935936) you referred me to, wasnt suitable for my system, however it described one of the situations where ive experienced bsod,
      My Computer


  2. Posts : 7
    Windows 7
       #12

    usasma may be onto something here, but I think it may be your RAM. Corsair RAM has been giving a lot of folks issues lately. I have their Ballistix RAM, and have had all sorts of BSODs with it, first randomly in Vista, then a bit more regularly in Windows 7. I'm not sure what it is about Windows 7 that makes it crash, but if you look at reviews on something like Newegg for later model versions of Corsair you'll see all types of folks complaining about their RAM crashing their OS's on them after about 6 to 9 months of use.

    My RAM issues in Windows 7 always went sort of like this: After about 6 months of virtually no issues I'd have my PC powered on for a few days, and then, out of the blue, I'd get a BSOD. Typically this wouldn't even happen under load (though I would have a memory hogging Firefox window up for a couple days). I'd restart the PC without actually booting completely down, just going through the start menu and doing a soft restart there. I'd get another BSOD not long after... sometimes a few hours later. If I completely booted down, then booted back up, I'd be okay for another few days until it would start all over again. Running Memtest86+ I saw some very odd things. If I restarted my system into Memtest with a soft restart after a BSOD I'd see all types of memory errors. If I booted completely down and then booted into Memtest I'd see no memory errors. I thought this was totally bizarre and thought that maybe it wasn't the memory, but after doing a bit of online research this appears to be a common theme among folks having issues with Corsair.

    Two solutions:
    1.) Try swapping out the Corsair for another brand if you have anything laying around just to see if you still get the BSODs. This will help you confirm whether or not it really is the RAM. I did this with some slower OCZ RAM and found I had zero issues with BSODs.
    2.) Corsair is very picky about the timings set in the BIOS. You said you have the timings already manually set, but you might want to experiment a little with the voltage. I had fewer issues with my default timing in Vista, but under Windows 7 I've experimented with the timings and voltage a bit and the system seems to be a bit more stable (knock on wood).
      My Computer


  3. Posts : 8,870
    Windows 7 Ult, Windows 8.1 Pro,
       #13

    I agree with adrift, that particular Ram can be a real pain to get stable. It might be a good idea to try and run a stablity program like Prime Blend to see if the problem shows up. If it shows to be unstable then some voltage adjustments in bios might help. The Auto voltage settings very often just aren't good enough.
      My Computer


  4. Posts : 4
    Windows 7 x64
       #14

    Hi, see this thread, I have found a solution after searching a long time (at least works for me):

    Mystery Problem: Resume from Sleep

    Post #26

    Regards :)
    Last edited by akatarmo; 15 Sep 2009 at 12:00.
      My Computer


  5. Posts : 5,840
    Vista Ult64, Win7600
       #15

    Hi, why did you install this program, if you dont mind me asking you,

    ASUS AI Suite V1.05.29 for Windows 32/64bit XP & 32/64bit Vista & 32/64bit Windows 7 - Installed
      My Computer


  6. Posts : 5,705
    Win7 x64 + x86
       #16

    Something seems to happen when the forum software "simplifies" the link. Here's the text version:
    Code:
    https://www.sevenforums.com/general-discussion/14477-contast-bsods-2.html#post157051
      My Computer


  7. Posts : 5,705
    Win7 x64 + x86
       #17

    jfar - The fileASACPI.SYS from his BSOD file was dated from 2006. That version of the file is a Windows Vista version and it's known to have issues with Windows 7.

    The program that installed it is most likely the Asus AISuite - but there's other Asus tools that seem to use it. So the safest thing was to install the AISuite - which will update the driver to a 2008/9 version (which doesn't have any known issues with Win7)
      My Computer


  8. Posts : 5,705
    Win7 x64 + x86
       #18

    Now that the file is installed - sit back and wait for another BSOD.

    If you don't get one in the next 24 hours, there's hope that we may have fixed it.
    If you don't get one in the next 3 days, then it's probably, hopefully, most likely, etc that we've fixed it.
    If you don't get one in the next week, then it's most likely that we have fixed it - and it probably ain't worth worrying about anymore! :)

    Good luck!
      My Computer


  9. Posts : 5,840
    Vista Ult64, Win7600
       #19

    usasma said:
    jfar - The fileASACPI.SYS from his BSOD file was dated from 2006. That version of the file is a Windows Vista version and it's known to have issues with Windows 7.

    The program that installed it is most likely the Asus AISuite - but there's other Asus tools that seem to use it. So the safest thing was to install the AISuite - which will update the driver to a 2008/9 version (which doesn't have any known issues with Win7)
    Thanks, I just didn't see where that suddenly came up from, and I was going to recommend to the OP NOT to install it because of what you said.
      My Computer


  10. Posts : 9
    Windows 7 Ultimate 64-bit
    Thread Starter
       #20

    Again!


    Ive had my computer running through the night, woke up, was fine for like 4 hours then bam bsod, did a soft restart and immediately after entering windows i got another bsod,

    My RAM issues in Windows 7 always went sort of like this: After about 6 months of virtually no issues I'd have my PC powered on for a few days, and then, out of the blue, I'd get a BSOD. Typically this wouldn't even happen under load (though I would have a memory hogging Firefox window up for a couple days). I'd restart the PC without actually booting completely down, just going through the start menu and doing a soft restart there. I'd get another BSOD not long after... sometimes a few hours later. If I completely booted down, then booted back up, I'd be okay for another few days until it would start all over again. Running Memtest86+ I saw some very odd things. If I restarted my system into Memtest with a soft restart after a BSOD I'd see all types of memory errors. If I booted completely down and then booted into Memtest I'd see no memory errors. I thought this was totally bizarre and thought that maybe it wasn't the memory, but after doing a bit of online research this appears to be a common theme among folks having issues with Corsair.
    And yes adrift! that is exactly my problem, if i run memtest86+ directly after getting a bsod and doing a restart without shutting power off completely i get like 5k+ errors, and if i reboot like 5 times or turn off the power completely i get no errors at all, ive changed the settings a bit now and im going to try it out, unfortunately i have no other ram available to tests it out :\
    Think i should keep on tweaking this ram or simply just return it for another brand/type or the same memory?

    But what causes this type of error? is this a hardware ram problem or is it just the settings?

    Attaching the dumps
      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 14:15.
Find Us