First BSOD 8/25/10 at 8:23p.m.
-
You'll need to be a little more specific in what "slow" means specifically (what you observe and what resmon disk and memory show you), and what actually happens after you press ctrl+alt+del (aka, what does "not slow" mean). I think I understand, but it's always good to describe exactly what is slow and what is not slow - for instance, you say that after waking up from sleep, the computer was slow and unresponsive. You also say you've had extreme slowdowns when playing video at a different date/time, so is that also a total system slowdown? When it's slow, does it take a long time to open Start > Run > resmon or task manager, does perfmon show high amounts of disk or CPU activity during this time? Etc... :)
-
-
I was unable to do anything on the PC when it became slow. Windows 7 suggested I use the basic Aero scheme though while it was happening. When I pressed ctrl+alt+delete the task manager loaded instantly and the slowdown immediately stopped so I was unable to observe the cpu and ram usage from there. When i've had video playback issues as of late only loading the video would be extremely slow and then no audio but all other aspects of my PC worked as usual. Maybe they're unrelated but both started happening in the same time frame.
-
cluberti- if I may please slip a suggestion in.
You got a 0x24:Ntfs.sys BSOD. That often relates to a bad hard drive, corrupted file system, bad page file, and many other things.
I strongly recommend installing these updated nForce drivers: NVIDIA DRIVERS 15.51 WHQL
That should update your outdated nVidia storage drivers.
-
-
Yup, and chkdsk /f on the volume as well. Not sure about CTRL+ALT+DEL yet though, as doing that would do a lot of things, but none of them I can think of would magically free up a slow system. That is really, really odd. I'm sure there's a reason for it, but I'm unsure as to what it would be yet.
Here's a question - do you have a PS/2 keyboard you could attach to the system temporarily?
-
![]()
Yup, and chkdsk /f on the volume as well. Not sure about CTRL+ALT+DEL yet though, as doing that would do a lot of things, but none of them I can think of would magically free up a slow system. That is really, really odd. I'm sure there's a reason for it, but I'm unsure as to what it would be yet.
Here's a question - do you have a PS/2 keyboard you could attach to the system temporarily?
Sorry about the few days that have passed with no response. I do have a PS/2 keyboard somewhere in my house.
Just to go over what i've done over the past few days.
I ran the Windows 7 memory (ram) diagnostic tool. No errors.
Ran chkdsk /f which resulted in 0 errors.
Used my Windows 7 installation disc to upgrade/repair my installation of windows.
Reinstalled my bios.
Updated the drivers for my motherboard as recommended.
No slowdown or BSOD as of yet since the upgrade/repair but 1 error in the event viewer does stick out like a sore thumb.
Event ID - 12
Source HAL
The platform firmware has corrupted memory across the previous system power transition. Please check for updated firmware for your system.
Count 1
FirstPage: 8
LastPage: 8
This error only occurs after the computer has waken from sleep mode.
I've literally attempted to update all drivers and I have no idea if it has done any good as of yet. I do know that nothing i've attempted to update has fixed that event error though.
edit: Suppose I could just never enter hibernation on my PC again considering all of the problems i've had seem to be centered around it but I depend on the service...
-
Well do you *need* to hibernate, or is sleep "good enough"? Sounds like your BIOS isn't entirely ACPI 2.0 compliant, and while sleep works, hibernate doesn't. It wouldn't be the first time I've seen it, for what it's worth.
-
-
Sorry got mixed up a bit, had just woken up myself. I basically just use sleep mode. At any rate that event seemed to start happening on 6/25/10 but wasn't happening daily. I couldn't find any other event that matched the date and time of the first recorded log of the first HAL event.
I do know now though that it has been happening every day since 8/24/10 after exiting sleep mode i've been getting that error in the event viewer. It does seem to coincide with the date of my first BSOD.
edit: Just on a hunch I uninstalled Microsoft Security Essentials and tah-dah. The HAL error has ceased thus far in appearing on the Event Viewer after 2 tests in sleep mode. 1 for 5 minutes and 1 for 10 minutes. Suppose i'll see what happens after the PC has been in sleep mode for several hours after returning from work.
Quote