Various BSODs on a fresh install


  1. Posts : 5
    Windows 7 Professional x64
       #1

    Various BSODs on a fresh install


    Hello,
    I had a lot of trouble with blue screens on this system (as per profile) with a previous installation too, but never got round to dealing with it properly. So now, it's a less than week old installation that I've put very few things on yet, but crashes a *lot* when I try to run games. Does blue screen outside of this, just not as much.

    The error codes vary, but most common is IRQL_LESS_OR_NOT_EQUAL.

    Would be very grateful for advice on this :)
      My Computer


  2. Posts : 5,405
    Windows 7 Ultimate 64bit SP1
       #2

    Hi. :)


    Asus ATK0110 ACPI Utility (a known BSOD maker in Win7). Also a part of the Asus PCProbe and AISuite Utilities yours is old from 2005 no way to be compatible with windows 7.



    Scroll down to the utilities category in this link: http://www.asus.com/Motherboards/AMD...USB3/#download,download and install the updated software\driver,restart.



    Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005)



    Finish with this and post back.
      My Computer


  3. Posts : 5
    Windows 7 Professional x64
    Thread Starter
       #3

    Hi Panais,

    Thanks for getting back to me so quickly! :)

    I've done that, ASACPI.sys is now from July '09. Silly me missing out drivers...
      My Computer


  4. Posts : 5,405
    Windows 7 Ultimate 64bit SP1
       #4

    No you are not silly,it could happen to everyone.


    Now,give it time (1-2 days) work\play as usual and post back with news.
      My Computer


  5. Posts : 5
    Windows 7 Professional x64
    Thread Starter
       #5

    Afraid to say it didn't need a couple of days: I thought I'd do some "stress testing" (e.g. play SW:TOR), and it crashed immediately.

    I didn't catch the error message, but here's the files again.

    As an aside, there was a slightly newer Ai_Suite a bit further up the list (6th entry, V1.06.20), so that's the one I have.
      My Computer


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

    The ASACPI.sys driver still dates back to 2005, please update it by using the Device Manager

    Code:
    ASACPI.sys        fffff880`13073000    fffff880`1307b000    0x00008000    0x42476c4c    28/03/2005 06:30:36
    Test your GPU
    NVIDIA/AMD Video Card - Test with OCCT
      My Computer


  7. Posts : 5
    Windows 7 Professional x64
    Thread Starter
       #7

    Hi yowanvista,

    In Device Manager, the driver for ATK0110 ACPI UTILITY is listed as being ASACPI.sys, dated 16/07/2009.

    Is there another instance of something that uses this that I need to update? If so, where would I actually find it in Device Manager?

    Thanks, just going to test the GPU now.

    Edit: Stupid question time: do I need to remove DirectX 11 and replace it with 9c in order to use GPU: OCCT?

    GPU memtest found no problems over 10 passes.
    Last edited by Miraine; 22 Dec 2011 at 14:05. Reason: Added info
      My Computer


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

    Miraine said:
    Hi yowanvista,

    In Device Manager, the driver for ATK0110 ACPI UTILITY is listed as being ASACPI.sys, dated 16/07/2009.

    Is there another instance of something that uses this that I need to update? If so, where would I actually find it in Device Manager?

    Thanks, just going to test the GPU now.

    Edit: Stupid question time: do I need to remove DirectX 11 and replace it with 9c in order to use GPU: OCCT?

    GPU memtest found no problems over 10 passes.
    No you don't need to remove anything, Direct X11 cannot be removed.

    You will need to perform some additional hardware tests
    HDD: | Seagate
    RAM: RAM - Test with Memtest86+

    Post back with your results.
      My Computer


  9. Posts : 5
    Windows 7 Professional x64
    Thread Starter
       #9

    Hello,

    I haven't tested the HDD, but I've now had the same crashing issues on three separate installations on three separate drives (because when it first started, I thought it was HDD failure, so borrowed another drive to test that theory).

    Previously I'd run memtest86+ for quite a few hours and found no errors. A friend made a comment about testing it "hot", so today after a crash I immediately ran memtest again. After a short while, it started failing constantly (e.g. an error for every single operation). I rebooted and the second time, it only got a few moment into the test before hanging with continuous beep from the internal speaker (no errors reported before it hung though). Screenshots attached, second one is where it hung.

    After this, I switched it off for a bit before running memtest again. It's currently doing that with no errors reported at all so far.

    So, memtest throws up lots of errors if I run it after a crash, and none otherwise.

    I admit, I don't know what this means :)

    UPDATE: After 2 hours of memtest it found a bunch of errors again. For 10 minutes every single address failed with error bits of 00000400, then resumed normal operation for 5 minutes before hanging.

    "Handily" it seems things are getting less stable, as I ran memtest for several hours without errors the previous time (a few months ago). Unfortunately I'm now being dragged off to visit relatives so testing different configurations of slots and sticks will have to wait for a few days.
    Last edited by Miraine; 23 Dec 2011 at 12:01. Reason: Update
      My Computer


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

    This means that you're got defective RAM, please replace your RAM sticks.
      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 14:39.
Find Us