Every so often my desktop computer goes to a blue screen that says "Crash dump", and then shuts off. Other stuff is there too, but it doesn't stay up long enough for me to read. Its an HP, running Chrome as the browser. I've ran several virus scans, and nothing is ever found. Of course that doesn't mean anything. What's happening? Is it a virus, or is it overheating and cutting off? Power source? The computer is about a year and a half old. What else can I do, short of taking it to someone, to determine what is going on.

Jim

http://www.worldstart.com/d...lue-screen-of-death/

Next time it blue screens, get the error code and look it up (or post it here). It will look something like this:
http://images.pcworld.com/h...10-bsod_original.jpg
either a name (like in the top rectangle) or a number, like 0x0000007b.

A Crash Dump is what happens in your shorts when you get into an auto accident.

quote Originally posted by kwagner: http://www.worldstart.com/d...lue-screen-of-death/ Next time it blue screens, get the error code and look it up (or post it here). It will look something like this: http://images.pcworld.com/h...10-bsod_original.jpg either a name (like in the top rectangle) or a number, like 0x0000007b.

Will do. There was some type of code, but I couldn't make heads or tails of it. It goes to a screen that ask what mode you want to reboot in, but I don't know what to do, so I just have it reboot in normal mode. I gotta go to work, but I'll let my wife know, and maybe she can post it, if she see's it later today. Thanks.

Jim

Turn off the "reboot when there's an error" setting. That'll at least give you time to jot down that error code...


On a bus on my BB atm, can some post how to do that using the different flavors of Windows?

quote Originally posted by TheDigitalAlchemist: Turn off the "reboot when there's an error" setting. That'll at least give you time to jot down that error code... On a bus on my BB atm, can some post how to do that using the different flavors of Windows?

Or just have it log to disk. Without details, most likely its a driver problem, or a piece of hardware that is failing ( still driver related )...

Look for C:\MEMORY.DMP
Stop code should be in the file.

WinXP and other default to small memory dump ~256KB size (List same page to disable auto reboot)
Other options none and Kernel memory dump.

Kernel is big. How much RAM = How big the file + overhead. Reboot time is how fast system can copy RAM to HD File.

Yes, most times BSoD is driver and/or hardware w/ problem.

Just google stop code # for things to check.

------------------
Dr. Ian Malcolm: Yeah, but your scientists were so preoccupied with whether or not they could, they didn't stop to think if they should.
(Jurassic Park)

The Ogre's Fiero Cave (It's also at the top and bottom of every forum page...)

So here are the codes, forgive me if I leave out a character. I am assuming the 0 are zeros, and not capital O's.

On the blue screen:

Stop: 0X000000E1 (0XFFFF800037C5560, 0X000000000000000X2, 0XFFFFFA8009441DBO)

Then after reboot this appears in a window:

Problem signature 1033
BCCode: e1
BCP1: FFFF800037C5560
BCP@: 0000000000000002
BCP3: FFFFFA8009441DBO
BCP4: FFFFFA8009441DBO
OSVersion 6_1_7601
Service pack 1_0
Product 768_1

If I've given out something that should not be given out, someone please let me know so I can edit it out.

Jim

Bump for any advice.

Jim

Nothing secret, so dont worry about that.

Anytime i have seen a windows dump it had something a bit more useful towards the top.

I'd suggest using something like Registy Mechanic(or some free software that does the same) to sweep your registy for errors. My next step after that, if it's still occurring, would be to start the task manager (ctrl-alt-del) and shut down everything I didn't need under "Processes" and see if that stops it, and if it does, you can thereafter try shutting down one thing at a time until it goes away, at which point you know what program to stop running and/or re-install. Of course, if I see something suspicious running on that screen, then I would assume I've been infected with malware of some sort and get ahold of something to check for such, like Malwarebytes' Anti-Malware.
If nothing software related seems to fix it, I'd suspect hardware and check that all my fans were working properly (I had one clog up on my video card once and the heat buildup would cause random crashes) and the heatsinks were free of dust. Before trying to replace anything though, I'd probably try a fresh install of windows on a different partition/drive to see if it occured on that and then finally I might suspect bad ram or something and find some software to test it.
Troubleshooting random crashes on a computer is a lotta fun. You'll probably find and fix a lot of other things along the way before you finally find your key problem. Goodluck.

Well thinks for the help guys, but I'm just too disconnected when it comes to this computer stuff. I think I'll blow out the dust, and then pay somebody to look at it, because all of this number, BIOS, Kernal, registry, thigamabob crap, doesn't mean anything to me. I give up.

Jim

quote Originally posted by jimbolaya: Well thinks for the help guys, but I'm just too disconnected when it comes to this computer stuff. I think I'll blow out the dust, and then pay somebody to look at it, because all of this number, BIOS, Kernal, registry, thigamabob crap, doesn't mean anything to me. I give up. Jim

Oh come on dude, it is no different than,

BIOS, carb
Kernal, crank shaft
registry, ignition
thingamabob, thingamabob

It’s no different than a car.

Steve

------------------
Technology is great when it works,
and one big pain in the ass when it doesn't



Detroit iron rules all the rest are just toys.

Checked for C:\MEMORY.DMP and/or C:\Windows\Minidump folder for ___.dmp?

Should have affective file(s).

The error is "WORKER_THREAD_RETURNED_AT_BAD_IRQL".
That doesn't mean much to the layman, unfortunately
Try this program to look at your crash dumps:
http://www.nirsoft.net/utils/blue_screen_view.html
What version of windows? Have you installed any programs or hardware (USB camera, thumbdrive, sound card, etc) recently?

Sorry... I forgot you Need MS software to read minidump and change ___.dmp file security access.

View Properties on recent .dmp File in C:\Windows\Minidump
Security Tab
Edit button
add button
Enter you windows login name and ok button
Select login name
Check in Check box for full control
click ok

Email to me or post to google drive

Minidump ___.dmp only have affected program/drives/dll files names and some data why/how they got hosed and is small enough to email etc.

[This message has been edited by theogre (edited 12-03-2012).]

I use this helpful little application when my one computer kept having BSOD's.

bluescreenview

quote Originally posted by FieroJam: I use this helpful little application when my one computer kept having BSOD's. bluescreenview

This is smaller than MS debug tools and less pain to tell someone how to install and use... And you don't want to install on iffy machine.

Get ZIP file. You don't install it right now.
In program...
Hit F8 to see BSoD
use file menu and google search

If can't access minidump file then need to change security.

quote Originally posted by kwagner: The error is "WORKER_THREAD_RETURNED_AT_BAD_IRQL".

Sounds like an excuse to get out of trouble at work to me!

quote Originally posted by FieroJam: I use this helpful little application when my one computer kept having BSOD's. bluescreenview

So what is this supposed to do? I installed it, and now it just sits there, and there is no icon, or way to run anything. In addition, it set the alarms off on my antivirus protection, saying this program "could" be harmful to my computer. I did something I rarely do, I ignored that message and installed it any way, since my computer appears to be hosed anyway, and a lot of those messages are false. Will it do it's thing when I get my next crash?

Jim

Have you checked the log files? it may have an event in there which might shed some light on this...