BSOD dell vostro 1014, hangs when charging, auto shut downs

Hello learned sirs,

I have recently bought a Dell Vostro 1014 Laptop. it has been acting up recently a lot and the following is occuring :
1. automatic crashing of system
2. BSOD ( i have attached the dump files and all the other files after running the program as listed in instructions)
3. freezes in between randomly, sometimes even in middle of startups.
4. i am not even able to run HDD regenerator to see wether i have bad sectors or not
5. i have a small doubt that in addition, when i plug in my charger it freezes up again as well.
6. i was not having these problems for over last 8 months . Please Help

PS NOTE : i do surf the web a lot, i use torrents but i also have Malwarebytres anti malware and MS security essentials installed on my system.

Any help will be greatly appreciated... :)

Don't have both Malwarebytes and MSE running at the same time. They will conflict with each other if they both have AV engines running simultaneously.

Anyways, you have hardware failure, most likely CPU/Mobo/PSU. Most of your bugchecks are 0x124 WHEA errors reporting consistently that the bus for your CPU internal L0 cache is failing. There's also heavy corruption going on with a good bit of the other bugchecks.

If you want, you should first try and update all Dell drivers, especially your BIOS and CPU/chipset drivers. While I doubt this will resolve the issue, there are rare cases which this is caused by BIOS problems or even a messed up/buggy chipset driver.

Your laptop should still be under warranty. You'll need to send it to Dell and have them service or replace the laptop. There's nothing here that you can - nor are you permitted - replace on your own.

Vir Gnarus said:

Don't have both Malwarebytes and MSE running at the same time. They will conflict with each other if they both have AV engines running simultaneously.

Anyways, you have hardware failure, most likely CPU/Mobo/PSU. Most of your bugchecks are 0x124 WHEA errors reporting consistently that the bus for your CPU internal L0 cache is failing. There's also heavy corruption going on with a good bit of the other bugchecks.

If you want, you should first try and update all Dell drivers, especially your BIOS and CPU/chipset drivers. While I doubt this will resolve the issue, there are rare cases which this is caused by BIOS problems or even a messed up/buggy chipset driver.

Your laptop should still be under warranty. You'll need to send it to Dell and have them service or replace the laptop. There's nothing here that you can - nor are you permitted - replace on your own.

first off Thanks so much @ Vir Gnarus for the quick reply. i cant tell you how helpless i feel, regarding this issue since i have no idea what the dumps mean :) . But its trhiugh support of people like you that we go on i suppose .

Sad part is my laptop is out of warranty, for most part people advise me to change my hard disk, so if you could either suggest a specific problem or maybe help me analyse the reason, i would be much obliged.

PS : I have removed malwarebytes as advised, as for PSU failure i am not too sure since i feel it is a matter of coinsidence when i plug in my charger the laptop freezes .
ALSO : recently i was advised by another person that these faults might be due to memory corruption ?? any idea

I'm afraid disk has nothing to do with this. It's an internal problem with your cpu/mobo/PSU. There's the very slight offchance we're dealing with bad memory here which is replaceable on your laptop, which you can try testing with something like memtest86+, running it at least 7 passes (just leave it run overnight, it runs infinitely until you tell it to stop). Understand that PSU/Mobo/CPU problems can manifest themselves as false positives in this test. However if you do find errors the least you can do is buy new RAM and replace it. If the problems still arise, then either you bought a bad set of RAM, or the more likely scenario which is your PSU/Mobo/CPU failing. Since you are out of warranty, your only option is probably going to be replacing the entire laptop.

Thanks Vir Gnarus, however i would be much obliged if anyone who has the time and expertise can debug the dump files and tell me a little in details as to what is the exact reason of these crashes, since mobo/cpu/psu is too broad a reason for me to trash my laptop not older than 14 months.

PS: As before any help and response is greatly appreciated. :)

I did, and one can't. Crashdumps can only generate assumed information provided to it by either drivers or the Windows kernel for hardware checking, which it did. The CPU generated a fault which the Windows kernel caught and therefore caused a BSOD, but how that CPU fault came to be in the first place cannot be determined from this data, and never really will outside of being able to make an educated guess, which I did. In fact, there's really no solid hardware tests or diagnostics for CPU, motherboard or PSU failure outside of taking each part out individually and inserting it into a system that has reliable parts. Obviously that's not an available option here given we're dealing with a laptop, and one out of warranty. All that can be determined from this data is, "Is this a hardware or software failure?" If it's software, chances of finding exact chance are much better. But if it's hardware, all you can ask is, "What is most probable cause for this?" In this case, I venture to believe CPU, mobo or PSU are most definitely suspect.

It is not uncommon to have a system that died in around a year's time when it's a Dell. One can get lucky and have a Dell system that lasts a few years, but the chances for that is lower than other brand names (aside from HP and Sony). As the saying goes, "You get what you pay for." You are not purchasing Dell for top-of-the-line high-quality product; you are purchasing it because it offers competitive pricing. Yet again, this can happen with any brand laptop, just more often with Dells and HP.

If you are desperate for a more solid answer on this, bring it to a local shop that handles Dell repairs. They might have spare parts on hand that they can replace and determine what's causing the problem by swapping the hardware. Of course, you'll be paying a good bit for it. So it's up to you whether you wanna go for it, or decide to cough up a bit of money (memory is cheap nowadays) to see if it really is the memory itself (doubt it), or replace the laptop, which is the most common option for people in your predicament.

If you want validation for my claims, here's the output:

Code:

0: kd> !errrec 864bc4dc
===============================================================================
Common Platform Error Record @ 864bc4dc
-------------------------------------------------------------------------------
Record Id     : 01cd5eb650d13883
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/10/2012 16:09:09 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ 864bc55c
Section       @ 864bc634
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x86
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x000000000001067a
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ 864bc5a4
Section       @ 864bc6f4
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 7a 06 01 00 00 08 02 00 - bd e3 08 0c ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ 864bc6f4

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ 864bc5ec
Section       @ 864bc774
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xf200084000000800

The "M" in the error may mean memory, in which case it would be wise to run that Memtest86+ for a good while, and then replace the memory if there are signs of failure. That would be your cheapest, and least obstructive option here. Personally, I cannot see how L0 cache has anything to do with RAM, but given it mentioned the bus and not the L0 cache itself failing, crosstalk between RAM and CPU could be suffering problems. Most suspect item in that case would be the motherboard itself.

This is just for one bugcheck, but most of them are exactly this WHEA error.