ISATAP and BSOD
This morning, I had my first BSOD since installing Windows 7 beta. It occured while trying to resume from S3 sleep. It was a SYSTEM_SERVICE_EXCEPTION that mentioned haudio.sys.After I restarted the system, I began to see for the first time an error in the Device Manager: Microsoft ISATAP Adapter #3 is not working properly (Code 31). I gather that this error is considered insignificant, but I wonder if it's coincidental that it started occurring right after the unprecedented BSOD. (I rebooted again and the ISATAP error is still there.)Following the crash,I ran a disk check on all my partitions, and no errors were reported. The only updates installed for the past couple of days are Defender definitions. I haven't added any hardware, and the only recently installed software is MS Flight Simulator X (SP2).Any idea what may be going on?GA-P35-DS3Lr2(F8) Q9450 OCZ8500(4GB) GTX260(WDM1.1/181.71) 3xGreenPower(1TB)SATAWinTV1600 GGW-H20L 3007WFP Win6.1.7000x64 Avast4.8.1335
March 10th, 2009 3:14pm

I've found similar errors with the ISATAP adapters. My "fix" is to uninstall the device in Device Manager.In all cases that I've seen this (3 or 4), the uninstalled ISATAP adapter won't come back when you check for hardware changes.- John
Free Windows Admin Tool Kit Click here and download it now
March 13th, 2009 12:33am

BTW - haudio.sys doesn't seem to yield any results when searching the web. If that's the case, it could be malware. If it's actually HDaudio, then it's a driver that's part of the HD audio functions in Windows. The most likely culprit then would be your audio drivers.- John
March 13th, 2009 12:36am

usasma said: I've found similar errors with the ISATAP adapters. My "fix" is to uninstall the device in Device Manager.In all cases that I've seen this (3 or 4), the uninstalled ISATAP adapter won't come back when you check for hardware changes.Yes, that's what I ended up doing. I'm a little puzzled though why this error first showed up a couple of days ago, when I've been running Windows 7 beta for over a month.
Free Windows Admin Tool Kit Click here and download it now
March 13th, 2009 2:23am

usasma said: BTW - haudio.sys doesn't seem to yield any results when searching the web. If that's the case, it could be malware. If it's actually HDaudio, then it's a driver that's part of the HD audio functions in Windows. The most likely culprit then would be your audio drivers.Sorry, typo. It was indeed HDaudio.
March 13th, 2009 2:24am

Further piece of information: the Reliability Monitor shows a ("successful") driver installation for Microsoft ISATAP Adapter immediately after restarting after the BSOD I got upon resuming from S3 on the morning of March 10th. I'm not sure what triggered the driver installation. View Update History does not list it.
Free Windows Admin Tool Kit Click here and download it now
March 13th, 2009 5:02pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics