| Author | Thread |
|
|
01/16/2007 05:17:15 PM · #51 |
When troubleshooting, the best way to go is to rule out the simple things first. I do not believe you at the reformat stage.
1. Swapping out the memory modules one at time with a new RAM module to test for faulty memory would be a good and direct place to start.
2. Reviewing any other errors that are occuring will be a recommended idea by looking in the event viewer of the system and application logs. (Start...Run...Eventvwr.msc) You may find clues here for driver issues.
3. Logging in under the "Last Known Good Configuration" would be interesting to test for errors as well.
Just some thoughts...:-)
|
|
|
|
01/16/2007 05:18:48 PM · #52 |
Originally posted by Gordon:
It's actually remarkably straight-forward for a MSKB article. Links to each step and everything.
One of your drivers is freeing previously freed memory.
You debug it by creating a memory dump file, then using the free to download kernel debug tools to work out which driver owns or tried to access the wrong memory, then replace/ repair that driver.
Mind you, if the above seems like babble to you, you don't have much hope of doing the debug yourself. |
ROFL!!!!!!!!!!!! |
|
|
|
01/16/2007 05:24:25 PM · #53 |
Originally posted by DrAchoo:
ok, take your Mac love elsewhere. This is for us hardcore people who aren't afraid of a little driver incompatibility...
My father works for Microsoft...
My brother works for Microsoft...
My sister works for Microsoft...
...I can imagine the grief over getting a stylish piece of art deco with a keyboard. |
...and I work for Microsoft.
|
|
|
|
01/16/2007 05:26:47 PM · #54 |
Originally posted by lesgainous:
Originally posted by DrAchoo:
ok, take your Mac love elsewhere. This is for us hardcore people who aren't afraid of a little driver incompatibility...
My father works for Microsoft...
My brother works for Microsoft...
My sister works for Microsoft...
...I can imagine the grief over getting a stylish piece of art deco with a keyboard. |
...and I work for Microsoft. |
Microsoft has one of the top Mac programming teams in the world with the Mac Business Unit. I'm sure they would appriciate your support by buying a Mac and getting Office X.
|
|
|
|
01/16/2007 05:27:19 PM · #55 |
Originally posted by DrAchoo:
...my computer started in on random Blue Screens of Death.... |
Had this problem once. Replaced the power supply. Problems where solved!
|
|
|
|
01/16/2007 05:29:33 PM · #56 |
Originally posted by chimericvisions:
I may be (fairly) unique in this, but I just generally reformat and start over. I like the feel of a fresh OS without any app clutter lying around.
Then again, I can start from a clean system and have it back to fully functioning in no more than a couple hours. For some people (my dad), this takes days or weeks. |
I'm with you. I don't have patience for a malfunctioning OS.
|
|
|
|
01/16/2007 05:32:44 PM · #57 |
| I started having it a while back too. Updated my HP start up files and no problem since. I sent in one of the error reports and it pointed me to the updated files. |
|
|
|
01/16/2007 05:34:02 PM · #58 |
Originally posted by fotomann_forever:
Originally posted by chimericvisions:
I may be (fairly) unique in this, but I just generally reformat and start over. I like the feel of a fresh OS without any app clutter lying around.
Then again, I can start from a clean system and have it back to fully functioning in no more than a couple hours. For some people (my dad), this takes days or weeks. |
I'm with you. I don't have patience for a malfunctioning OS. |
Yet you use Windows? I don't understand!?!?!?!?
;-) Couldn't resist
|
|
|
|
01/16/2007 05:37:51 PM · #59 |
Well, perhaps I'm onto something. In almost all cases before the BSD, in the application logs I get a series of warnings that say this:
Detection of product '{DDDD0C4B-57F7-4A85-ACF0-DB3FC8F1DBB4}', feature 'NatSpeak' failed during request for component '{D2D7B4BF-6CCA-11D5-8B3F-00105A9846E9}'
NaturallySpeaking is a voice recognition program I have. However, just as I was typing this a few minutes ago I got the BSD again and this time the warning in apps was this:
The COM+ Event System failed to create an instance of the subscriber partition:{41E90F3E-56C1-4633-81C3-6E8BAC8BDD70}!new:{6295DF2D-35EE-11D1-8707-00C04FD93327}. CoGetObject returned HRESULT 8000401A.
mean anything to anybody?
|
|
|
|
01/16/2007 05:40:51 PM · #60 |
| A google indicates that {D2D7B4BF-6CCA-11D5-8B3F-00105A9846E9} is the component ID for agent.exe |
|
|
|
01/16/2007 05:49:07 PM · #61 |
Originally posted by DrAchoo:
Ha, ya, thanks for nothing Gordon... ;)
OK, I have a list of my unsigned drivers. What is the easiest way to turn these off and see if the problem resolves? |
Boot in safe mode. Most blue screens are caused by driver issues. booting in safe mode will keep the drivers from being loaded.
Like others (who probably also have more than a decade of teeth gnashing experience with it) I think you are wasting your time trying to diagnose what is easily remedied by reloading the OS. |
|
|
|
01/16/2007 05:55:15 PM · #62 |
If it's a Windows driver that's the problem you could reinstall Service Pack 2. You should uninstall it first and then reapply the automatic updates to get it back. This would in effect replace a large amount of windows files.
If it is a driver that belongs to a non-Windows package then reinstalling that software may solve the problem.
Before you go down this route or even reinstalling Windows, can you run your "home" profile and confirm that does not have the problem. If it does not then the simple solution would be to delete the "work" profile and create a new one. This should not result in the loss of any software but if you have installed software and made it available only to the "work" profile then you'd need to reinstall those packages. |
|
|
|
01/16/2007 05:59:29 PM · #63 |
Ya, good idea. I'll let it run once more until I get a BSD and then I'll switch to my other profile and let it go for the rest of the day or until I get a BSD on that profile. If no problems on the other one, then I'll just redo the profile and see if that helps.
But wouldn't the culprit program still be out there waiting to be activated?
|
|
|
|
01/16/2007 06:00:15 PM · #64 |
| You haven't ruled out faulty hardware issues (like memory) which would be quick to test prior to a reinstall of the OS. The errors in the event viewer logs should also give event ids which would be interesting to have a look at. |
|
|
|
01/16/2007 06:03:59 PM · #65 |
Originally posted by DrAchoo:
Ya, good idea. I'll let it run once more until I get a BSD and then I'll switch to my other profile and let it go for the rest of the day or until I get a BSD on that profile. If no problems on the other one, then I'll just redo the profile and see if that helps.
But wouldn't the culprit program still be out there waiting to be activated? |
I don't really know about what is stored in a profile and what isn't but a few posters earlier in this thread note that profiles can easily become corrupted. If your "home" profile runs ok then it means one of the following I think (remember this is not my area of expertise)
1. your "work" profile is corrupted (and needs rebuilding)
2. your "home" profile does not load the naughty driver (look for software you run in one but not the other)
3. it's a "red herring" and just luck it doesn't happen (stranger things have happened)
Maybe someone out there know's if a corrupt profile could manifest itself in this manner?
|
|
|
|
01/16/2007 06:26:30 PM · #66 |
Originally posted by hihosilver:
You haven't ruled out faulty hardware issues (like memory) which would be quick to test prior to a reinstall of the OS. The errors in the event viewer logs should also give event ids which would be interesting to have a look at. |
The stuff under the error event is the same as the BSD info I gave above. |
|
|
|
01/16/2007 06:27:49 PM · #67 |
OK, I got it again on the work profile (the COM+ warning coming within one minute before).
I'm going to run under the home profile now and see if I get the BSD. |
|
|
|
01/16/2007 06:30:15 PM · #68 |
| bsOd!! don't pull bsd into your windows nightmare! |
|
|
|
01/16/2007 06:51:14 PM · #69 |
Originally posted by lesgainous:
...and I work for Microsoft. |
I did, 1998-2000. |
|
|
|
01/16/2007 06:55:10 PM · #70 |
Originally posted by chimericvisions:
Originally posted by lesgainous:
...and I work for Microsoft. |
I did, 1998-2000. |
Hey, wait a minute. You are in Portland, OR. I'm sure you aren't doing anything with the snow, so how about hopping over and just fixing everything for me? ;) |
|
|
|
01/16/2007 06:57:05 PM · #71 |
Originally posted by DrAchoo:
Hey, wait a minute. You are in Portland, OR. I'm sure you aren't doing anything with the snow, so how about hopping over and just fixing everything for me? ;) |
Maybe once ODOT lifts the chain restrictions from the freeways and all of the semi-trucks have been air-lifted out of the T-Curves... ;)
Just last night I was at Fred Meyer saying "I want to get some chains so I can go to Hood this year." Of course, I didn't at the time. |
|
|
|
01/16/2007 07:00:40 PM · #72 |
Originally posted by DrAchoo:
OK, I got it again on the work profile (the COM+ warning coming within one minute before).
I'm going to run under the home profile now and see if I get the BSD. |
Jason, Check your email, I PM'ed you.
|
|
|
|
01/16/2007 07:23:43 PM · #73 |
| Since your family works in MS, just get one of them to buy you a copy of Vista from the staff shop for $20 or whatever it is... :-) |
|
|
|
01/16/2007 07:27:09 PM · #74 |
Originally posted by jhonan:
Since your family works in MS, just get one of them to buy you a copy of Vista from the staff shop for $20 or whatever it is... :-) |
You know, even though I could get it for $20, I'm not sure I'm going to upgrade. My view is that each Windows OS is bulkier and bulkier due to compatibility requirements from previous versions. Eventually it will implode and MSFT will be forced (actually they should want) to start over with a parallel OS that does not carry the baggage.
XP works pretty well for me, other than the current issues, it has been rock stable. I'm not sure I want to slow things down even more just for pretty graphics.
|
|
|
|
01/16/2007 07:37:51 PM · #75 |
Could this be the fix?...
 |
|
