Debugger?

[ell]

Hi, I've been googling for two days now, still can't get a handle on these random blue screens, they are so infrequent. I'm leaning towards bad ram or video, but I can't be sure. I ran a complete system stress test for 2 hrs. I've tried swapping the ram, updating drivers, anybody know how to decifer these logs, or point me to a program or site that can teach me???? struggling with this one

 

[JD1248]

Windebug has worked for me in the past. Also you can try to swap out as many components as is possible, one at a time of course.

 

[ell]

thanks! I'm on it, hope it simple to use.

 

[PcTek9]

windebug is not simple. it has over a thousand commands.

Bryce just recently wrote an article about a bluescreen reader he uses that's very good. I think it might have been called "whocrashed" but just read the old articles by bryce on the technibble forum homepage (before you get into the forums)

 

[JD1248]

PcTek, thanks for posting that tip. I haven't used that program yet, so I didn't want to recommend it. And yes Windebug can be hard to use at first, but I think it is worth knowing how to use. MStechnet has a podcast on crash dump analysis that is very good. If my memory serves it's by Mark Russovich. Another tip for blue screen troubleshooting is to boot from live cd and see if computer still crashes.

 

[Tweak]

Usually these two are the main mentioned...

WhoCrashed
http://www.resplendence.com/whocrashed

BlueScreenView
http://www.nirsoft.net/utils/blue_screen_view.html

Sometimes having both is ideal because at times one or the other may work properly.

 

[ell]

Usually these two are the main mentioned...

WhoCrashed
http://www.resplendence.com/whocrashed

BlueScreenView
http://www.nirsoft.net/utils/blue_screen_view.html

Sometimes having both is ideal because at times one or the other may work properly.

I've tried them all now, I like bluescreen view the best, but I still cannot pinpoint my issue, I did find ntoskrnl.exe is involved in just about every one of my dumps, but from what I've found that could be just about anything, thanks everybody for your help! Heres my issue and diagnosis, throw in your opinion-please!

original issue: system caught in blue screen/boot loop

1. my diagnosis after complete system/hardware scans>defective HD>New Hard drive installed

2. week later customer calls with blue screen again
I run diagnostics and find no hardware issues, run memtest 16 hrs suspecting bad ram, drivers look fine in device manager, found a couple infections, ran chkdsk and sfc, performed repair install. no blue screen 3 days, returned to customer.

3. 11 days later, blue screens again! no infections, ran 2 hour system stress test, no problem, then suddenly bsod in windows. Removed 1 stick of ram, boots up fine!(thought I had it) no so fast, moments later another bsod! I pull second ram and swap with my own good one-still blue screen as windows loads. Put original stick back in, it boots, put other stick back in too, set performance to server from workstation,ran chkdsk, uninstalled/reinstalled video, touchpad, audio drivers from hp, it hasn't crashed for 2 days....

 

[Tweak]

Considered the power supply or main-board as a potential problem? Heat doesn't seem likely being in different areas with the same results and neither does peripherals or the power outlet specifically in the home. (which I've seen similar so I mention it) Damaged installation, bad windows update, anything software related you might feel can relate to it somehow? Really just tossing out some ideas here, I really dislike troubleshooting when not in front of the unit, then I find not much can go without a fix, just a matter of time ya know.

 

[rusty.nells]

ntoskrnl.exe is the kernel image. It loads (among other things) the drivers.

 

[ell]

ntoskrnl.exe is the kernel image. It loads (among other things) the drivers.

thats kinda what I've found, so needle in a haystack here, I think what Tweak said about the power supply or mobo is my issue, unfortunetly I lack the skills/tools to pinpoint it, and seeing as it happens so infrequently I don't know how I could. I guess knowing that my customer doesn't want to spend any more $ on it I will just tell him any solution is likely to cost more than its worth. Thanks for your input you guys.

 

[ell]

ntoskrnl.exe is the kernel image. It loads (among other things) the drivers.

Considered the power supply or main-board as a potential problem? Heat doesn't seem likely being in different areas with the same results and neither does peripherals or the power outlet specifically in the home. (which I've seen similar so I mention it) Damaged installation, bad windows update, anything software related you might feel can relate to it somehow? Really just tossing out some ideas here, I really dislike troubleshooting when not in front of the unit, then I find not much can go without a fix, just a matter of time ya know.

He installed something called windows feature pack for storage-IMAPI update for blueray (an xp auto update?) the day before it started crashing again, this thing is not bluray compatible I'm sure, but there aren't any errors in the logs saying it caused any probs.

 

[Tweak]

He installed something called windows feature pack for storage-IMAPI update for blueray (an xp auto update?) the day before it started crashing again, this thing is not bluray compatible I'm sure, but there aren't any errors in the logs saying it caused any probs.

That seems to point to a bit of an older update as mentioned here.

