BSOD at startup + random

[tenormanEd]

Hello, I have been getting BSOD before windows start up and some times after as well. I have posted the
windows error message I get after reboot and attatched dump files. Please let me know what other information I may provide.

Thank you.

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

Additional information about the problem:
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050033
BCP3: 00000000000406F8
BCP4: FFFFF800034C6E3F
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\111814-24460-01.dmp
C:\Windows\Temp\WER-36036-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

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

EDIT 1: My computer started restarting every 5-7 seconds. This makes me think I must at least have a hardware issue. This is just my intuition though. Thoughts?

 

[Arc]

There is a wide versatility in the bugcheck codes and the probable causes.

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.

It it does not show any error, 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.
____________________________________________________________

BugCheck 3B, {c0000005, fffff8000379e8d9, fffff88006b8f8f0, 0}

Probably caused by : ntkrnlmp.exe ( nt!CmpGetNameControlBlock+12e )

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

BugCheck 50, {fffff87ffc62c870, 8, fffff87ffc62c870, 5}


Could not read faulting driver name
Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+11f )

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

BugCheck D1, {fffffa8027308910, 2, 0, fffff880018fa8c9}

Probably caused by : NETIO.SYS ( NETIO!IndexListClassify+50 )

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

 

[tenormanEd]

I have ran memtest86 for 10 passes with no errors moving to next step.