Maybe someone on here can figure this one out, as the 'geniuses' at Asus cannot... I just finished building this new machine, an Asus M4A79T motherboard and AMD 955 quad-core cpu, 8gb ram, running win7 64 bit. I installed their bios updater, and everything went fine. Tried to uninstall it, and it 'said' all was well. The next time I restarted, I got the following messages: "C:\Users\me\AppData\Local\Temp\185809Log.iniss lost" and "C:\Users\me\AppData\Local\Temp\212301Log.iniss lost". I am seeing NO sigh of the AsusSetup files that the error is referring to (as per the upper left corner of the warning). What is 'looking' for this missing file if I uninstalled it, and where can I find it so I can stop it from happening?? Any ideas? I would hate to reinstall just because of this... See screenshots: http://i26.tinypic.com/2q2358n.jpg

start "button" / type config and hit enter / click Startup tab and look down the list to see if something ASUS related is beinhg started - you can probably uncheck it. Hope that helps.

I tried all of the 'obvious' stuff. I'm at a loss on this. I don;t understand why a program that I uninstalled is even there OR looking for a temp log file in the first place???

I tried all of the 'obvious' stuff. I'm at a loss on this. I don;t understand why a program that I uninstalled is even there OR looking for a temp log file in the first place??? Things like that happen simply because the unwise or uninstall instructions fail to remove the actual program startup from the registry.

The references to TEMP folder are a big clue that some one-timecode was intended to execute, or did execute but then failed to disable itself.Look in Task Scheduler. Usually, oem stuff is found in the topmost Task Scheduler Library folder. When I have problems like this, if I find a likely entry, I disable it (as opposed to deleting it). If that solves things, then after a long period where I am convinced,I will delete that entry altogether.Also, check the Task Scheduler Library\Microsoft\Windows\RestartManager folder.

The references to TEMP folder are a big clue that some one-timecode was intended to execute, or did execute but then failed to disable itself. Look in Task Scheduler. Usually, oem stuff is found in the topmost Task Scheduler Library folder. When I have problems like this, if I find a likely entry, I disable it (as opposed to deleting it). If that solves things, then after a long period where I am convinced,I will delete that entry altogether. Also, check the Task Scheduler Library\Microsoft\Windows\RestartManager folder. I looked in Task Scheduler, and see an Asus entry, but nothing 'in' the folder. This is probably because I already got angry enough to sift through the registry and hunt down any Asus entry. There is also no RestartManager folder at all. Now I am having the 'System Interrupts' processes using up 40% of my cpu at intermittent times, for no apparent reason. I assumed this was because of the Asus driver, so I installed it again. No change in the System Interrupt problem, and the two errors came back upon startup. Can these problems be somehow related? What exactly is "system interrupt". I can go to 10 different sites, and get 10 different answers... I was also experiencing an error when trying to open up device manager. It would say something about 'management console' error. I don't recall the error. I had a bad feeling about this 64 bit install from the beginning, as it was 'hanging' at the very first screen you see (just a fancy blue desktop with a cursor). It did this for about 5 minutes, and the install proceeded, hanging again the next screen too with the blue circle staring me in the face. The 32bit install didn't do this at all. Sure, it's fast now that it is finally installed, but you ever just have a 'bad' install that makes you just not feel right about it? I specifically built this thing with a boatload of memory and new components to take full advantage of 64 bit, and now I am regretting it. Another thing is, I am getting really low windows ratings on my graphics cards for some reason - only a 5.9 rating. The rest of the components are 7.0 or higher. This is leading me to believe the 'system interrupt' thing is a driver issue? These are dual 1gb video cards (gigabyte 9600gt silents) and there is no reason they are being rated this low.

I tried all of the 'obvious' stuff. I'm at a loss on this. I don;t understand why a program that I uninstalled is even there OR looking for a temp log file in the first place??? Things like that happen simply because the unwise or uninstall instructions fail to remove the actual program startup from the registry. So then run CCleaner and get rid of the junk files and invalid registry keys! (go to ccleaner.com )Hello! Please reply back, promptly if possible with the results to solutions to your problem!Curious about Win7 min. system requirements?Readme for older ATI graphics card and Windows 7 users - JoelbX