Help me identify the BSoD.

iAmAdrian

Distinguished
Dec 15, 2013
272
0
18,780
This is the info I have.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: FFFFF900C2573CF0
BCP2: 0000000000000000
BCP3: FFFFF960002BC69D
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\021714-32011-01.dmp
C:\Users\Adrian\AppData\Local\Temp\WER-44195-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Please tell me what I need to provide in order to determine the cause.

Thanks,
Adrian
 
bccode error 50 is usually associated with a hard fail on storage. whether it be ram, vram of the hdd so this is 1 of them hard to reach errors...
check through previous errors as they may help you pinpoint a more general area of the fault. often 2-3 different errors can point to the same failed hardware.
 

brarboy

Honorable
here is another method with bootable USB.
Download Auto Installer USB key from here: http://www.memtest.org/download/5.01/memtest86+-5.01.usb.installer.zip
extract it and run Memtest86+ USB Installer. Then follow the onscreen instructions. Reboot your computer and set your system BIOS to boot from USB-ZIP or USB-HDD. Or, set the hard disk boot priority to boot from the USB stick if your BIOS lists the device as a hard drive
Save your BIOS settings and reboot. Upon reboot, you should have a successful launch of Memtest86+ from the USB flash drive.
 
Apply the service pack and the updates to your old version of windows 7 RTM version.
you had a driver at memory location FFFFF960002BC69D
try to read from memory location FFFFF900C2573CF0 and got error because the address was not in memory and it was required to be in memory
(not on the hard drive)

if you have the debug memory dump you would just look to see what dirver was at the memory location FFFFF960002BC69D
and update the driver. If it is a windows provide driver you check to see it has been corrupted and repair it.
(use the system file checker command sfc.exe /scannow)