BSOD on multiple occasions... Error 0x0000007A and 0x000000F4

Yea, i ran malwarebytes scan originally before i even started this thread and it never found anything

Man microsoft sercuirty essentials took a really long time... almost 6 hours but it didnt find anything... im going to try the windows repair now...

Good luck!

Windows Repair couldn't find anything :-( man I am about to give up...

Nonsense! I understand your frustration, but we'll get you up & running, just don't give up!

We've gone through most tests, and the only one so far that has shown errors is the Seagate hard drive diagnostics, so I strongly believe it is your hard drive. I will show this thread to another brilliant member here. Reasons being is because my hard drive knowledge isn't the best and I am unsure of what tests to run and which program / windows app is best for this.

Hang in there :)

ePeen said:

Oh wow.. tough break, your luck is almost as bad as mine. Call Samsung and let them know the tools have found errors and such, and describe your issue to them and what we've gone through already to eliminate other culprits. Hopefully if you're under warranty and they'll replace the drive.

You will actually want to contact Seagate. See if the link provided in the following quote helps as well.

Now that the sale of HDD division of Samsung Electronics to Seagate Technology Plc("Seagate") has been finalized, Seagate will provide all customer support including the warranty service of Samsung HDD.

For more information, visit Seagate's Samsung subsite

Having visited the site myself, I cannot find anything useful other than the option to contact Seagate for full support on Samsung drives. You should explain to Seagate that their diagnostic software will not repair your drive even though they promise full support for Samsung drives.



Also, have you run Disk Check with both boxes checked? Can you post the logs after doing so by following the steps in Check Disk (chkdsk) - Read Event Viewer Log

Yea, i have called seagate and they tell my hard drive isn't under warranty and that there isn't much they can do. The lady was actually pretty rude... but anywho... i try to run the CHKDSK with both boxes checked, but it wont let me. It tells my that the hard drive is in use and to schedule the CHKDSK for the next time windows restarts. The only problem with this, is that it says it's doing it and then just for like 3-4 seconds and then just shots right to Windows login screen. Not sure what to do about that... i have ran the CHKDSK with the "Scan for and attempt recovery of bad sectors" however the results come back error free. The CHKDSK does let me run both boxes checked on my recovery partition, just not my C: partition. I am running fresh tests on the recovery partition right now and will run the "Scan for and attempt recovery of bad sectors" test for the C: partition and i will report back with the logs. Thanks for all your help.

You can run the disk check outside of Windows, but it will not generated the logs. You will have to let us know what it says.

Use Advanced Boot Options to select Repair Your Computer and get to the System Recovery Options. Then select the command prompt. Do the following:

chkdsk /r c:
chkdsk /r d:
chkdsk /r e:
chkdsk /r f:

.etc until you get the message that the volume could not be opened for direct access. For any drives that do not give the message:
"Windows has checked the file system and found no problems"
run chkdsk again as above. In other words, if it says:
"Windows has made corrections to the file system"
after running the disk check, run the disk check again.

I realize you may only have one disk show up in Windows explorer, but you may have more than one disk through recovery options. This is because the system creates a hidden boot partition (which will be C: in recovery), you may have a recovery partition for your PC that is hidden (which will be D: in recovery), and you will have your primary Windows partition (which may be E: in recovery). A custom PC will likely have at least C: and D: to scan.

here are the logs... i had finally got it to run right when the computer restarted it didnt skip it... it actually did what it was supposed to this time... here are the logs...

Code:

　
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk. 
CHKDSK is verifying files (stage 1 of 5)...
324096 file records processed. File verification completed.
1604 large file records processed. 0 bad file records processed. 0 EA records processed. 45 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
402674 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
324096 file SDs/SIDs processed. Cleaning up 191 unused index entries from index $SII of file 0x9.
Cleaning up 191 unused index entries from index $SDH of file 0x9.
Cleaning up 191 unused security descriptors.
Security descriptor verification completed.
39290 data files processed. CHKDSK is verifying Usn Journal...
36242600 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc0000185 at offset 0x9c671e000 for 0xe000 bytes.
Read failure with status 0xc0000185 at offset 0x9c6725000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x9c671e000 for 0x7000 bytes.
Read failure with status 0xc0000185 at offset 0x9c6726000 for 0x6000 bytes.
Read failure with status 0xc0000185 at offset 0x9c6727000 for 0x1000 bytes.
Windows replaced bad clusters in file 154091
of name \Windows\Prefetch\LOGONU~1.PF.
324080 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
12428722 free clusters processed. Free space verification is complete.
Adding 2 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
299526143 KB total disk space.
249263044 KB in 213301 files.
112152 KB in 39291 indexes.
8 KB in bad sectors.
436051 KB in use by the system.
65536 KB occupied by the log file.
49714888 KB available on disk.
4096 bytes in each allocation unit.
74881535 total allocation units on disk.
12428722 allocation units available on disk.
Internal Info:
00 f2 04 00 bc da 03 00 d4 db 06 00 00 00 00 00 ................
b9 05 00 00 2d 00 00 00 00 00 00 00 00 00 00 00 ....-...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Windows has finished checking your disk.
Please wait while your computer restarts.

