HP Pavilion Slimline s5212y Desktop Blue Screen Shut Down

September 1, 2013 at 12:37:38
Specs: Windows 7
My HP Pavilion Slimline s5212y Desktop shuts down and gives me a blue screen. I have taken apart and blown out the unit including the heat sink. Any ideas?

See More: HP Pavilion Slimline s5212y Desktop Blue Screen Shut Down

Report •

#1
September 1, 2013 at 15:07:31
If the blue screen remains long enough let us know the error it is reporting, at least the first string of digits shown and if a file name is mentioned give us that too. There are stacks of different blue screen errors which can have a multitude of causes (software or hardware). That information would help us narrow it down.

Always pop back and let us know the outcome - thanks

message edited by Derek


Report •

#2
September 1, 2013 at 17:59:33
Im sorry... Not trying to be rude but I didn't understand.

So you first got the blue screen, than you took it apart blowing out the unit including the heat sink?

If thats the case, then I think you got your self a broken PC..

Culer fins ala mort!

message edited by Josep


Report •

#3
September 2, 2013 at 09:10:22
Josep,
I had read that the heat sink could be the problem. I usually blow my computers any way. But when I opened the computer I found the heat sink full of dirt & and lint. Hoping that after I blew it out the problem would go away. It has not! HP is no help. I've checked for virus's. None! Making last ditch effort before replacing machine. Thanks.

Report •

Related Solutions

#4
September 2, 2013 at 09:43:52
Keep looking for that blue screen info, it might allow us to make some sort of headway.

Always pop back and let us know the outcome - thanks


Report •

#5
September 3, 2013 at 20:34:00
Okay... Here it is. Your NTOSKRNL.EXE might be missing or corrupt! That is why you're get the blue death screen.

Like Derek said this might be this error can caused by different reasons.

Here are your probable issues:
miscellaneous corruption, missing ntoskrnl.exe file, corrupt ntoskrnl.exe file, corrupt boot.ini file, missing boot.ini file, corrupt hard drive, corrupt Windows OS, or maybe a keyboard issue.

Solutions on next post if still interested!

Culer fins ala mort!

message edited by Josep


Report •

#6
September 4, 2013 at 06:23:01
Derek,
Here's what I got off the blue screen. Stop: 0X00000109(0XA3A039D8976AB51A

Also

NT0SKRNL.EXE-Address FFFFF80000B96BB0
I hope that gives you something.
Thanks


Report •

#7
September 4, 2013 at 08:02:29
Thanks for the information. Unfortunately it turns out that this particular error can arrive for a wide range of reasons (hardware and software).

The very first thing I would do is power off, take out the RAM sticks then clean their edge connectors with a pencil eraser. Even the slightest vibration can sometimes cause them to move onto an oxidized area on the edge connectors. Pop the sticks in and out a few times so that the sockets themselves get cleared of oxide.

If that doesn't help it would be worth downloading a RAM test and running it for several hours. My thinking is it we should first rule out RAM from the equation.

If you get any further blue screens after the above which are different, then let us have them - it might give a clue. The most important parameters are the error message itself (often in capital letters) then the first set of figures and any file name mentioned - Stop: 0X00000109 and NT0SKRNL.EXE in the example you gave.

Always pop back and let us know the outcome - thanks


Report •

#8
September 8, 2013 at 04:45:34
I edited my last post...

Need to double check are you running windows 7 on your hp?

Culer fins ala mort!


Report •

#9
September 8, 2013 at 07:02:41
Josep, Derek
I am running Windows 7 Home. I removed the memory, cleaned with an eraser and reinstalled. Still the same issues. Same error messages.

Report •

#10
September 8, 2013 at 12:50:31
I'm afraid we now need to go through the tedious job of trying to first find whether it is a hardware or software fault then investigating possible reasons for what is causing the trouble.

If this blue screen appears frequently then try using it from Safe Mode for a while. The screen won't look very nice but most basic things will still work. If you can come away certain it doesn't fail from there we should be able to assume it is NOT a hardware fault.

If it still fails when in Safe Mode then do the memory (RAM) check, which would eliminate that from the equation:
http://www.sevenforums.com/tutorial...