Since it runs for awhile at times I'd look also an AutoRuns and see what I might change that may help and go from there...could help lessen some issues and point toward the problem more-so...although it may very well be hardware in which case this won't matter except to familiarize you with AutoRuns. (which is excellent if you don't already know it well)

 

[ell]

That seems to point to a bit of an older update as mentioned here.

Since it runs for awhile at times I'd look also an AutoRuns and see what I might change that may help and go from there...could help lessen some issues and point toward the problem more-so...although it may very well be hardware in which case this won't matter except to familiarize you with AutoRuns. (which is excellent if you don't already know it well)

I thought it was odd it was installed, I think he was having trouble with his cd drive, I also noted issues he had trying to install office 2000, I'd really like to format and reinstall xp, but since hes already installed all his itunes, office, etc it would be a pain, plus when it blue screened once booting to ubcd I'm thinking hardware, also one of the recent bsod didn't even point to a image causing the crash, like maybe power issue???? I went through all the startups, nothing peculiar there, its too weird. I have the system tweaked to best performance, few startups, avg thats about it. It doesn't crash when its over-loaded, and not when any certain program is started. Maybe now its fixed.....yah right.

 

[Tweak]

I thought it was odd it was installed, I think he was having trouble with his cd drive, I also noted issues he had trying to install office 2000, I'd really like to format and reinstall xp, but since hes already installed all his itunes, office, etc it would be a pain, plus when it blue screened once booting to ubcd I'm thinking hardware, also one of the recent bsod didn't even point to a image causing the crash, like maybe power issue???? I went through all the startups, nothing peculiar there, its too weird. I have the system tweaked to best performance, few startups, avg thats about it. It doesn't crash when its over-loaded, and not when any certain program is started. Maybe now its fixed.....yah right.

Well it sounds more like a stability issue in relation to the hardware at times, the other times software so... perhaps this is the best idea...get a spare hard drive and load XP on it and see how it runs...or ghost his and format then load using his drive to be even more sure what is going on, then you know for sure what is a problem and if it is required you have his drive backed up and can either move his needed data or you can re-image the data back so it is the same as it was and nothing changes, end back in the same boat.

 

[ell]

Well it sounds more like a stability issue in relation to the hardware at times, the other times software so... perhaps this is the best idea...get a spare hard drive and load XP on it and see how it runs...or ghost his and format then load using his drive to be even more sure what is going on, then you know for sure what is a problem and if it is required you have his drive backed up and can either move his needed data or you can re-image the data back so it is the same as it was and nothing changes, end back in the same boat.

you lost me somewhere there, are you saying ghost his drive to another drive, and put that in?

 

[Tweak]

you lost me somewhere there, are you saying ghost his drive to another drive, and put that in?

Either take a new drive and load it and see what happens or create a backup ghost image and save it then reload the system with his drive, if it works then you know it is software that was the problem and you also know for sure if his drive works...if it still has the same problems then it is hardware, once you know what is what you can fix it. Having the ghost image means either #1 putting back as it is right now OR browsing the image and pullng whatever data you might need for the fresh installation. I say ghost image but it applies with whatever type of imaging software you prefer. Hope that is clear, sorry it wasn't.

 

[ell]

Either take a new drive and load it and see what happens or create a backup ghost image and save it then reload the system with his drive, if it works then you know it is software that was the problem and you also know for sure if his drive works...if it still has the same problems then it is hardware, once you know what is what you can fix it. Having the ghost image means either #1 putting back as it is right now OR browsing the image and pullng whatever data you might need for the fresh installation. I say ghost image but it applies with whatever type of imaging software you prefer. Hope that is clear, sorry it wasn't.

Yes, I thought of imaging the drive, but he has gone and installed office, and other programs from cd, I can't move them back without the cd's and I don't want him to do it again. Wish I could image just data/programs and move it back to a clean install. I guess I'm finally out of time, he just emailed me, hes back, I had to tell him I couldn't pinpoint it, thankfully hes not mad, he just wants me to burn his data to dvds and says hes going shopping if/when it dies for good. Crap, I wish I could have figured it out, now I'm afraid this may happen again. I would have never put in the new drive if I had seen any other red flags in the hardware scans. Thanks for your advice, I'm sure I'll need it again!

 

[Tweak]

Yes, I thought of imaging the drive, but he has gone and installed office, and other programs from cd, I can't move them back without the cd's and I don't want him to do it again. Wish I could image just data/programs and move it back to a clean install. I guess I'm finally out of time, he just emailed me, hes back, I had to tell him I couldn't pinpoint it, thankfully hes not mad, he just wants me to burn his data to dvds and says hes going shopping if/when it dies for good. Crap, I wish I could have figured it out, now I'm afraid this may happen again. I would have never put in the new drive if I had seen any other red flags in the hardware scans. Thanks for your advice, I'm sure I'll need it again!

I had hoped to see how this played out as well, there is always next time huh...let's hope for easier fixes for the future buddy.

 

[ell]

I had hoped to see how this played out as well, there is always next time huh...let's hope for easier fixes for the future buddy.

Thanks! have a merry-merry