Solved Computers shows black screen, long beep and restarts

December 31, 2015 at 06:20:59
Specs: Windows 7
Hello, lately my computer has been restarting at random times.
Black screen, a long beep and it restarts itself.

The temperatures are ok (21º-24º CPU on idle, 30º-35ºc GPU on idle).

I tried to take all the memory sticks out, still happens. Yesterday I cleaned the whole computer, changed the thermal paste and it was working fine for about 9 hours.

But today, it just happened again. Black screen, long beep and restart.

I tried plugin in a different sock. We will see.

Any suggestions?

Thank you very much in advance for your time.


PS: I did a memory test and it didn't show any issue (memtest86)


See More: Computers shows black screen, long beep and restarts

Report •

#1
December 31, 2015 at 08:40:08
nobody? It just happened again... I don't know what to do


Report •

#2
December 31, 2015 at 09:13:51
✔ Best Answer
Do this:
http://pcsupport.about.com/od/windo...

Instead of restarting the computer should then give you a blue screen. Let us know the error message and particularly the first set of figures. If a file is mentioned let us know that too. This should give us some idea what is happening.

Re #1. Prompting makes no difference because posts are just opened as and when volunteers come along. The posts has to be opened to see the prompt so those who feel they can help will do so.

Always pop back and let us know the outcome - thanks


Report •

#3
December 31, 2015 at 09:20:03
Thank you Derek. I will try that and I will post result as soon as I get some.

Sorry about the bump. I won't do it again!


Report •

Related Solutions

#4
January 1, 2016 at 03:33:25
Hello Derek, it happened again.
This is the blue screen I got


http://i.imgur.com/c6wpXsE.jpg


And another one http://i.imgur.com/iJ5ZvXe.jpg

message edited by ehtiotumolas


Report •

#5
January 1, 2016 at 05:26:28
Hi,

You have two errors. An interrupt request error and a system service exception error.

Both of these errors could be related to software, possibly a driver error.

This can be caused by malware or updating system hardware drivers on an operating system that hasn't been updated for a while.

Is your Windows 7 running all the latest updates?
Have you recently updated any drivers recently such as GPU for example?
Have you run any antimalware software recently?

message edited by btk1w1


Report •

#6
January 1, 2016 at 05:47:39
I just checked windows and it is all updated.
And yes, I got a program which updates all my drivers...maybe that is the problem...
What should I do?

I think this program updated many of my drivers.

I am running malwarebytes right now.

THanks!


Report •

#7
January 1, 2016 at 06:04:35
Malwarebytes is a good choice to run an initial scan.

If it comes back clean you can go into device manager and check for any warning symbols.

In device manager you have the option to roll back driver(s) but if there are no warning symbols it would be a matter of guess work.

Another option would be to disable your driver software (if it runs automatically) and using system restore to take your system back to a date prior to the problems to see if this resolves the issue.


Report •

#8
January 1, 2016 at 06:08:24
Thank you.
I already unistalled it, because I wasn't very sure about it. So now even more reasons for it.

I will try to do a system restore. If that doesn't work, I think I will format and reinstall windows.

Thank you for your time. I will keep you updated!!


Report •

#9
January 1, 2016 at 11:29:08
I just installed windows 10 (clean install) and it is happening too.
Now, windows 10 gives me a blue screen saying something about bad_pool_header error.

:\

I tried with just one set of RAM at time and happens anyway...so I guess it is not the RAM. I will run memtest64 all night tonight

This is the bluescreen I got last time

http://i.imgur.com/zYbXXDc.png

message edited by ehtiotumolas


Report •

#10
January 1, 2016 at 12:39:04
"windows 10 (clean install)"
That got me wondering. Assuming you don't mean "clean boot" then did you do the normal Upgrade first in order to get the MS free option? Or did you use a Win 10 operating system disc?

Too late now but perhaps it was a pity that you did the W10 upgrade while in the middle of trying to diagnose a problem. Windows 10 could be adding its own new set of niggles into the equation.

Yes driver update programs should be avoided, they usually cause more problems than they fix.

Best go to "Device Manager" and let us know if any errors are showing. While you are there you could also use the "search for updates" feature on your drivers.

Apologies for coming back to your post so late - non-computer life got in the way.

Always pop back and let us know the outcome - thanks


Report •

#11
January 1, 2016 at 12:49:05
No need to apologize! I really appreciate the time you dedicate to this.

Sorry about that, I thought deleting all the drivers and installing them again would be a way to see if that was the problem.

I meant I upgraded to Windows 10, then I did a clean installation of Windows 10 (format and install).


There are no errors showing, but I am now searching for updates (this will take a while because I have to go one by one).

Do you think could be a PSU problem? I get blue screens, but sometimes the computer just gives me a black screens and restarts itself.

Thanks again.


Report •

#12
January 1, 2016 at 13:03:11
OK upgrade then format and install understood and a good idea.

Blue screens can be tricky - can be software or hardware. Hardware seems possible as you are getting issues with a complete operating system change and a fresh install. Somehow PSU is not something I would put at the top of the list.

Overheating can cause restarts. This might tell you something:
http://www.hwinfo.com/

To some extent I think we should now tackle this afresh so let us know how you get on with the drivers and give us any new blue screen detail you now get. The RAM test is a worthwhile step.

Always pop back and let us know the outcome - thanks

message edited by Derek


Report •

#13
January 1, 2016 at 13:06:29
Well, I just finished now searching for driver updates and I got new updates for my GPU, ATA Channel 1 and NVIDIA High Definition Audio

I am just with a single RAM stick and still getting black screens and restarts (with a long beep). Sometimes is this, sometimes is the bluescreen (so far, In Windows 10, only 1 bluescreen and 4 or 5 black screens followed for a restart.

Anywya, I will run tonight the memtest64 tool. Just in case (?).

message edited by ehtiotumolas


Report •

#14
January 1, 2016 at 13:16:53
As I said, even if I am running just a single RAM stick and still getting the crashes, I will put them back later on and run a full test overnight.

This are the temps hwinfo gives me. I think they are normal though


http://i.imgur.com/njgdJpZ.png


Thank you again for your time! I love computes and I consider myself not too dumb with them, but sometimes it's too hard to understand what's wrong :(

message edited by ehtiotumolas


Report •

#15
January 1, 2016 at 13:52:09
Yep, as you say, the temperatures are fine (Temperature 3 looks odd but it seems that is a false reading).

What already posted blue screen links apply since you installed Win 10? If none of them do let us have them when they arise.

Always pop back and let us know the outcome - thanks


Report •

#16
January 1, 2016 at 14:03:49
Thank you again Derek.

This is the last bluescreen I got since I installed Win 10. I got some blackscreens, but this is the only bluescreen.

http://i.imgur.com/zYbXXDc.png


Report •

#17
January 1, 2016 at 14:41:04
Thanks, I'll see what I can find.

In the meantime could you discharge the motherboard like this:

Turn off computer and remove from domestic power. If it's a laptop remove main battery too. Before putting it back together hold the Power Off/On button down for at least 20 seconds. This is a very long shot but I have known previous problems to be carried over to a new OS, so we had better make sure.

Ooops, sorry I missed the listed temperatures in your original post.

Always pop back and let us know the outcome - thanks


Report •

#18
January 1, 2016 at 15:08:08
Thank you!

I didn't know that you could discharge the motherboard like that. I will try. I was thinking that maybe could be static but I had no idea how to discharge it.

My dog has its bed close to the computer and I realised, like two days ago, that it was fully charge of static. I know that this could have nothing to do, but it is weird...and it could make sense.

I will discharge it, and we will see. Thanks again.


Report •

#19
January 1, 2016 at 15:17:00
It's not really static in the usual sense. It is that components such as capacitors can retain their charge and prevent chips from clearing their data. Shot in the dark but at least it's easy to try. It has been known to unstick things at odd times.

Not getting far as the error in the link at #16 seems to be one of those "could be anything" situations. As always though check out your drivers.

Always pop back and let us know the outcome - thanks


Report •

#20
January 1, 2016 at 15:29:52
I will try that now.

Well, so far after those driver updates I had no problems. Anyway, it has been just 2 hours since then.


Report •

#21
January 1, 2016 at 15:32:47
OK keep us posted.

Always pop back and let us know the outcome - thanks


Report •

#22
January 1, 2016 at 15:38:15
Best sit tight and monitor it for a while.

If you get in trouble again this is one of the few fixes I've found (NVIDIA driver & setting) so it might be worth checking out:
http://www.eightforums.com/bsod-cra...

Always pop back and let us know the outcome - thanks

message edited by Derek


Report •

#23
January 1, 2016 at 19:17:29
Another crash.
Same bluescreen related to ntoskrnl.exe

I dont have the Nvidia Streamer service in my computer, so I cant disable it.

I tested my HDDs and they are ok.


I also tried to unplug my computer and hold the power button for 20+ seconds. I still got a bluescreen after that.


Thank you for your help anyway!

message edited by ehtiotumolas


Report •

#24
January 1, 2016 at 19:22:53
If you put this in Google there are a lot of hits:

BAD_POOL_HEADER ntoskrnl.exe

I've got to nip away for a while but if you have a look there you might stumble across something.

Always pop back and let us know the outcome - thanks


Report •

#25
January 1, 2016 at 20:03:40
I have been checking links and stuff but nothing seems to fix it.
It is getting really annoying.


I ran a sfc scannow and I got some corrupt files but windows was unable to fix them.

This is the cbs.log, if that could help


https://onedrive.live.com/redir?res...

Thansk!


Report •

#26
January 1, 2016 at 22:24:20
The hwinfo reading for "temperature 3" might be of some concern. 80 degrees would probably be outside the default allowable temp limits in the BIOS.

My thoughts are that if the BIOS kicked in to protect the system from overheating that the OS wouldn't have anything to say. The system would just shut down from the BIOS end. Also the reading appears to be static. It is constant 80 regardless. This is still worth investigating though because it is operating system independent.


Report •

#27
January 2, 2016 at 06:31:56
That "HWINFO temperature 3" reading seems to be the subject of mystery if you google around on it. Sure it could well spell trouble if it is true but I'm not so sure that it is.

ehtiotumolas
Are temperatures given in BIOS?

Always pop back and let us know the outcome - thanks


Report •

#28
January 2, 2016 at 12:23:08
I did the memtest and I got no problems and also checked the BIOS temps.

Two screenshots here.

memtest http://i.imgur.com/cSSGQcW.jpg

BIOS http://i.imgur.com/uXHLV41.jpg


I think that other temp is a false temp.


Report •

#29
January 2, 2016 at 13:00:45
By the way, my computer has just frozen
No bluescreen, just frozen screen.


I really dont know what to do. I am just about to let it go and buy a new motherboard, GPU and CPU :( Maybe then I will solve the problem!

message edited by ehtiotumolas


Report •

#30
January 2, 2016 at 15:44:22
When you loaded Win 10 what was the source and media?. Your CBS log seems to show a good bit of trouble. I'm just wondering if the OS file you used was OK.

Always pop back and let us know the outcome - thanks


Report •

#31
January 2, 2016 at 16:16:29
I just upgrade my Windows 7 to Windows 10.
Then, when Windows 10 was installed, I did a clean installation (formating and reinstalling). All with the windows updater thing, no physical DVD or USB.


Report •

#32
January 2, 2016 at 16:47:55
OK. I seem to be stuck between two ideas:

1. This is a hardware fault because it is still playing up after Win 10 was clean installed.

2. It was a bad install (corrupt download maybe). However, if some of the blue screen reports were the same on both Win 7 and Win 10 it would be hard to imagine such a coincidence.

If it is hardware then I'm as lost as you are. You could run a disc check:
https://support.microsoft.com/en-us...
Also check all internal connections and clean edge connectors with a pencil eraser. In particular and add-on sound card and the RAM. I've also know SATA HD connectors to give trouble, both power and signal.

Always pop back and let us know the outcome - thanks


Report •

#33
January 2, 2016 at 16:53:42
Didn't go through all the posts.
Did you try another hard drive?

Report •

#34
January 3, 2016 at 10:18:18
No, I didn't.
I made a few scans to check their integrity and they seem to be okay, though.

Anyway, I left the computer on for about 16 hours so far and it has been okay. No problems at all.

The only difference...I closed Google Chrome...

I mean...it could be just a random thing but so far no problems.


I am going to keep this like that for another day. If no crashes happens, I will use Google Chrome back to see if that it's the cause.


Report •

#35
January 3, 2016 at 15:27:15
Sounds odd but nothing with computers should be a complete surprise.

Always pop back and let us know the outcome - thanks


Report •

#36
January 3, 2016 at 20:49:28
What did you use to scan the HDD?
Use the drive manufacturing disk tools usually available from their website.

Report •

#37
January 3, 2016 at 23:40:27
Yes sluc, I used the manufacturing disk *seagate for the HDD and samsung for the SSD).

And yes, it is really odd but my computer has been on for about 30 hours now...and still no crashes. I am going to work and after that I will try to use Chrome and we will see the results.


Report •

#38
January 4, 2016 at 09:17:09
It's been like 40 hours running my computer.
0 crashes.

I am opening now Google Chrome. Let's see if the crashes appear now or they are just solved :\

message edited by ehtiotumolas


Report •

#39
January 4, 2016 at 14:20:08
We'll all cross our fingers and toes.

Always pop back and let us know the outcome - thanks


Report •

#40
January 7, 2016 at 10:53:58
Well, it happened again a few times so... With or without Chrome.
I just dont know whats the cause.

It is so annoying to dont know it.

This is the only bluescreen I got because the other times my system just got frozen and I had to restart it.


http://i.imgur.com/vXr8p5h.png


Report •

#41
January 7, 2016 at 12:21:08
I couldn't read the full error messages but I assume one was "UNEXPECTED KERNEL MODE TRAP". See this, which suggests hardware is most likely:
https://neosmart.net/wiki/0x0000007...
I would steer clear of BIOS updates because they can brick the motherboard if they go wrong. They are usually only needed for very specific things such as installing a different processor.

One thing you could do is take out the RAM and clean the edge connectors with a soft pencil eraser. I've had trouble with these many times in the past, despite them looking OK. Pop the sticks in and out a few times before pressing them home as this will clean any oxide off the sockets themselves. Best do the same on Video card edge connectors and both power and signal connectors on SATA drives. Press all cable connectors firmly home whilst you are in there.

Always pop back and let us know the outcome - thanks


Report •

#42
January 7, 2016 at 12:53:54
Derek, I wont stop thanking you for all your time.
I will definitely try this (I have a few busy days, but I will try it).

You always bring me hope :)

Thank you very much.


Report •

#43
June 3, 2016 at 09:13:20
I found the problem, my PSU was faulty. I had a Corsair CX 600w.
I had this problem for several months.
I bought a new PSU and everything is fine. No problems at all.

Hope this will help somebody


Report •

#44
June 3, 2016 at 09:14:18
Found the solution! I just quote you just in case you wanted to know

Report •

#45
June 3, 2016 at 11:24:02
That's very good news and thanks for taking the trouble to pop back and let us know. As you say, it might help others.

message edited by Derek


Report •

Ask Question