BSOD after dvd-rb instalation

[Jack'n'xbox]

Like the subject says I get the BSOD. I have run diagnostic software and all hardware comes up clean. The only new software is dvd-rb. I have had this error 3 times now. And was wondering if anyone else has dad this happen to them? I’m now uninstalling it, and will see what happens when I install it on another computer.

I just relised that I had read and earlier post about a new avisynth, so It could be that software too.

Heres the error

Stop: 0x000000f4 (0x00000003, 0x897DBBA8, 0x897DBD1C, 0x8064450)

Heres my minibump

[jdobbs]

It is something other than DVD-RB... otherwise it would be happening on other computers as well.

[Jack'n'xbox]

It is something other than DVD-RB... otherwise it would be happening on other computers as well.


Good to here.

Was thinking about AVG daily updates, the problem could be there.

Were the error code or minidumps any help, as for me they mean nothing.

thanks,

didn't mean to target your prog, I was starting to panic.

[Boulder]

You can download "Debugging Tools for Windows" from Microsoft's site, install it and use the open crashdump feature to open that minidump of yours. It can usually give you a clue regarding what caused the crash.

[shoarthing]

Agree with & further to above post: to get a clear idea of what's going on, install Windows Debugging Tools, & have an internet connection open:

1) Create folder c:\symbols
2) Download and install the latest debugging tools (http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx)
3) Locate your latest memory.dmp file - C:\WINDOWS\Minidump\minixxxxxx.dmp [to find exact name check event viewer/system]
4) Open a CMD prompt, then cd C:\program files\debugging tools for windows\
5) Type or paste the following code [adapting 'minixxxxxx.dmp' to true name], hit enter after each line:

kd -z C:\windows\mindump\minixxxxx.dmp
kd> .logopen c:\debuglog.txt
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q

. . . after analysis you'll now have a debuglog.txt in root C: