BCCode 50, numerous BSOD after turning computer on

[Problemek]

Within minutes after computer is turned on, I get BSOD. There is a restart and then I get BSOD again and so on. From time to time there is a pause in this cycle when everything seems to work but when I turn computer again the problem continues...

Další informace o problému:
BCCode: 50
BCP1: FFFFF9811A5426A8
BCP2: 0000000000000000
BCP3: FFFFF8800161AE00
BCP4: 0000000000000005
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Soubory, které popisují problém:
C:\Windows\Minidump\072315-37596-01.dmp
C:\Windows\Temp\WER-66378-0.sysdata.xml

 

[Arc]

The zip you uploaded does not contain any crash dump.

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup tool before you upload another zip.

 

[Problemek]

Thanks a lot! I have unfortunately run CCleaner before posting that zip. So now hopefully a zip with some info.

 

[Arc]

BugCheck 50, {fffff9811aa826a8, 0, fffff88001456e00, 5}


Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs![COLOR=Red]memcpy[/COLOR]+250 )

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

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

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

Let us know the result. A camera snap of the memtest86+ screen before closing the program will be nice.

 

[Problemek]

I have run the test overnight but no errors were found... Photo is attached.
I have done a hard disc partitioning 3 weeks ago. Could there be some connection with my current problems?

 

[Arc]

This image does not include all the required fields to infer about the result of the test.

View attachment 367371

 

[Problemek]

Thanks, here is a new one with whole screen covered.

 

[Arc]

Next, search for a driver which may pass bad info to the memory. Enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Problemek]

Here is a zip with a new crash dump...

 

[Arc]

This one is not seeming to be verifier enabled.

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

This string would mention about the verifier in that case.