Comments on: BSOD Stop: 0x000000F4 (0×00000003, 0x8982F218, 0x8982F38C, 0x805D1204) http://itknowledgeexchange.techtarget.com/itanswers/bsod-stop-0x000000f4-0x00000003-0x8982f218-0x8982f38c-0x805d1204/ Sat, 18 May 2013 17:13:23 +0000 hourly 1 By: kevinbeaver http://itknowledgeexchange.techtarget.com/itanswers/bsod-stop-0x000000f4-0x00000003-0x8982f218-0x8982f38c-0x805d1204/#comment-60914 kevinbeaver Tue, 17 Mar 2009 14:48:29 +0000 #comment-60914 Can you start it up long enough – perhaps in Safe Mode – and run a malware scan? That may be doing it…bad memory or other failing hardware can contribute to something like this as well.

]]> By: pjb0222 http://itknowledgeexchange.techtarget.com/itanswers/bsod-stop-0x000000f4-0x00000003-0x8982f218-0x8982f38c-0x805d1204/#comment-60869 pjb0222 Mon, 16 Mar 2009 16:55:07 +0000 #comment-60869 Look at the event log for any further error messages.
I suggest enabling at least mini-dumps.
If you have a dump file, you can use the MS debugging tools to read the dump and get some details about the STOP error.

As to the parameters after the STOP code, MS support is about the only group who can sdecipher and they need a dump file to analize.

]]> By: mrdenny http://itknowledgeexchange.techtarget.com/itanswers/bsod-stop-0x000000f4-0x00000003-0x8982f218-0x8982f38c-0x805d1204/#comment-60845 mrdenny Sun, 15 Mar 2009 21:00:03 +0000 #comment-60845 What else did it say on the screen? Perhaps a file name?

]]>