BSOD, possibly while using DVBViewer to record

BobFX · 11 Jan 2013

Before you mentioned testing in safe mode, I started to swap some hardware:

I have 2 PCs, PC1 the one that was crashing and PC2, that both record using an identical Technotrend sat card.

I swapped the 2 cards. PC2 did not start to crash, which seems to rule out a bard card.

However, at first, PC1 was not able to use the PC2 card: it did recognize it and loaded the correct driver, but "the device did not start".

After removing the driver, several times, rebooting, several times, removing physically the card and putting it back, suddenly it started to work. No idea why.

And so far, no more crashes! An overnight recording went without any problem.

I won't be sure that the problem vanished until at least one week of regular usage (although it reached the point where I could never record more than 15 minutes before a crash, so it's anyway better). I'll post here next week to keep you informed.

If I get new crashes, I'll test in safe mode.

BobFX · 12 Jan 2013

Well, it did not last long, it started crashing again.

I tried in safe mode. I did not get any crash, but I can't use the sat card in that mode, since its driver is not loaded.

However, to stress the PC, I ran the Windows version of Memtest.

The standalone Memtest86 version did not show any error, but this one did!

I removed half of the memory, and it stopped showing errors.

I'm retrying to record now, we'll see how it will go.

I find very surprising that Memtest86 (standalone) did not find any error, and that Memtest (Windows) did.

BobFX · 12 Jan 2013

Still crashing, I think that I need an exorcists!

koolkat77 · 14 Jan 2013

Sorry for the late response.
Can you upload new reports.

BobFX · 14 Jan 2013

koolkat77 said:

Sorry for the late response.
Can you upload new reports.

I changed the video renderer used by DVBViewer, and so far, it's not crashing anymore.

It probably won't last, I'll upload a report when it will happen again.

Thanks.

BobFX · 17 Jan 2013

Well, no more crashes in a couple of days, I think that I found the culprit.

There were apparently 2 problems: bad memory (not detected by standalone Memtest), and a video renderer not to be used with Win7.

Thanks for your tips, the process of elimination helped.

koolkat77 · 17 Jan 2013

Thanks for the update.

Let us know how things are after a week of observation.

BobFX · 23 Jan 2013

Well, the PC does no longer crash when recording, so that's a significant progress.

It does however crash when doing work that does intensive display, like when editing a recording with VideoRedo.

Please note that this PC is used over RDP. I made a few tries directly on the console, and could not trigger a crash. It's not 100% conclusive, I haven't found a way to make a systematic crash, but this could be happening only in an RDP session.

I attach the latest dumps, thanks.

koolkat77 · 23 Jan 2013

Caused by Acronis again.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800728b2a8, fffff8800728ab00, fffff80002dd794e}

*** WARNING: Unable to verify timestamp for tdrpm273.sys
*** ERROR: Module load completed but symbols could not be loaded for tdrpm273.sys
Probably caused by : tdrpm273.sys ( tdrpm273+46f3e )

Followup: MachineOwner
---------

Code:

