BSOD With No Debug File

[Chicken89]

My PC will encounter a bluescreen and not write a minidump file.

Current Settings:
Startup and Recovery: checked write an event to system log and automatically restart, write small dump, small dump directory: %SystemRoot%\Minidump
Services: Windows Error Reporting Services enable on startup
Performance: pagefile managed by windows.

Reseated sata cables, memory sticks, ran memtest86+, windows memory diagnostic tool, and checked hard drive for errors.
Installed latest bios and storage controller drives.

The bluescreen error i get is 0x000000F4 and it occurs irregularly and usually at near idle.

.... also have the hotfix for hard drives with more than a 1 TB

 

[zigzag3143]

My PC will encounter a bluescreen and not write a minidump file.

Current Settings:
Startup and Recovery: checked write an event to system log and automatically restart, write small dump, small dump directory: %SystemRoot%\Minidump
Services: Windows Error Reporting Services enable on startup
Performance: pagefile managed by windows.

Reseated sata cables, memory sticks, ran memtest86+, windows memory diagnostic tool, and checked hard drive for errors.
Installed latest bios and storage controller drives.

The bluescreen error i get is 0x000000F4 and it occurs irregularly and usually at near idle.

.... also have the hotfix for hard drives with more than a 1 TB

without the dmp file all we can asceretain is

The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

I would run an system file check to verify the OD files.

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Let us know the results from the report at the end.

 

[Chicken89]

Found corrupt files, some were unable to be repaired.
This came up four times in the report:
2011-05-27 22:41:24, Info CSI 000004fc [SR] Cannot repair member file [l:24{12}]"xpsrchvw.exe" of Microsoft-Windows-XPSReachViewer, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-05-27 22:41:25, Info CSI 000004ff [SR] Cannot repair member file [l:24{12}]"xpsrchvw.exe" of Microsoft-Windows-XPSReachViewer, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-05-27 22:41:25, Info CSI 00000500 [SR] This component was referenced by [l:224{112}]"Microsoft-Windows-Xps-Foundation-Client-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.Xps-Foundation-Xps-Viewer"
2011-05-27 22:41:25, Info CSI 00000503 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:24{12}]"xpsrchvw.exe"; source file in store is also corrupted

 

[Chicken89]

Replaced xpsrchvw.exe from two installation disk of my copy of windows and another from a different copy (still win 7 pro 64 bit). Each time it said the file was corrupted when i ran SFC, even after replacing both the system32 and SysWOW64 xpsrchvw.exe files.

Ran chkdsk after all of that and it says there is no problem with my drive....

 

[zigzag3143]

Replaced xpsrchvw.exe from two installation disk of my copy of windows and another from a different copy (still win 7 pro 64 bit). Each time it said the file was corrupted when i ran SFC, even after replacing both the system32 and SysWOW64 xpsrchvw.exe files.

Ran chkdsk after all of that and it says there is no problem with my drive....

the way win 7 works is that it gets a hash of the date, file name, and size. If the ones you replace them with are not identical it will say corrupt. The one on your system may have been modified by some apps installer of update.

The preferred methed is to do a repair install.

 

[Chicken89]

I had the same blue screen problem and debug write before; this is already a clean reinstall of the OS. The xpsrchvw.exe file shouldn't have anything to do with the debug file not writing, right?

 

[Chicken89]

Problem was the Marvell SATA III controller. I plugged my hard drive into the Intel SATA II controller and it works fine with no BSOD now.