BSOD on netbook

Hello everyone!

My netbook crashed and went straight to bluescreen a couple of weeks ago. The same thing happened twice today completely randomly which got me really concerned. Windows seems to work just fine right now. Just a random BSOD out of nowhere and reboot, Yet it happened twice in a row today, maybe 1-2hrs time between the crashes.

As of yet, the blue screen disappeared to quickly for me to note down the Error number.

I let the program dm log collector run and have attached the .rar file. Hope this gives you guys some info!

Greetings!

Please upload your MSINFO32.nfo file. We cannot suggest you anything without checking that in this situation.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

________________________________________________________________

Code:

BugCheck 124, {0, 84daf024, f6000000, 10015}

Probably caused by : AuthenticAMD

Followup: MachineOwner
---------

Code:

Processor Manufacturer        AMD processor
  Processor ID                  100f5000fffb8b17
  Processor Version             AMD C-50 Processor
  Processor Voltage             8ch - 1.2V
  External Clock                100MHz
  Max Speed                     1000MHz
  Current Speed                 1000MHz

Code:

BiosVersion = V1.04
BiosReleaseDate = 12/21/2010
SystemManufacturer = Acer
SystemProductName = Aspire One 522

Hi Watza666.

A stop 0x124 is generally a hardware related issue. And testing the hardware of the laptop is not very easy, rather is is somehow tough. If you think that you will not be able to deal with the hardware, better you take the laptop to a repair shop.

If you think that you can continue with troubleshooting, we can continue here. In that case, depending on the age of the laptop, the first thing is to check the temps. Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Hi Arc! Again, thank you for being very kind and detailed in your instructions for me! I surely appreciate it!

The netbook must be around 3-4 years, it is definitely not the youngest, but I haven't had any problems yet since I purchased it from a friend 2 years ago. A hardware problem, thus, seems plaubsible.

I have had my netbook plugged in and running for aprox. 5 hours now, but mostly with just Skype and Chrome running and screen in standby as I was AFK. When I came back, I immediately installed Speccy. This is my Snapshot.
I know not much about computers, but I was quite concerned by the temperature under the Graphics point. In the screenshot it is 69°C, but when I first opened Speccy it was 78°C! That seems extremely high. As I am writing this, it is still at around 69°C. But then again, I'm only using Chrome and Skype right now.

Edit: Along with Chrome and Skype, I just opened up Open Office Word and Powerpoint and it crashed while I had my back turned. Right now I'm opening up all these programs once more and this is the Speccy. The Graphics thing peaked at 82-83°C.

This computer needs some dusting and fresh thermal paste.



If you can do it yourself, you may do it. But if you dont have done it earlier, take it to a technician, straight; ask him to do it for you.

Till you do it, us a cooling pad.

Watza666 said:

Alright, so you are sure that the problem is definitely some kind of overheating?

Nothing can be said so precisely for a stop 0x124 BSOD, but overheating is one of the most frequent causes of it. And as overheating is there, it is to be controlled at first.

If teh issue persists even after taking the heat under control, then we can search for the cause elsewhere.