Frequent BSOD's.. at wits end :(

Page 2 of 5 FirstFirst 1234 ... LastLast

  1. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #11

    I looked at all six of your dumps. Five of them blamed memory corruption or memory management and one simply blamed hardware. One of the dumps was a Driver Verifier enabled dump. It was the one that blamed hardware.

    Stop error code 50, PAGE_FAULT_IN_NONPAGED_AREA - usually caused by Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.

    Stop error code 24, NTFS_FILE_SYSTEM -usually causes are Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure.

    Stop error code 1A, MEMORY_MANAGEMENT - usually caused by Device driver, memory, kernel.

    Stop error code C4, DRIVER_VERIFIER_DETECTED_VIOLATION - usually caused by a device driver.

    Stop error code A, IRQL_NOT_LESS_OR_EQUAL - usual causes are Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.

    I still see this driver in your latest dumps:
    ASACPI.sys Sun Mar 27 22:30:36 2005 - Please install the latest ATK0110 Utility for Vista/7 from this link: ASUSTeK Computer Inc.-Support-.

    I also find this outdated driver: anodlwfx.sys Fri Mar 06 05:10:08 2009 - Alpha filter driver, Alpha Networks, Inc, Alpha Networks Inc.. I am guessing this is a wireless or Ethernet adapter driver. Try to update it via your wireless or Ethernet adapter manufactures website.
    Last edited by CarlTR6; 24 Sep 2010 at 11:01.
      My Computer


  2. Posts : 29
    Windows 7 64 Bit Home Premium
    Thread Starter
       #12

    Hi Carl thanks for your time.

    I have since updated that driver and, touch wood, I've had no BSOD's yet. However I have no idea what that Alpha Networks driver is - I use a D-Link adapter, nothing to do with Alpha.

    I'm now however getting a couple of "black screen" errors when using 3D graphics, which reboots itself.
      My Computer


  3. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #13

    That is good news - except for the black screens.

    Alpha networks is a spin off from D-Link. See if you can update your adapter drivers from D-Link. It might have some bearing on your black screens.

    I suspect that ASACPI.sys was the main cause of your BSOD's. The 2005 version is almost guaranteed to cause crashes.
      My Computer


  4. Posts : 29
    Windows 7 64 Bit Home Premium
    Thread Starter
       #14

    Ah ok - well I did infact download drivers direct from D-Link, not using the CD that came with the product. I will poke around to see if I can find any 64bit DWA-140 drivers newer than ones I have.

    Where does this infamous 2005 driver come from? It's a new build system so I can't understand it.
      My Computer


  5. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #15

    That infamous driver belongs to Asus ATK0110 ACPI Utility and is also a part of the Asus PCProbe and AISuite Utilities. You would not believe how many times we have encountered that monster. :)

    The Alpha driver may work; but if you can update it, it would be a lot better.
      My Computer


  6. Posts : 29
    Windows 7 64 Bit Home Premium
    Thread Starter
       #16

    Guys, thanks to you my BSOD's seem to had gone! So thumbs up for your assistance.

    I am occassionally getting black screens now, requiring a hard reboot. This can be in or out of a 3D application. WOuld you have any idea on that? Sorry to push my luck - I know it's the wrong colour screen!

    Edit: Just had a blue screen after installing a few drivers.... have rolled back just in case and will not touch anything for a few days! Had a PAGE_FAULT error.
    Last edited by mrflib; 25 Sep 2010 at 15:40.
      My Computer


  7. Posts : 712
    Windows 7 x64, Windows XP SP3, Fedora
       #17

    Have you run the hardware tests I mentioned in Post #7 yet?
      My Computer


  8. Posts : 29
    Windows 7 64 Bit Home Premium
    Thread Starter
       #18

    Hi Reventon,

    I haven't had a chance to run Prime/Memtest since reinstall - unfortunately a lot of work has come up and I've needed the PC for other things. However, I did run IntelBurnTest - which failed. I was advised this tested CPU and RAM?



    If you think I should still run the tests I can do memtest this evening and run prime overnight?
      My Computer


  9. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #19

    Memtest will take about seven hours. You should run it over night. I am not familiar with the test you ran; but that indicates further testing and that you may well have a problem with the CPU. I just do not know how much trust to put in that test. I do not remember how long I ran Prime (old timers disease).
      My Computer


  10. Posts : 29
    Windows 7 64 Bit Home Premium
    Thread Starter
       #20

    Unfortunately just had another BSOD. Dump attached. I will run memtest now for 8 hours, then get prime going. I suspect prime won't finish as I'll get a BSOD during.
      My Computer


 
Page 2 of 5 FirstFirst 1234 ... 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 04:57.
Find Us