fffff880`0728a378  fffff800`02af2bcb nt!KeQueryCurrentStackInformation+0x4b
fffff880`0728a380  fffff880`0728b2a8
fffff880`0728a388  fffff880`0728ab00
fffff880`0728a390  00000000`00000000
fffff880`0728a398  fffff880`0124ee28 Ntfs!_C_specific_handler
fffff880`0728a3a0  fffff880`0129dfa0 Ntfs!__PchSym_ <PERF> (Ntfs+0x68fa0)
fffff880`0728a3a8  fffff880`012b96b4 Ntfs!NtfsFsdFlushBuffers+0x104
fffff880`0728a3b0  00000000`00000000
fffff880`0728a3b8  fffff800`02af2aed nt!RtlpExecuteHandlerForException+0xd
fffff880`0728a3c0  fffff880`01286b60 Ntfs!NtfsStatusQueue+0x2350
fffff880`0728a3c8  fffff880`0728b7c0
fffff880`0728a3d0  00000000`00000000
fffff880`0728a3d8  fffff880`01235000 Ntfs!NtfsFreeReservedMdl <PERF> (Ntfs+0x0)
fffff880`0728a3e0  fffff880`0728a480
fffff880`0728a3e8  fffff800`02af18c5 nt!RtlDispatchException+0x415
fffff880`0728a3f0  fffff880`01286b60 Ntfs!NtfsStatusQueue+0x2350
fffff880`0728a3f8  fffff880`0728a438
fffff880`0728a400  fffff880`0728b2a8
fffff880`0728a408  fffff880`01235000 Ntfs!NtfsFreeReservedMdl <PERF> (Ntfs+0x0)
fffff880`0728a410  00000000`00000000
fffff880`0728a418  fffffa80`01e57a00
fffff880`0728a420  fffffa80`02946cb8
fffff880`0728a428  fffffa80`0293bd80
fffff880`0728a430  fffff880`0728b7c0
fffff880`0728a438  fffff880`01235000 Ntfs!NtfsFreeReservedMdl <PERF> (Ntfs+0x0)
fffff880`0728a440  fffff880`01286b60 Ntfs!NtfsStatusQueue+0x2350
fffff880`0728a448  fffff880`0728a9a0
fffff880`0728a450  00000000`00000000
fffff880`0728a458  fffff880`0129dfa0 Ntfs!__PchSym_ <PERF> (Ntfs+0x68fa0)
fffff880`0728a460  fffff880`0728c000
fffff880`0728a468  fffff880`07284000
fffff880`0728a470  00000000`00000000
fffff880`0728a478  00000000`00000000
fffff880`0728a480  fffff880`012b96b4 Ntfs!NtfsFsdFlushBuffers+0x104
fffff880`0728a488  fffff880`01235000 Ntfs!NtfsFreeReservedMdl <PERF> (Ntfs+0x0)
fffff880`0728a490  fffff880`0129dfa0 Ntfs!__PchSym_ <PERF> (Ntfs+0x68fa0)
fffff880`0728a498  fffff880`0728b7c0
fffff880`0728a4a0  fffffa80`01e57a60
fffff880`0728a4a8  fffff880`0728a4d0
fffff880`0728a4b0  fffff880`0124ee28 Ntfs!_C_specific_handler
fffff880`0728a4b8  fffff880`01286b60 Ntfs!NtfsStatusQueue+0x2350
fffff880`0728a528  fffff880`01bb65c2Unable to load image \SystemRoot\system32\DRIVERS\snapman.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
 snapman+0x235c2
fffff880`0728a9a8  fffff800`02dd7830 nt!FsRtlNotifyFilterReportChange
fffff880`0728a9b0  fffff880`012b9700 Ntfs!NtfsQueryStreamsInfo
fffff880`0728a9b8  fffff800`02a49000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`0728a9c0  fffff800`02ce30d4 nt!BBTBuffer <PERF> (nt+0x29a0d4)
fffff880`0728a9c8  fffff880`01235000 Ntfs!NtfsFreeReservedMdl <PERF> (Ntfs+0x0)
fffff880`0728a9d0  fffff880`0129bac8 Ntfs!__PchSym_ <PERF> (Ntfs+0x66ac8)
fffff880`0728a9d8  fffff880`01235000 Ntfs!NtfsFreeReservedMdl <PERF> (Ntfs+0x0)
fffff880`0728a9e0  fffff880`0129df88 Ntfs!__PchSym_ <PERF> (Ntfs+0x68f88)
fffff880`0728a9e8  fffff880`01235000 Ntfs!NtfsFreeReservedMdl <PERF> (Ntfs+0x0)
fffff880`0728a9f0  fffff880`0129dfa0 Ntfs!__PchSym_ <PERF> (Ntfs+0x68fa0)

And you may need to add more ram to your system.

BobFX · 23 Jan 2013

But, remember, I still had those video related crashes when I removed Acronis!