A driver issue is possible if we can first be certain it is not a hardware fault.

Always pop back and let us know the outcome - thanks


Report •

#11
September 8, 2013 at 20:22:42
Derek,
Ok I checked the memory it was ok. I then put the computer in safe mode. The computer did not shut down. I ran it for six hours. It was shutting down every 20-30 minutes. So it looks like it's not hardware. So what do I need to do now?

BigD


Report •

#12
September 9, 2013 at 11:42:49
If the issue suddenly happened and it was not too long ago, you could take the easy way out and do System Restore (back to before it started playing up). Your own stuff will be OK but anything you have installed since then will go - including Windows Updates..

Otherwise the best bet is to go to HP and get all the latest drivers - they are often implicated in blue screens when they are not down to hardware. When you run from Safe Mode you are using minimal drivers. It's not just that they might happen to be out of date but that installing the latest versions will overwrite what is there. If something has corrupted new drivers could well put it right. If you want to pick and choose then it might be best to try renewing the Display driver first.

Always pop back and let us know the outcome - thanks


Report •

#13
September 9, 2013 at 13:47:56
Another thought - you might care to run Blue Screen View on it:
http://www.nirsoft.net/utils/blue_s...

Always pop back and let us know the outcome - thanks


Report •

#14
September 10, 2013 at 08:39:51
Derek,
I had tried the system restore, I guess I didn't pick a date far enough back. I did go thru and update all my drivers. I then ran the Blue Screen View. The NTOSKRL.exe came up as the driver in the lower screen. Is this driver corrupt?

Report •

#15
September 10, 2013 at 09:09:10
I have assumed you are still getting the BSOD's. If so see below:

NTOSKRNL.exe is not actually a driver but an important system file. Unfortunately it doesn't necessarily mean that the file itself is corrupted (MS often use the nearest error message that appears to fit). Just the same it would be as well to check system files like this:
http://www.sevenforums.com/tutorial...
Follow it from Option 2.

Always pop back and let us know the outcome - thanks

message edited by Derek


Report •

#16
September 11, 2013 at 08:08:58
Ok, I ran the sfc/scannow and no errors or problems. Still getting the BSOD.

Report •

#17
September 11, 2013 at 10:35:00
Again, purely for elimination there are a couple of things we should do:

Download, install, update and run MalwareBytes freebie (green icon top right):
http://www.filehippo.com/download_m...
Unless it finds anything of consequence on the quick scan I think we can assume your issue is not virus related.

Run Windows 7 disk check:
http://www.sevenforums.com/tutorial...
This is against the off chance that there is a bad patch on the HD that needs fixing. It could be a part not used when in Safe Mode.

We are a bit stuck with throwing things at this issue in the hope we can unearth something. Some folk have resorted to reloading Windows but I doubt either of us want to think in that direction. In another case a RAM check for many hours found a faulty stick of RAM. If you have more than one you could try running the system with just one at a time but I'm inclined to agree that if it is OK in Safe Mode it points generally to software. Whatever, if you do decide to peer inside then clean the RAM edge connectors with a pencil eraser as oxide can cause intermittent faults. I usually pop the sticks in and out a few times to clear any oxide off the sockets themselves too.

EDIT:
As far as bigger guns are concerned there is always this:
http://www.sevenforums.com/tutorial...
It relies on what system disks you have available or whether you would really want to go this way - later if necessary maybe.

Always pop back and let us know the outcome - thanks

message edited by Derek


Report •

#18
September 11, 2013 at 17:39:08
A bit more:

Is "STOP" the only error message showing on the blue screen - nothing else in block capitals?

Do the blues screens happen while you are using it or are they sometimes during startup?

Always pop back and let us know the outcome - thanks

message edited by Derek


Report •

#19
September 22, 2013 at 14:32:12
Boot your Windows 7 Installation USB or DVD. Open the 'repair my computer' and run 'command prompt'. Type in "Chkdsk /R C:" (usually the booting drive) then type in "Y" and reboot the computer. Be patient as Windows attempts to repair any errors.

Culer fins ala mort!


Report •

Ask Question