BSOD Need Help!

Arc said:

So you cannot do a BIOS update?

SO many drivers failing at a stage .... that's really not good.

Scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Let us know the results.

Also, I do not know how to do a BIOS update.

I tried googling LG R380 BIOS update but could not get anything useful.

UPDATES:

I used the Kapersky TDSSKiller scan and it came out clean.

Then, I tried opening the Windows Defender Offline but it cannot run in Safe Mode and I could not enter Windows 7 in its normal mode so I cannot run Windows Defender Offline?

Arc said:

For the first one, TDSSKiller, execute the exe anyhow, in safe mode or normal mode.

For the second one, you need to burn the downloaded ISO in a CD, then boot from the CD and perform a full scan.

Alright I am burning the Windows Offline Defender into a CD now, will let u know the results soon.

Pauly said:

Create WDO bootable media (usb/cd) from your other computer then put in this one and boot from it :)

I have trouble burning the WDO on a CD, is it possible if I install/burn it into an external HDD?

Alright it is 4:04 am here (Singapore), I am tired. I will continue tomorrow. Thanks Dsprague, Arc and Pauly for your insights/help/comments/analysis.

Dear Dsprague, Arc, Pauly or anyone else,

Is there other solutions than Windows Defender Offline as I have tried burning the ISO/Software into a DVD but just keep failing to do it.

Any solutions other than WDO? *desperate*...

I've been reviewing this. You said you've been having a hard time finding support for this product. You also said you are from Singapore. Have you tried accessing LG's Singapore native site and see if updates are available through there? Localized product models are often difficult to find with Google just because of the language difference. It's an LG product, purchased at Singapore (I assume), so best place to look is the Singapore LG site.

If this still shows up nothing, contact their support line and ask them where to find updates. If they say the product is no longer supported, it's time to start saving up for a new one, because there's no point hanging onto a dead product. The fact is, I'm afraid this is may be looking like one of those cases where an old deprecated PC has reached its EOL (End-Of-Life) and now support is no longer available for it (as in, no new driver updates, etc). The result is that a driver bug is causing problems with the system, but there's no way to update and therefore potentially remove the bug. This is where it's time to start looking for a replacement, or downgrade the system to an OS that is more likely to be supported (i.e. Windows XP) due to its age.

Anyways, I've been perusing your crashdumps, and indeed it looks consistently like a driver bug. It has to do with your wifi and/or NIC drivers that are not working properly in the Windows 7 environment. The dates for the drivers are all from 2009, and some either date to Windows 7 release or predate it, meaning they were most likely not designed for Windows 7 support, or they did a rush job and just released Windows 7 supported drivers just stable enough to get by at the time before the EOL on that product occurred. Either way, it's all looking like the hardware itself just needs updating, which means a new PC.

I understand this may not sound like a good position to be in, but cheap products with short support lifespans being the big thing nowadays, all one can do is just go with the flow, or pay a premium to get a high quality system that is less likely to fall into this problem. This is the equivalent of buying cheap inkjet printers that burn through ink cartridges and jam easily and break down quickly when one can save up more money to buy a decent laserjet printer that will last them almost forever. You just get what you pay for.

Oh, btw, once your virus infection is indeed found to be clean, make sure to uninstall Ad-Aware if you haven't already. I've been seeing that in a number of the BSODs as being the cause, though it was showing up in older crashdumps.

Analysts:

Most frequent BSOD is caused a driver reaching max IRQL (IRQL FF) most likely to grab a spin lock (as shown in the raw stackdump) but for some reason is trying to execute code from a null address (null instruction pointer). Perhaps there's some context switch that isn't going well or what, but whatever it is, the fact is in the raw thread stack it shows TCP/IP activity as well as the wifi/net drivers and perhaps even the Nvidia driver in some cases. Unfortunately, there's no way to work out this without driver updates for any of these.