Solved BSOD 0x0F4 NO DMP files created

[mondonewc]

Hi Seven Forums.

I'm trying to trouble shoot some bsod problems for a friend (via teamviewer, so bare with me).

1 year old custom build, the bulk of the info should be set in the system specs pane.

A few weeks ago he wiped the pc and reinstalled windows. since then when he boots it up, when it's been left idle, opening skype or doing basic functions it bsods.

Having set W7 to save dump files, I cant get anything output in either windows/Memory.dmp OR in root/minidump meaning I don't have much to show you and checking other threads I cant find a specific reason for that. (seems similar to this thread http://www.sevenforums.com/bsod-hel...screen-stuttering-bsod-error-0x0000000f4.html ).

I include SF diag file though that cant get the dmp info, I also include a speccy screenshot and a crystal disk hd info screenshot of both drives.

As far as I or he can tell so far he has nothing OC, it's running only MSE/Mbytes/ccc AV wise.


Due to not physically being there and him using the computer for work I haven't yet tried to coach him through running memtest or furmark/prime95 etc.

There were hardly any non Microsoft drivers to test with driver verifier, those that there were caused no problems. Needless to say i've been through and checked that there are no important updates to be done and that all drivers are up to date as far as I can see.

Given that there are no dump files being output what should be the next step to try and diagnose the problems?


Thanks very much in advance.



EDIT-

Ran chk dsk and got no errors with the following output -

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 3)...
  662528 file records processed.                                          File verification completed.
  985 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              60 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 3)...
  978442 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 3)...
  662528 file SDs/SIDs processed.                                         Cleaning up 830 unused index entries from index $SII of file 0x9.
Cleaning up 830 unused index entries from index $SDH of file 0x9.
Cleaning up 830 unused security descriptors.
CHKDSK is compacting the security descriptor stream
  157958 data files processed.                                            CHKDSK is verifying Usn Journal...
  37459360 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

 241599487 KB total disk space.
  99075668 KB in 503338 files.
    158408 KB in 157961 indexes.
         0 KB in bad sectors.
    773131 KB in use by the system.
     65536 KB occupied by the log file.
 141592280 KB available on disk.

      4096 bytes in each allocation unit.
  60399871 total allocation units on disk.
  35398070 allocation units available on disk.

Internal Info:
00 1c 0a 00 3d 17 0a 00 34 94 0d 00 00 00 00 00  ....=...4.......
21 01 00 00 3c 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.

 

[Arc]

Hi mondonewc.

Make it sure that both your SSD's are running with the latest firmware.

• How to Upgrade OCZ SSD Firmware | StorageReview.com - Storage Reviews
• How to Upgrade Samsung SSD Firmware | StorageReview.com - Storage Reviews

Uninstall Marvell Sata Controller.

Then do it: http://www.sevenforums.com/tutorials/61869-ahci-enable-windows-7-vista.html

Let us know the results.

 

[mondonewc]

Much love for arc

Hey arc, thanks very much for the quick response.


We have upgraded the samsung ssd with magician, however the OCZ ssd is the primary drive and has windows installed on it so I can neither wipe it with the ocz program or update the firmware. Should I write an iso image of the toolbox and then look to upgrade the firmware that way? It's not a major loss to just completely wipe the system and reinstall win7 if that's easier/better?

Have uninstalled the marvell driver and enabled AHCI in the bios, this changed the setting from raid to AHCI will this cause any issues?


Will check back regularly for further instruction, and of course reply again if we experience any more BSOD in the meantime.

Thanks very much again.

 

[Arc]

Hey arc, thanks very much for the quick response.

You are welcome mate.

We have upgraded the samsung ssd with magician, however the OCZ ssd is the primary drive and has windows installed on it so I can neither wipe it with the ocz program or update the firmware. Should I write an iso image of the toolbox and then look to upgrade the firmware that way? It's not a major loss to just completely wipe the system and reinstall win7 if that's easier/better?

That is why the update to the OCZ firmware is needed. A stop 0xF4 is most commonly caused by a backdated firmware of the primary drive.

OCZ says .....
View attachment 308928
Have a look here: View attachment 308929

I hope it works smoothly for you.

Have uninstalled the marvell driver and enabled AHCI in the bios, this changed the setting from raid to AHCI will this cause any issues?

That is what was intended

 

[mondonewc]

Hey arc thanks very much again for the quick response.

We started up from the OCZ bootable toolbox and it said that there were no new updates available.

So far no new BSOD to report, hopefully that is the last of them.

I am going to tentatively mark this thread as solved and will obviously come running back to you if it goes wrong again.


Thanks once again for the quick responses.

 

[Arc]

I think you should have observed the situation for a couple of days more.

Anyway, if it goes any wrong again, we are here, give us a shout.