New
#11
After a restart following many hours of perfectly normal session on regular mode, the same problem is occurring after login.
After a restart following many hours of perfectly normal session on regular mode, the same problem is occurring after login.
At this point I would have to blame your hard drive. Corruption should not occur this often... well it really shouldn't occur at all.
It's working in regular Windows mode again, but I'm concerned about turning it off in case I end up stuck in Safe Mode again!
Xaixo, I have not personally owned a ssd at this point so my own experience with them is limited to a few friend's machines at this point. Just so you see what I'm seeing in a nutshell though. Here is what the debugger is basically saying.
REGISTRY_ERROR (51)
Something has gone badly wrong with the registry. If a kernel debugger
is available, get a stack trace. It can also indicate that the registry got
an I/O error while trying to read one of its files, so it can be caused by
hardware problems or filesystem corruption.
It may occur due to a failure in a refresh operation, which is used only
in by the security system, and then only when resource limits are encountered.
Arguments:
Arg1: 0000000000000001, (reserved)
Arg2: fffff8a000023120, (reserved)
Arg3: 0000000000cdb000, depends on where Windows bugchecked, may be pointer to hive
Arg4: 0000000000000374, depends on where Windows bugchecked, may be return code of
HvCheckHive if the hive is corrupt.
The reason I'm pointing at the hdd is because of the I/O error that seems to be the source of your problem. It could be the drive it could be the controller. I've never heard of this error occurring repeatedly like you are experiencing it though. In a situation where it didn't turn out some piece of hardware is damaged. I suppose RAM is a possible culprit as well.
Something is interfering with your machine properly shutting down though. It's very early in the morning right now. Let me suck down some coffee and I'll have another more indepth look at this most recent dump file.
Edit:
I do see you have the old ASUS ASACPI.sys
It is possible this could be causing the problem. Considering how badly out of date it is. This is about the last software item on the list I can point too though.
You are fortunate you motherboard is one of the boards ASUS apparently decided to provide win 7 support for. http://www.asus.com/product.aspx?p_i...dbb&templete=2 If you click on the downloads ta and choose win 7 64bit you'll find a number of updated system drivers for you system. I would suggest installing as many of them as you can. Chipset, audio, and SATA especially. If there are multiple items for one update type look at the dates on them and choose the most recent. we'll leave the bios update alone for the moment as I don't see a update specific to your problem. And flashing a bios improperly can kill a system dead. On second thought you should probably start with the SATA since that seems to be the source of our current issue.
Last edited by Maguscreed; 13 Feb 2011 at 08:31.
I seem to have fixed this issue as of yesterday - I booted from my old boot drive (the 1TB WD Caviar Green drive, now used as storage), and then updated the firmware of the SSD. I then booted back on the SSD in Safe Mode and used MSConfig and removed everything apart from Catalyst Control Centre from startup. Used SFC /SCANNOW and then rebooting seems to have done the trick!
Things are back on startup now and are working as they used to.
Thanks for the help, I've updated the related drivers as well. Much appreciated! I'll be back if it dies on me again!