TechSpot

BSOD after first time boot up. Please help

By jat0rz
Feb 20, 2010
  1. Route44

    Route44 TechSpot Ambassador Posts: 12,166   +37

    Purchase the RAM that is on the qualified vendor list from Asus for your particular motherboard. Such would be the wise and prudent course of action.

    Don't worry about the drivers. They are W@indows OS drivers and not third party drivers.

    The minidump was another 0xA and another OS driver.
     
  2. jat0rz

    jat0rz TS Rookie Topic Starter Posts: 25

    Alright so I will get QVL Ram, then report back to you once it has arrived and has been installed. That may take about two weeks or so, is that ok?

    Also, if these BSOD's are coming from Windows Drivers, and are consistent every time I power on my computer, how come I shouldn't worry about it? Or is it all RAM related?
     
  3. Route44

    Route44 TechSpot Ambassador Posts: 12,166   +37

    Sure it is okay! We're here to help. I really hope this RAM will straighten everything out.

    Don't worry about the Windows drivers. We see it all the time. The issue isn't with your OS; they are only telling us there is a problem.

    The thing about memory issues is that they can throw out all kinds of error codes and reasons but when it comes right down to it memory is the issue either a) corrupted, b) wrong voltage settings, or c) mismatched RAM between motherboard and RAM or between RAM of different make.

    We've seen these issues here time after time after time.

    * Keep us up-to-date.
     
  4. jat0rz

    jat0rz TS Rookie Topic Starter Posts: 25

    Problem solved, Route44 (so far). After emailing back and forth with G.Skill they looked into my mobo and told me to try 8-8-8-24 1.6v DRAM 1600 settings in the BIOS. I forgot to mention to them that I was not able to change timings manually in the BIOS. I went ahead and googled "M4A78T-E RAM Timing" and found out that the newer BIOS's had a bug where it wouldn't allow you, so I flashed back to and old BIOS and was able to change to the settings they recommended. I ran memtest for a few hours and removed the 1 bad stick. I let it sit overnight, turned it on this morning, and not a single problem has occurred :)

    Bottom line is it was a corrupted stick of RAM, as well as incorrect BIOS settings that was causing these problems. I guesss the 1 time I got a BSOD after taking out the bad RAM before was just a fluke and I should have retried.

    Anyway, thank you very much again for all of your help. I would not have been able to figure this out without you, Route44. I will definitely be coming back to these forums!
     
  5. Route44

    Route44 TechSpot Ambassador Posts: 12,166   +37

    Excellent! And good work on your part. For clarification, with the older BIOS without bug you were able to set the voltage at 1.6, correct?
     
  6. jat0rz

    jat0rz TS Rookie Topic Starter Posts: 25

    Argh... I suppose I spoke too soon. I left the computer off for close to 12 hours today and when I logged into windows a box popped up telling me ATI Catalyst had stopped working... and then BSOD. It was very heart shattering... So lets keep this open and continue trying to figure it out. Here is where we stand:

    My RAM is not defective as I have removed the defective RAM and ran multiple tests on the good stick.

    I have attached the minidump from the latest BSOD.

    As for your question, I could always set the voltage, but I needed to roll back the BIOS to an earlier edition to allow me to manually change the timings. It is a bug that ASUS is currently working on.

    P.S. Thanks for the comment... guess I have to keep up the good work though until we figure this out...
     

    Attached Files:

  7. Route44

    Route44 TechSpot Ambassador Posts: 12,166   +37

    Your error is 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues.

    Unfortunantly it only cited a Windows driver which are too general to be of much help.


    But this code was also in the dump: 0xc0000005: Access Violation error and they are typically due to faulty RAM or device driver, incorrectly written, installed or updated software, malware applications or even Windows security features.
     
  8. jat0rz

    jat0rz TS Rookie Topic Starter Posts: 25

    Sorry I have not been around recently, have been pretty busy but have also been messing around with the computer. Without fail, every single time I turn my computer on for the first time after being turned off for more then a few hours (if I turn it off for an hour, then back on, it runs fine), my computer crashes within the first few minutes of loading the windows login screen. The only way to keep it from repeating is to hold my power button until the computer shuts off, then turn it back on. The blue screen error message is always different, however, it always points to this driver:

    ntoskrnl.exe

    I have google'd it and have read many different posts regarding it, however, after trying some of the things, I still have the same issue.

    Windows repair finds no errors.

    Any ideas? Again, I am running Windows 7 Professional.
     
  9. Route44

    Route44 TechSpot Ambassador Posts: 12,166   +37

    That is a core Windows driver and I would have suggested a repair but you've already done that.

    How does your memory voltage look? Has Asus fixed that BIOS bug yet?
     
  10. jat0rz

    jat0rz TS Rookie Topic Starter Posts: 25

    No news on the BIOS bug yet... voltage is still sitting at 1.6 and 8-8-8-24 timing as suggested by G Skill's rep.

    A core Windows driver eh? So... if I cannot run repair because "your start up is running perfect" what else could I do? I am guessing I cannot delete this driver?
     
  11. Route44

    Route44 TechSpot Ambassador Posts: 12,166   +37

    No, not the driver listed! :) ntoskrnl.exe is is central to your OS. Here is the thing to keep in mind about OS drivers: They more point to the fact that there is an issue rather than they themselves are causing the issue.

    There are of course exceptions and certainly OS corruptions do occur.

    Have you run a harddrive diagnostic yet?
     
     
  12. jat0rz

    jat0rz TS Rookie Topic Starter Posts: 25

    I ran an HD Diagnostic program and everything came back fine. Figured I would update you. Within the last few days the BSOD has been happening randomly, not just after first power up. In the middle of doing anything, whether it be playing a game, or surfing the net, I get a "Memory_Management" bsod, that always points to "ntoskrnl.exe We have already ran Memtest86 several times, changed the voltage and timing settings, ran hard drive diagnostics, disabled//uninstalled several programs.... so what is next?
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.