New
#11
I had the same problem with a desktop PC.
Tell me, is it overclocked? Even if it is just the memory...
Thanks
I had the same problem with a desktop PC.
Tell me, is it overclocked? Even if it is just the memory...
Thanks
6GB - Two brands of stick
Slot 0 2048 MB DDR2400 Micron Tech
Slot 1 1024 MB DDR2400 Hynix Semiconductors
Slot 2 2048 MB DDR2400 Micron Tech
Slot 3 1024 MB DDR2400 Hynix Semiconductors
Not that I already tested the memory using three different tools and have left memtest86+ to run overnight - no errors.
By the way, it still crashes upon sleep/hibernation. The dump after the re-install still refers to ntfs.sys+c9836 with time stamp 7/13/2009 6:20:47 PM. Interestingly, after the re-install, windows gave an message that is is repairing .NET 4.0 after which I had to restart. Evidently, this was not the cause of the crash as it is still crashing (may be the result of the crashes).
Nothing is over-clocked. The computer has been running Vista ultimate for more than two years until the recent failed start up which prompted me to reinstall vista then upgrade to Windows 7 Pro.
Thanks. Interestingly, I changed the power option so as NOT to sleep. Almost to the minute, every 30 minutes it will crash if left idle. As long as you are working with it, it is fine.
Update - I have removed Win 7 Pro and re-installed OEM Vista ultimate. It is working flawlessly. This rules out any possibility of h/w issue.
I am thinking of re-installing Win 7 Pro and see if the error would appear. Any thoughts/suggestions?
You can try upgrading to 7 again and see if the problem continues. If it does try taking a look here Win 7 Crash on Resume from Sleep - Microsoft Answers and see if that helps with your problem
My Windows 7 Pro 64 worked perfectly fine up until an update, at which point it is crashing exactly as described in the thread above. As long as the computer is in use, it never crashes, only if left alone for a few hours, I am assuming it is the switchover to sleep mode that causes the crash but I really have no solid evidence.
GV
I did a clean re-install using a different Win 7 64 bit CD and painstakingly installed all updates. It has been working fine ever since. I am not sure if this had to do with a corrupt version of Windows. Though it is interesting that you had a similar experience.