Solved BSOD while watching a youtube video.

[Hovis]

Got a BSOD while watching a youtube video, 480p medium sized window.

I also had my music player open but wasn't listening to music at the time of the BSOD.

Files:
View attachment 199258

Help finding what caused this appreciated!

Thanks

 

[ePeen]

3B bugcheck, lists the probably caused fault as fltmgr.sys (Microsoft Filesystem Filter Manager). This was most likely not the cause of the crash itself, but something caused that specific driver to crash.

The process it has listed the caused the crash was ekrn.exe, which is part of the ESET NOD process/kernal. Please disable or uninstall NOD32 as your anti virus and report back.

Also another suggestion, my recommendation because you mentioned it happened while watching a YouTube video is to disable HWA (hardware acceleration) for YT playback just to test and see if that helps.

To disable it, simply go to any YouTube video (or flash video for that matter), right click it, Settings, and uncheck "Enable hardware acceleration".

Onto driver(s) that need updating:

ctac32k.sys - Wed Jul 02 04:38:22 2008 (Creative Audio Driver). Can be updated here.

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88000c12c1c, Address of the instruction which caused the bugcheck
Arg3: fffff88003a69920, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
fltmgr!FltReadFile+cdc
fffff880`00c12c1c 0000            add     byte ptr [rax],al

CONTEXT:  fffff88003a69920 -- (.cxr 0xfffff88003a69920)
rax=0000000000000001 rbx=fffffa8007551000 rcx=fffffa8007161640
rdx=0000000000000011 rsi=fffffa80070171d0 rdi=fffffa8006fc9a10
rip=fffff88000c12c1c rsp=fffff88003a6a300 rbp=0000000000000000
 r8=0000000000000000  r9=fffff88003a6a388 r10=fffffa80070171d8
r11=fffff88003a6a360 r12=fffffa80070171d0 r13=0000000000000000
r14=0000000000000011 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
fltmgr!FltReadFile+0xcdc:
fffff880`00c12c1c 0000            add     byte ptr [rax],al ds:002b:00000000`00000001=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  ekrn.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88000c12c1c

STACK_TEXT:  
fffff880`03a6a300 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!FltReadFile+0xcdc


FOLLOWUP_IP: 
fltmgr!FltReadFile+cdc
fffff880`00c12c1c 0000            add     byte ptr [rax],al

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  fltmgr!FltReadFile+cdc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fltmgr

IMAGE_NAME:  fltmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7929c

STACK_COMMAND:  .cxr 0xfffff88003a69920 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_fltmgr!FltReadFile+cdc

BUCKET_ID:  X64_0x3B_fltmgr!FltReadFile+cdc

Followup: MachineOwner

 

[Hovis]

Thanks, it's the first time ESET has caused a BSOD or been linked to one so I will re-install it. I don't want to remove it as I payed for a 1 year license and i'm only 2 months into it. However if it causes another BSOD I will have to find an alternative.

I will also disable hardware acceleration thanks for the tip.

I have PAX drivers (link) installed for my sound card which is based on the most recent driver from creative. SO unfortunately I can't update that driver as it is the most recent driver! I know... creative are awful!

Thanks for the help

 

[ePeen]

Ah, Pax Drivers.. the unofficial modded beta drivers? Be careful with those. Although it is true they are better than Creative's drivers, they are unofficial. I would personally recommend disabling ESET temporarily and installing MSE (microsoft security essentials) for testing purposes rather than a reinstallation, but again, whatever you'd like to try first.

I understand your frustration with purchasing a license. If it turns out to be ESET, I'd be more than happy helping you find a great alternative

 

[Hovis]

You're right about the PAX drivers they are unofficial and are based off the beta drivers from creative. However I think McClelland has done a great job as the most recent "stable" release from creative for Win 7 was released in Jun 2010 which I used to use and was fine but to be honest if very old. I then tried out the beta drivers from creative and they caused my PC to hard reset a lot so I went back to the old drivers. I then found the PAX drivers and gave them a shot and all I can say is that they really are something special, the sound quality that my Xtreme Gamer now outputs is very very good, incredibly crisp! McClelland has also made all the additional programs work really well on Win 7 like the volume panel and THX, although I tend not to play around with those much as, like you said, it is unofficial so it is questionable whether they can cause undesirable effects or not.

Anyway for the moment i'll play around with ESET and let you know if I run into any problems again. If I do I might have to take you up on your offer of some help on finding an alternative anti virus

Thanks !

 

[ePeen]

No problem, keep me updated

 

[Hovis]

Hey I don't know if you'll end up seeing this but I found out the reason I had got this BSOD and some system freezes (like literally my PC would completely freeze) since posting the original post was because my RAM wasn't getting enough voltage.

It was a long process to diagnose the problem, switching RAM in and out testing each stick and each slot, but I got there in the end.

I previously thought my RAM was fine as memtest returned zero errors during tests but my PC would still crash in games and occasionally while browsing the web. However since increasing the voltage my system has been stable.

Thanks for your help and I will now not be needing a new anti virus

I'll mark the thread as solved.

 

[ePeen]

Great to hear, Hovis! What was your DRAM voltage at prior to increasing it, and what's it at now?

 

[Hovis]

First off I have this RAM.

I had the sticks set to 1.6V which is what is recommended, however the RAM is 2 years old now so I guess they just needed a bit of a bumb due to their age and the amount of gaming they've been put through . I now have the voltage set to 1.66V. I also added +0.02V to my Northbridge voltage just to make sure

Also what was odd is that my system was perfectly stable when I had only 1 stick in the motherboard. But when I added +1, +2 or +3 sticks my system became unstable. I guess it's just to do with how my motherboard supplies the voltage.

 

[ePeen]

Hopefully that did the trick, although for a safety measure I would reduce it to 1.65v

 

[Hovis]

Hopefully that did the trick, although for a safety measure I would reduce it to 1.65v

I will see if the RAM is stable at 1.65V. Thanks for the heads up.

 

[ePeen]

No problem, best of luck. Let me know if you continue to have any issues.