📎 AI Summary:
The thread discusses a Windows 8.1 user experiencing a BSOD caused by memory corruption, with detailed analysis suggesting potential issues with faulty hardware, drivers, or system software like antivirus programs. Expert advice includes updating drivers, removing conflicting security software, checking BIOS and firmware updates, and testing RAM with Memtest86. The overall sentiment is troubleshooting-oriented, emphasizing systematic hardware and software checks to identify and resolve the underlying cause of the BSOD.
M

Martin Hickie

Senior Member
Member details
Joined
Apr 1, 2011
Messages
25
Thread Author #1
This BSOD has just started today. My computer unexpectedly rebooted itself while printing. I don't know what the cause is as the cpu and ram is all ok but i don't know how to test the 2x dvd roms and the hdd just to make sure them are working ok too. I have a minidump file in my onedrive so can someone take a look at it and tell me what caused the BSOD.

https://onedrive.live.com/redir?resid=CA20511261C3DC5E!2564

The minidump file is in a zip folder called Win8.1 32bit minidump.
 

Solution
kemical
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {b0df8c38, 0, 8163e92f, 0}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiCaptureProtectionFromProto+d )

Followup: MachineOwner
Hi,
causes for the bugcheck can be:
Bug check 0x50 usually occurs after the installation of faulty...
Sort by date Sort by votes
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#2
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {b0df8c38, 0, 8163e92f, 0}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiCaptureProtectionFromProto+d )

Followup: MachineOwner
Hi,
causes for the bugcheck can be:
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

SRTSP.SYS Mon Feb 10 23:03:36 2014: Norton Anti-Virus which is well known for causing issues. Try uninstalling with this removal tool:
https://support.norton.com/sp/en/uk/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us

RapportEI.sys Thu Jul 10 17:21:56 2014: Trusteer Ltd. Rapport Security software driver, as above please remove.

In their place run MSE as it's very stable:
Link Removed

BiosVersion = F1
BiosReleaseDate = 12/09/2009
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-MA770T-ES3
You also have Bios updates pending. Check on the revision of your motherboard by looking on the actual board itself (either 1.0 or 1.3) and apply the correct download accordingly. You'll notice on the support page the two different version numbers so make sure you get the right motherboard.
http://www.gigabyte.com/products/product-page.aspx?pid=3466#bios

If you have an SSD check for Firmware updates and for both SSD/SATA drives run a chkdsk:
http://www.tekrevue.com/tip/how-to-scan-fix-hard-drives-with-chkdsk-in-windows-8/

Rtnicxp.sys Fri May 30 16:12:11 2008: Realtek ethernet driver please update:
Link Removed

If after making the above changes you still get the bsod then you need to test your RAM.
Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
http://www.memtest.org/

To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
Try and run the test overnight if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

Post any new dump files.
 
Upvote 1 Downvote
Solution
You must log in or register to reply here.