ar1stotle wrote:Are you doing anything specific when it happens or does it seem to be pretty random? You might want to try just running a chkdsk /F, as sometimes the hard drive just gets corrupt data which makes Vista act terrible.
It's been pretty random.
Grav!ty wrote:I think try finding new chipset drivers Larry. That error message you're getting can also be caused by a damaged swap file (virtual memory) or mismatched RAM. It can also be a hard drive going bad. Do you have identical memory sticks in the system? Probably the easiest thing to check is the swap file. I'll boot to Vista in a bit a see how to delete it and and then recreate it.
It is a brand new laptop -- I've only had it 2 weeks -- so I hope it's not the hard drive going bad. I assume the memory sticks are identical. I haven't changed anything.
Grav!ty wrote:You can delete the swap file by going to right click Computer>Properties>Advanced>Performance>Settings>Advanced>Virtual Memory>Change
From there Uncheck Automatically manage, select No paging file>Set and then follow the steps from there and OK out of the Properties.
You then need to reboot and go back there and select Automatically manage again and reboot to get a fresh page file created.
EDIT: I see ar1stotle also suggests the HDD
JabbaPapa wrote:It was often the case when I have had a new Vista setup, that I would get a few BSODs during the first 1-2 weeks before it settled down.
One good thing about the OS is that it automatically sends an error message to MS about the crash, and more than once I have had feedback appear on my desktop which has helped to resolve certain issues.
Vista is more stable than XP despite some common suggestions to the contrary, however some BSODs can be caused by software conflicts, usually involving software that is both written originally for XP and running continuously in the background. 3rd party firewall and AV software spring naturally to mind, but they are not the only potential culprits.
But the most likely cause of Vista BSODs is that it's still a relatively new system, and that data indexing and system optimisation tasks are still ongoing which can cause I/O conflict in some cases and therefore BSOD.
I sure hope your first statement is the case. It does make sense.
Since you mentioned it...I am a little confused about the "sending to MS" dialog. It does not have the option "send now." Only "check later" or you can cancel it. Am I supposed to get some kind of message back? Because every time this dialog box has come up but I never get anything back afterward. I haven't gotten any feedback.
I hope it's just "settling in," as it were.
EDIT: I just deleted/rebuilt the swap file.
I'll see if it happens again and then I'll run chkdsk /F if it does.