Packard Bell laptop 0x0000004F STOP error on startup

Scruffywelder · 29 Jul 2013

Hi guys.

My girlfriends laptop has a habit of pulling an occasional (seemingly random) BSOD on start-up. As far as either of us can remember it's the same error code every time.
Having had good advice from the forum previously I thought the best thing to do was ask here (before killing-it-while-attempting-to-fix-it).
Hopefully the files requested in the How/What to Post instructions will be attached to this post.
Thanks in advance for any help or advice available.

Cheers, Scruff

koolkat77 · 30 Jul 2013

McAfee is a frequent cause of blue screens, please remove it.

Replace with Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:

Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Microsoft Security Essentials - Microsoft Windows

Malwarebytes Free

Do not start the trial version of MalwareBytes

You may also take a look at:

Good & Free System Security Combination

Make scans with -

TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US

Online Virus Scanner Eset

Please take a back up of the hard drive asap - (on an external device / HDD)

Reduce items at start up:

Performing a Clean Startup in Windows 7

Add, or Remove Startup Programs in Windows 7

Your Antivirus software is basically whats just needed there.

Use the System File Checker tool and Run Disk Check:

Repair Windows 7 System Files with System File Checker

Run Disk Check in Windows 7 for Bad Sectors & Errors

Upload a screenshot using:

CrystalDiskInfo

For how to upload a screenshot or file, read here

Test your Hard Drive by running:

Hard Drive Diagnostic Procedure

Monitor hardware temperature with system monitoring software like Speccy or HWMonitor:

Piriform - Speccy

CPUID - HWMonitor

For how to upload a screenshot or file, read here

Code:

Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue Jul 30 02:21:50.059 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:22.495
BugCheck F4, {3, fffffa80086e0b30, fffffa80086e0e10, fffff80003788350}
Probably caused by : wininit.exe
BUGCHECK_STR:  0xF4_5
PROCESS_NAME:  wininit.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Fri Jul 26 18:58:19.594 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:20.030
BugCheck F4, {3, fffffa8008770b30, fffffa8008770e10, fffff80003786350}
Probably caused by : wininit.exe
BUGCHECK_STR:  0xF4_5
PROCESS_NAME:  wininit.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Fri Jul 26 03:07:25.355 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:22.791
BugCheck F4, {3, fffffa80081b2b30, fffffa80081b2e10, fffff800037d3350}
Probably caused by : wininit.exe
BUGCHECK_STR:  0xF4_5
PROCESS_NAME:  wininit.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Jul 21 00:07:13.612 2012 (UTC + 6:00)
System Uptime: 1 days 22:48:39.048
BugCheck 1000009F, {4, 258, fffffa800416b660, fffff80000b9c510}
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``