11-15-2008 09:20 AM
11-18-2008 02:05 AM - edited 11-18-2008 02:31 AM
Hate to be the bearing of bad news but I STILL have the bug and it is the latest version. Usually happens when my Vista 32 system is idle. Had to uninstall and go back to AVG. Least it works...
Too bad, this was the version of Norton I really liked the best too. I will keep an eye out in this thread to see when you have really fixed this MAJOR CALAMITY of a bug.
11-18-2008 06:49 AM
Can you please take a look at the Vista "Problem Reports and Solutions" (Under Control Panel / System and Maintenance) for any recent instances of the update causing this issue? There's a link at the bottom of that screen that says "Copy to Clipboard". Can you paste the details here or send them to me in a Private Message?
11-18-2008 12:32 PM
Did Symantec solve the problem - or is still being looked at ?
Solved -means working 100%- all the time
From what I see - I doubt it
11-18-2008 07:44 PM - edited 11-18-2008 07:49 PM
Symantec Service Framework
11/17/2008 3:41 AM
Problem Event Name: InPageError
Error Status Code: c00000b5
Faulting Media Type: 00000003
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 06b2
Additional Information 2: 63291592dbf6c08ad850526800afe1e2
Additional Information 3: 1414
Additional Information 4: 7b696a72c9f7076b2308f9d78cff9db3
Files that help describe the problem
This is the MS Solution...
Follow these steps to troubleshoot problems with your computer's hard disk.
This problem was caused by Windows not being able to open a file on your computer's hard disk. This might be a temporary condition that could go away after restarting your computer, or it could be a more serious problem with your hard disk or its driver.
Mike, I have been down this "give us info and we will fix it" road way too many times before. I keep doing the troubleshooting and rarely does it ever help ME. My last post. Good luck.
11-19-2008 08:48 AM
As the MS information suggests, this error is generally indicitive of a hardware failure:
The specified I/O operation on %hs was not completed before the time-out period expired.
If you would like me to take a look at the associated memory dumps to provide you with more specifics, you can take the steps below. Note however that there's not much the Norton products can do to compensate for a hardware failure.
From the "Problem Reports and Solutions" page (where you got the copy of the text) there should be a link to "View a temporary copy of these files." This will extract the details of the problem to a temporary directory.
Once Windows Explorer opens, select all the files, right click, and select "Send To -> Compressed (zipped) folder".
Copy the new zip file to your desktop. I can provide a place for you to upload it when you're ready.
11-19-2008 08:52 AM - edited 11-19-2008 08:52 AM
you have a faulty hard disk on your computer.
It is quite unfair to blame Norton for that.
11-19-2008 10:06 AM - edited 11-19-2008 10:09 AM
Doh! A bad hard drive. Gee, why didn't I think of that? errr, except I did. Brand new 1 TB drive (1 month old). Ran three separate tests for my hard drive (including chkdsk), all came up clean. Did a complete Vista system reload with the new drive. I ALSO reloaded NIS twice. What are the chances of a bad part of the drive getting the exact same hit three times in a row? ZIP...
The ONLY indication of a hard disk failure according to MS is that a FILE FAILED TO RUN. MS blames it on hardware (only after saying to try a reboot), I blame it on a faulty file. NIS RUNS FINE after a reboot, just like the FIRST PART of MS message says to try. THEN NIS dies when my monitor goes to sleep or the computer has been on idle for a while, just like all these OTHER folks.
BAD HARD DRIVE? Don't think so.
11-19-2008 10:24 AM
I (personally) didn't mention anything about a bad hard drive
The error is indicative of a general "hardware failure" or "hardware timeout". The most common place I've seen this type of error is with smart card readers, though its not limited to those types of devices by any means.
My (best) guess, without seeing where exactly the fault occurred, is that there's an issue between one of our idle tasks that interacts with the file system (i.e. Norton Insight Scan or Idle Full System Scan), and the behaviour of one of the removable or network storage devices attached (i.e. it became disconnected or entered a low power state, and was unable to reconnect, power back on, or otherwise respond to file-system-related reqeusets before the OS timed it out).
Its also possible you have your fixed disc(s) set to spin down after a certain amount of time, and for whatever reason, file-related activity times out. This seems highly unlikely, however.
Unfortuantely, with the information you've provided thus far, I can only guess.
11-19-2008 10:59 AM
Mike, Good reply! I do have a HP Server on the system as well as a networked printer AND a Popcorn hour media server AND a PS3 AND a XBox360 (doubt the last two as they are not on). Drive is always on and no hibernation. I also have an external BlacX ESATA box which is also turned off.
Makes sense. When you are able to rewrite your code to prevent choking and dying because of my hardware not playing nice with your software, let me know and I will certainly try NIS again!
PS I have two other computers that I will be loading the software on, one on this network (with XP) and one on my sons machine in college. Boy, if you think MY network is strange, you should see the mashup my son's housemates have scrubbed together (at least 6 routers, switches, and hubs, 5 to 12 computers running, LAN cables running from floor to floor, temporary Lan hookups hourly, wireless, Linux, XP, Vista, and a blade server). Now AVG works on ALL of our machines. I expect the same from any program that I replace it with.