My only reason for concern about the driver name spelling was to be sure that you did the search on the right one. Were you able to update asio.sys?
I am glad to hear results of SFC and of no BSOD... yet.
As for the formatting... not all that long ago, I too thought that a "format" was a "format".
Regards. . .
jcgriff2
.
Funny thing, I tried doing updates to all the ASUS drivers and software from the ASUS support site just to be sure everything was good because I had problems again. When I tried to run any of the updates, I'd get a BSOD. When as a last resort, I grabbed the cd that came with the mobo to grab the ASUS update program again, if I clicked any setup program on the mobo cd I got a BSOD when the file ran. And each BSOD of course listed an ASUS driver or executable as the culprit.
So I finally took the long way around, formatted the HDD and installed windows 7 again. I'll be sure not to get any programs or drivers from ASUS anymore since I have already flashed the BIOS and chipsets to the latest versions. It's is also interesting to note that a search for daodx.exe turns up nothing on google, and people on the ASUS forums don't know exactly what it is. But it is on the ASUS mobo disk. Can't figure out exactly which program it is, or what it does, though.
Thanks all for the help, it is much appreciated. I was just trying to get around having to reinstall everything again
We'll see how this install works
And some more BSOD's today, 1 during windows update, 1 during an sfc run, 1 during a system restore....all fund stuff.
Help with the debugging is appreciated:)
All four dumps point at memory corruption although it could also be a bad driver affecting the memory
i would run memtest again for as long as possible just to be doubley sure, sometimes bad ram can pass memtest without errors sometimes it takes lots of passes to show errors, i would recommend getting 5 passes as absolute minimum preferably more.
check all your voltages in the bios make sure CPU and Ram are set to proper settings incorrect voltage can cause this issue the board as you have already seen does not always set things correct when auto is used when I setup a new build the first thing I do is load the bios and go over every page and get the settings right if you do not and just go right into installing OS you may end up chasing your tail trying to figure out why things are unstable
The last 4 dump files are essentially the same as the group that jcgriff2 analyzed. Try running Driver Verifier according to these directions:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
I agree with Driver Verifier.
Also could be RAM, but seeing so many references to the page file leads me in the direction of a rogue driver.
BTW - I found drivers belonging to Windows One Care Live in one of the dumps. One Care Live was discontinued on June 30, 2009.
When did you install it? Did you have BSODs prior to installing OCL?Code:MpFilter.sys Wed Jun 10 22:33:21 2009 (4A306CF1) MpNWMon.sys Wed Jun 10 22:33:23 2009 (4A306CF3)
What was the installation source?
OCL --> Windows Live OneCare - Home
Regards. . .
jcgriff2
.
Thanks for all the replies. I understand you guys have more experience than I do, but I'd rather make sure that all my RAM settings are correct since it is all currently auto in BIOS. If incorrect setting are causing the issues, then I think that verifier would always find a problem. Sooner or later, if the RAM setting are the problem, it will fail and whatever was accessing memory when the problem happens would be pointed to as the fault. Waiting for a response from the manufacturer of the RAM.
I have never heard of One Care Live, I do not know how it got on the 'puter. I look at all windows updates and usually only do critical/security ones and not the optional. Windows defender comes with Win7 automatically now, and I have Microsoft Security Essentials. Could those files be associated with those programs now?
Once I have proper RAM settings in BIOS, I will run driver verifier again.
I wish you the best of luck. You obviously do have the right to make the ulimate decision.
Posting here certainly did provide you with several alternate paths.
Please let us know how you make out.
Regards. . .
jcgriff2
.
Quote