0x0000007A (0X00000003, 0xc0000005, 0x00000800)
This page seems to suggest it's potentially a hard drive error given the 0x0000007A. But do any of those other three strings of numbers provide any additional clues I wonder?
Printable View
0x0000007A (0X00000003, 0xc0000005, 0x00000800)
This page seems to suggest it's potentially a hard drive error given the 0x0000007A. But do any of those other three strings of numbers provide any additional clues I wonder?
Hi AK,
We need some more information:
1. What sort of hardware platform?
2. what operating system (flavour of Windows)?
3. What were you running at the time or trying to do?
4. Using "Event Viewer" what messages are there in the system logs?
:)
The 0xc0000005 looks like it could be some sort of access violation or Registry problem.
1. IBM T60 (there's no escaping these things :eek:)
2. XP Pro SP2
3. Don't know what the last thing the user had run, but it BSOD'ed a couple of times at bootup, then went back to normal. I'm assuming for now it's intermittent.
4. Not much...Most errors I see don't look related. The only error I see that *may* have some relation around the same time period was a failure installing .NET Framework 2.0 SP1. It produced Event ID 10005, Source MsiInstaller.
The user is a Power User, not a local admin, so that would likely trigger any permissions-related errors.Quote:
The 0xc0000005 looks like it could be some sort of access violation or Registry problem.
/edit --
The MsiInstaller error and the reboot happened at almost the exact same time. The eventlog service started at bootup at 3:05, MsiInstaller error at 3:06.
Well,
I guess the first thing to try is running defrag and see if it will work. If there is anything wrong with the drive or file structure it will crap out with an error message.
Then run chkdsk, and see if that will complete. Make sure that you get a report/log. Don't bother with a surface scan, the next step will handle that ;)
Then run the HDD manufacturer's diagnostics with a complete or full scan if that is an option.
By the time you have done that we will know whether you have a hardware problem or it is Billy Windoze :D
EDIT:
Yes, the T60 is a rather popular businessman's laptop so it is hardly surprising.
sfc /scannow
Thats worked for me on HP notebooks with that error before.
id do mfg hdd diags chkdsk then an inplace upgrade