Random BSOD/reboot

Here is your issue:

Event[34019]:
Log Name: System
Source: Ntfs
Date: 2012-08-20T05:58:51.774
Event ID: 55
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: BDP
Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.

Event[27360]:
Log Name: System
Source: Ntfs
Date: 2012-06-17T13:51:17.249
Event ID: 55
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: BDP
Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:.

This one is an old computer. So the HDD is also old I guess? The installation is very old, too. Even log starts a long way back.

Code:

  Date: 2011-07-03T20:14:37.000

Have you tried WD Data lifeguard? Try it again. Also give Seatools a go. Seatool for dos: SeaTools | Seagate download. Burn it in a blank cd or USB stick. boot from the CD or USB flash, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Also, I would suggest you to back up your data externally before doing those disc checks. Might be the HDD is failing. In this situation, first you need to keep your data secured.

Then, after the scans are done, format the HDD and reinstall windows. It will rectify the situation if it is a file system structure corruption only.

Have you ran malwarebytes ?

Post a screenshot of your HDD using CrystalDiskInfo.

HDD is fine .... so it is apparently seems that it is not the cause but the victim.

And here the trouble is lack of data. Make it sure that crash dump recording is properly configured.
Follow it: Dump Files - Configure Windows to Create on BSOD
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.

If still it is not a recorded dump, at least try to take a photograph. Event logs are silent about BSODs ...... otherwise at least the bugcheck code might give us a hint.

A lot of Ntfs, fltmgr and netio errors. Some examples ......

Code:

fffff880`02fcd320  fffff880`01276d28 Ntfs!NtfsStatusQueue+0x5528
fffff880`02fcd328  fffff880`0131e316 Ntfs! ?? ::NNGAKEGL::`string'+0x13e18
fffff880`02fcd330  fffff880`01270ca4 Ntfs!LfsData+0x84
fffff880`02fcd338  fffff880`0128e570 Ntfs!__PchSym_ <PERF> (Ntfs+0x6b570)
fffff880`02fcd448  fffff880`014065d2 NETIO!KfdClassify+0x934
fffff880`02fcd770  fffff880`0144e6e8 NETIO!handleTableLock
fffff880`02fceaa8  fffff880`0100caae fltmgr!FltpGetStreamListCtrl+0x8e
fffff880`02fceab8  fffff880`0102d5c5 fltmgr!SetStreamListStandardInformationFlags+0x1a5

And, Microsoft Network Inspection System Driver failure, too.

Code:

fffff880`02fcd628  fffff880`02a7f756Unable to load image NisDrvWFP.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NisDrvWFP.sys
*** ERROR: Module load completed but symbols could not be loaded for NisDrvWFP.sys
 NisDrvWFP+0xd756

It is not good as a sign. Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Also, if possible, update the BIOS and chipset for your BIOSTAR Group N68PA-M2T, from Biostar USA.