BSOD issue - PC randomly shuts down

Yes, it is Ralink.

Code:

==================================================
Driver Name       : netr28x.sys
Address           : 00000000`04420000
End Address       : 00000000`0451E000
Size              : 0x000fe000
Load Count        : 1
Index             : 84
File Type         : Network Driver
Description       : Ralink 802.11 Wireless Adapter Driver
Version           : 3.1.10.0
Company           : Ralink Technology, Corp.
Product Name      : Ralink 802.11n Wireless Adapters
Modified Date     : 11/08/2010 04:40:06
Created Date      : 29/03/2012 12:43:36
Filename          : C:\Windows\system32\DRIVERS\netr28x.sys
File Attributes   : A
Service Name      : netr28x
Service Display Name: Ralink 802.11n Extensible Wireless Driver
Digital Signature : 
==================================================

So you have to get it from MediaTek - Downloads Windows

Match your device model with the first column, and get it accordingly.

This BSOD is caused by Intel(R) 82579V Gigabit Network Connection driver.

Code:

BugCheck 19, {20, fffffa800791aa30, fffffa800791ab50, 41200a3}

*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
Probably caused by : e1c62x64.sys ( e1c62x64+1bec2 )

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

You need to update it. I am failing to find it in Packard Bell's site .... an alternative source I found is Intel(R) 82579V Gigabit Network Connection Driver Download for Windows XP, Vista, 7, 8 .

Your installed version is 12.2.45.0. I am suggesting you to take version 12.6.45.0.

If you can search it in Packard Bell's site, get it.

Let us know the results.

This time it is blaming the Ralink network driver, again.

Code:

fffff880`08f17a78  fffff880`044ffdb2Unable to load image \SystemRoot\system32\DRIVERS\netr28x.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netr28x.sys
*** ERROR: Module load completed but symbols could not be loaded for netr28x.sys
 netr28x+0x8ddb2

Its strange that all the network elements are failing here. So it may be something else that we are not thinking.

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Also Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If Both the virus scans and memtest are free from errors, go for a Clean Reinstall - Factory OEM Windows 7.

My apologies mate. We most of all the BSOD analysts are ATM failing to debug crash dumps, due to some issues with the microsoft symbol server.

As the dumps are not showing the output properly, we cannot analyze it and read it.

Hope you will understand the situation.