and

Code:

Chkdsk was executed in read/write mode. 
Checking file system on D:
Volume label is RECOVERY.
CHKDSK is verifying files (stage 1 of 5)...
256 file records processed. File verification completed.
0 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
312 index entries processed. Index verification completed.
　
CHKDSK is verifying security descriptors (stage 3 of 5)...
256 file SDs/SIDs processed. Cleaning up 1 unused index entries from index $SII of file 0x9.
Cleaning up 1 unused index entries from index $SDH of file 0x9.
Cleaning up 1 unused security descriptors.
Security descriptor verification completed.
29 data files processed. CHKDSK is verifying Usn Journal...
376480 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
240 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
538894 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.
12838911 KB total disk space.
10616200 KB in 54 files.
20 KB in 30 indexes.
67115 KB in use by the system.
65536 KB occupied by the log file.
2155576 KB available on disk.
4096 bytes in each allocation unit.
3209727 total allocation units on disk.
538894 allocation units available on disk.

here are some other things that i noticed in that app man that might be why my start up be messing up so much with the wifi going off and on and the task bar changing colors back and forth for like first 10-15 minutes....

Code:

The Desktop Window Manager has exited with code (0xd0000450)

Code:

Windows cannot access the file C:\Windows\Prefetch\LOGONUI.EXE-09140401.pf for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Host Process for Windows Services because of this error.
Program: Host Process for Windows Services
File: C:\Windows\Prefetch\LOGONUI.EXE-09140401.pf
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
Additional Data
Error value: C0000185
Disk type: 3

Code:

Faulting application name: svchost.exe_SysMain, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: sysmain.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c9db
Exception code: 0xc0000006
Fault offset: 0x000000000000f947
Faulting process id: 0x13dc
Faulting application start time: 0x01ccf5d143fb5ba8
Faulting application path: C:\Windows\System32\svchost.exe
Faulting module path: c:\windows\system32\sysmain.dll
Report Id: b2a0d5df-61c4-11e1-b7ea-00262db6027d

Code:

Faulting application name: svchost.exe_SysMain, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: sysmain.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c9db
Exception code: 0xc0000006
Fault offset: 0x000000000000f947
Faulting process id: 0x398
Faulting application start time: 0x01ccf5d113044d45
Faulting application path: C:\Windows\System32\svchost.exe
Faulting module path: c:\windows\system32\sysmain.dll
Report Id: 8143ecbc-61c4-11e1-b7ea-00262db6027d

Code:

The description for Event ID 0 from source gupdate cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
Service stopped

Code:

The Desktop Window Manager has exited with code (0xd0000450)

Code:

The description for Event ID 0 from source iPod Service cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
Service started

Code:

mDNSCoreReceiveResponse: Unexpected conflict discarding 19 4.0.168.192.in-addr.arpa. PTR cdguy707-PC.local.

Code:

The description for Event ID 0 from source HPSLPSVC cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
Service started

Code:

The description for Event ID 0 from source hpqcxs08 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
Service started

Code:

The description for Event ID 0 from source YahooAUService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
Service started

Code:

The Windows Management Instrumentation service has detected an inconsistent system shutdown.

Code:

The description for Event ID 0 from source SignInAssistant cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
WLIDInitializationTimerQueue. QueueWorkItem started (23:45:65)

Code:

The description for Event ID 0 from source SignInAssistant cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
g_ WLIDInitializationTimerQueue.Initialize started (23:45:65)

Code:

The description for Event ID 0 from source SignInAssistant cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
g_WLIDTimerQueue.Initialize started (23:44:878)

Code:

The description for Event ID 0 from source RichVideo cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
Service started

Code:

The description for Event ID 0 from source hpqddsvc cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
Service started

Code:

The winlogon notification subscriber <SessionEnv> was unavailable to handle a notification event.