BSOD once every 3-4days, Stop 0xf4

talon03 · 22 Sep 2012

Hey again... had another crash, uploading the latest dump.

koolkat77 · 22 Sep 2012

Hmm. dump doesn't give proper information.
Please enable verifier again for 36 hours.

talon03 · 24 Sep 2012

Ok.. verifier's picked something else up now, I put an audio CD in the drive there and it BSODed on me.
Also, I uninstalled Daemon tools a few days ago.
Uploading latest dumps.

JMV2009 · 24 Sep 2012

Try hcidesign.com/memtest. Upgrade bios, upgrade sdd/hdd firmware.

Good luck.

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc500a0a38, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc00000c0, error status (normally i/o status code)
Arg3: 00000001e41f8880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a0141474b0, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address

koolkat77 · 24 Sep 2012

Umm..get an update for its driver or uninstall it if you wish. CyberLink Software Updates

Code:

1: kd> lmvm CLBUDF
start             end                 module name
fffff880`05a00000 fffff880`05a6a000   CLBUDF   T (no symbols)           
    Loaded symbol image file: CLBUDF.SYS
    Image path: \SystemRoot\System32\Drivers\CLBUDF.SYS
    Image name: CLBUDF.SYS
    Timestamp:        Wed Oct 07 12:42:23 2009 (4ACC384F)
    CheckSum:         0006904B
    ImageSize:        0006A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

talon03 · 12 Oct 2012

Soooo... it's been about 2 weeks since the last BSOD, so I'm going to go ahead and mark this as solved.

I think the problem was my SSD unmounting itself. Before the last crash I heard that windows unplugged sound, and the pc became unresponsive before crashing.
I updated the BIOS, which caused all manners of pain and hurt. The new BIOS didn't recognise my RAM as being compatible and wouldn't even go to POST, so I had to use the USB flashback feature on the motherboard to downgrade the BIOS back to what it was.
After that, I discovered that my motherboard apparently has two SATA controllers, and that I'd installed drivers for both of them. I figured this might be causing a conflict so I uninstalled one of them and haven't had a problem since.

Thanks for all the help koolkat77!

koolkat77 · 12 Oct 2012

Thanks for reporting back. Glad to hear you got it sorted.