BSOD usually on startup. Various error codes including: 0xFFFFFE000000

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 7 Home Premium 64-bit
       #1

    BSOD usually on startup. Various error codes including: 0xFFFFFE000000


    Hi,

    I 'm running the following:
    Aspire Timeline X - 3830T notebook
    System is 1 year old
    Started blue screening pretty soon after I got it. Now blue screens more, maybe every 3rd startup.
    Ran Driver Verifier and attaching that dump.
    Have done memtest several times- no errors, plus full chkdsk test with no errors.
    Did try to download exe in posting guidelines but unavailable.

    Here's one of another one of errors:
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002F87AB5, 0x0, 0xFFFFFFFFFFFFFFFF)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntoskrnl.exe

    more details in text file attached.

    Any help much appreciated!
    BSOD usually on startup. Various error codes including: 0xFFFFFE000000 Attached Files
      My Computer


  2. Posts : 1,314
    Windows 7 64-bit
       #2

    You're saying you had it blue screen shortly after you purchased it and have been dealing with it for an entire year? Why did you not return it for replacement or repair? Did the warranty expire on it yet? My concern is that the system may have came with manufacturing defects and that you've been dealing with a PC with faulty hardware from the beginning.

    The information you provided isn't very definitive. Can you please provide a JCGriff report as instructed here? In addition, you can turn on Driver Verifier just to make sure we aren't dealing with a software bug. When you get to the part where you select which checks to make, do not select Low Resource Simulation, Force Pending I/O Requests and IRP Logging. Restart after everything is finished setting up. If you crash at startup, mash the F8 key during startup until you see the boot menu, then select Safe Mode and then disable Driver Verifier from there. Provide us all resulting crashdumps.

    Since I suspect we're dealing with hardware problems, you can perform a battery of hardware tests as followed:


    RAM: Memtest86+ - 7+ passes
    CPU: Prime95 - Torture Test; Large FFTs; overnight (9+ hours)
    GPU: MemtestCL - Run twice (if any of the tests work on your GPU; ATI cards will need to install the ATI APP SDK as it requires OpenCL)
    Drives: Seatools - All basic tests aside from the Fix all or the advanced ones.

    All of these (excluding MemtestCL) are included in the UBCD if you prefer a Live CD environment (which is the best environment to test hardware on). Note that Prime95 currently does not work on the UBCD. Also, please provide us temps/voltages using HWInfo with Sensors only option checked. Log two 30-minute instances: one for idle, and one for high load.
      My Computer


  3. Posts : 7
    Windows 7 Home Premium 64-bit
    Thread Starter
       #3

    Thanks Vir. I have been overseas since I bought it, so that's why I haven't returned it :)

    I have included the Resources and Performance Test result. It shows an error of missing driver for "unknown device". I don't have anything plugged in, so I'm not sure what this could be. Searching for driver using windows update fails to find update.

    I ran Driver verifier before and it crashes on boot repeatedly, until I booted to safe mode. Dump is in the attached file on the original post. Here is an excerpt:

    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0xC4 (0x0, 0x0, 0x0, 0x0)
    Error: DRIVER_VERIFIER_DETECTED_VIOLATION
    file path: C:\Windows\system32\ntoskrnl.exe

    I am starting with some of these other hardware tests, and will post info from them shortly.
    BSOD usually on startup. Various error codes including: 0xFFFFFE000000 Attached Files
      My Computer


  4. Posts : 1,314
    Windows 7 64-bit
       #4

    I'm sorry, neither of these that you've provided can help us much (I do not see the dump file). Can you please provide a JCGriff Report? Follow all the instructions from the article linked below. That will provide us enough information to work with.

    https://www.sevenforums.com/crashes-d...tructions.html
      My Computer


  5. Posts : 7
    Windows 7 Home Premium 64-bit
    Thread Starter
       #5

    I've attached all the actual files from my minidump directory. The one's before were from whoCrashed. Also I have saved as html performance monitor. I cannot download the BSOD exe from Griff's personal site, probably because I am in China.
    I have run Prime 95, Memtest and Seatools all with no errors.
    BSOD usually on startup. Various error codes including: 0xFFFFFE000000 Attached Files
      My Computer


  6. Posts : 1,314
    Windows 7 64-bit
       #6

    Unfortunately, the crashdumps aren't definitive, despite there being a few that had Driver Verifier running. DV did detect something, but in both cases it blamed your tcpip stack. In, pretty much all of them relate to it. Given that all drivers pertaining to your network interfaces (Intel Wifi/Atheros NIC) are looking pretty stale in age, you'll want to try updating them. Even if the updates appear old, they might be an improvement over the ones currently existing on your system.

    In addition, given that this is possibly onboard network controller we're dealing with, you may wanna also update BIOS and chipset drivers for your motherboard. Update audio drivers as well, as audio and network share the same resources and can cause conflicts with each other if there's bugs in their drivers.

    Otherwise, I cannot figure out much with the information currently given. If your latest crash was when Driver Verifier was on, and I had access to the kernel dump generated from it (MEMORY.DMP in your Windows directory), I have a much better chance at figuring things. Even with the file compressed, I'm not sure uploading a several hundred MB file to a 3rd-party filesharing site will do you any good where you're at right now. If you can, great. But if not, then all I can say is update all your drivers from the Acer website, and if that doesn't resolve your issue, you can probably start blaming hardware (motherboard most likely) for this, especially if it's been a problem you've experienced since you owned the notebook.
      My Computer


  7. Posts : 7
    Windows 7 Home Premium 64-bit
    Thread Starter
       #7

    memory dump from rural china


    Hi thanks for the suggestions, I will work on them. I spend half the day here in rural china getting this up, was a learning experience for me as I mimed in the internet cafe and tried to read chinese dialog windows!

    I was running driver verifier during the crash, and then copied and zipped the file right after. Here is the memory dump. Hope you can see it.

    Share Send / josh_MEMORY.zip
      My Computer


  8. Posts : 7
    Windows 7 Home Premium 64-bit
    Thread Starter
       #8

    Hi Vir,

    Did you get a chance to look at that memory dump? If this is a driver issue I'm guessing a clean install from the recovery partition wouldn't help, would it?

    Thanks
      My Computer


  9. Posts : 1,314
    Windows 7 64-bit
       #9

    Sorry, last week has been considerably busy for me. Analyzing kernel dumps can be a rather intricate process so it'll require some time.

    If it is driver related, a restore from a recovery partition should work, but it's a drastic measure, since it'll involve wiping everything out and resetting it to factory defaults. Have you gone ahead and looked for and updated all the drivers I mentioned in my previous post, as well as the BIOS? To find the appropriate drivers, you'll need to go to the Acer website and find the drivers and BIOS specific to your notebook.
      My Computer


  10. Posts : 7
    Windows 7 Home Premium 64-bit
    Thread Starter
       #10

    Yes I can imagine they would be tricky. I reinstalled all the drivers from the Acer website, and I thought it had maybe fixed the problem: No crases for 5 reboots, usually would crash every 2nd or 3rd. So I ran Driver Verifier since that usually causes a crash.. no crash..then in the last two days started crashing again. I haven't made any modifications since reinstalling the drivers. So the mystery continues...
      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 21:22.
Find Us