When you say "profile" there are two type's, one being "hardware" and the other being "user".
If its that later, it would most likely be a software issue - remember not all install's and more importantly un-install's are created or un-created well...many, and I mean way-way many un-install routines leave behind a matrix of registry entries for all kinds of reasons.
If its the hardware profile, well then it can clearly be a device, "and/or" a software install using a specific device driver not used in the other profile(s).
There is a wealth of info on the BSD codes, and they are clearly worthy of sorting though these issues - which btw - leads me to the MAC comments - "AT LEAST WE GET CODES"....
OK, I'll look into those codes when I get to work tomorrow. I went and picked the laptop up tonight and have used it on my work profile (and I mean "user" profile) for about 90 minutes with no issues.
So this is what I know:
So it works at home and does not work at work.
I did install a program on friday hours before it started freaking out, but I have both uninstalled it and uses system restore to points far before I got it. Could this still be to blame?
It's a "Bad Pool Call" error. I'll get the codes tomorrow. (assuming they come back)
Doc, did you install that "software" on your personal profile, work or the administrator profile? take a look at things loaded during startup, and disable anything related to that new piece of "software" (gee, cant you tell us the name at least?). Try MSCONFIG.
Doc, did you install that "software" on your personal profile, work or the administrator profile? take a look at things loaded during startup, and disable anything related to that new piece of "software" (gee, cant you tell us the name at least?). Try MSCONFIG.
Heh, I was being subtle because it was a DPC tracking program written by a member. I didn't want to cast blame when I don't know at all if it's the culprit. I loaded it on my work profile.
Doc, for simplicity just take a photo of the screen next time you get a BSOD and post it. Will be much easier to diagnose from there...
Oh yea as stated before, NEVER get rid of your Mac, the older CRT imac's make great trash bins if placed on the floor facing up rite, and most of the others are a good height for foot stools and or great door stops ;)
OK, no idea what DPC mod it was, but if it's Firefox specific, may I suggest you uninstall Firefox and reinstall?
Actually, have you tried re-creating your personal user profile? It's quite easy, and I seriously think it may fix the problem, since your work profile works fine. Success rate is high
OK, no idea what DPC mod it was, but if it's Firefox specific, may I suggest you uninstall Firefox and reinstall?
Actually, have you tried re-creating your personal user profile? It's quite easy, and I seriously think it may fix the problem, since your work profile works fine. Success rate is high
Those user profiles can get corrupt easily. I forgot exactly what problem I had (wasn't a blue screen) but that ended up fixing it.
You sure someone didn't load the BSoD screensaver on there messing with you? Because that would be funny LOL. Maybe not for you but somebody would be laughing.
There are lots causes for the blue screen popping up. It can be a poorly written device driver, bad memory, damaged registrys or usage of incompatible versions of DLLs. You'll have to search out the code and see what it is.
thanks silver, yes, most of the important stuff is off and I just off loaded all my pictures last week.
Interestingly it seems to be rock stable at home with my work profile. What's up with that? Could it be some piece of hardward at work like the wireless router? no other computers at work seem to be having problems.
BTW, why can't it be a driver problem if one profile works and the other doesn't? Would the two profiles ever have different drivers? My thinking is regarding things like the network printer at work or the wireless router at work. I don't think my home profile would be loading those drivers when it is loaded. But I could be wrong.
Without seeing the actual stop error code, unfortunately, you are in the position of having to troubleshoot that code once you see it again, but sometimes the end error isn't necessarily the beginning error...like a row of dominoes. When a machine has such a severe error, multiple issues may also exist depending on how well you maintain your machines. If the issue can't be fixed by the troubleshooting the particular stop error, then you'll end up making a checklist of troubleshooting items (some of which are listed here) or taking the machine to a professional for a hands-on look.
This page tells you technical stuff about the error but isn't too clear on what to do to fix it.
OK, too slow, found that yourself. That page scares me a bit too. It does however suggest the error lies in a device driver so I'd run MSCOFIG (Start > Run > type "msconfig") and use the "Diagnostic Startup" option.
You were right.. it's babble. Useful to developers who are actually debugging code, but not to a user. The only important sentence on that page is "Typically, faulty device drivers or device software cause this error message."
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.
Mind you, if the above seems like babble to you, you don't have much hope of doing the debug yourself.
This line should appear in 24-point type at the bottom of the first page of every manual, to alert people that they can avoid wasting time reading further ... : )
I'm running the home profile now to see if I get the same thing. Then I need to start attacking the drivers I guess, but I don't know the best way to proceed on that.
I bet it is related to something you have installed or software you have loaded. Go back thru steps you have taken recently, restore might not help here. I would take the softly, softly approach...ie...no hammer or boots. Get all your stuff off, format with wdclear or similar, and start again. I don't have the patience to sit looking at screens anymore.
If it don't work, junk it and start again. A reformat doesn't always clear everything, but wdclear will put your hard drive back to factory zero.
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.
