Solved BSODs when using dailymotion, youtube etc

[noob1]

I will bug test tomorrow just to rule out the possibility that the network driver was the problem, but should the BSOD persist I'd like to try single channel even if it does mean a compromise on speed - would it be possible for me to move to single channel, and if so, how would I do that?

 

[richc46]

Try one stick

 

[noob1]

The missus bug tested again today and there was another BSOD (see attached).

Is there a way I can test single channel memory with 2 stick as opposed to one or the three which I currently have?

 

[richc46]

The advice that I give is limited to the dmp resports. Here is your latest one.

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_noob1.zip\SF_13-09-2012\Mini091312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18607.x86fre.vistasp2_gdr.120402-0336
Machine Name:
Kernel base = 0x89010000 PsLoadedModuleList = 0x89127c70
Debug session time: Thu Sep 13 08:10:50.206 2012 (GMT-4)
System Uptime: 0 days 0:11:37.952
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 891ffdc2, bff5c7cc, 0}
Probably caused by : memory_corruption ( nt!MiRelocateImageAgain+38 )
Followup: MachineOwner
---------

I cant answer that question about memory but download speccy. It will tell you if you have dual or single, so you can test different options. Try putting the sticks in consecutive slots and then alternate, see if there is any change.

 

[tom982]

Rich, sorry to barge in on your thread, but I spotted something on one of the dumps which I don't know if you've seen or not:

Microsoft (R) Windows Debugger Version 6.2.8400.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Tom\AppData\Local\Temp\Temp1_noob1.zip\SF_13-09-2012\Mini091012-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18607.x86fre.vistasp2_gdr.120402-0336
Machine Name:
Kernel base = 0x8903e000 PsLoadedModuleList = 0x89155c70
Debug session time: Mon Sep 10 22:18:44.341 2012 (UTC + 1:00)
System Uptime: 0 days 0:16:34.123
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 89082996, cfd79934, 0}

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

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 89082996, The address that the exception occurred at
Arg3: cfd79934, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP: 
nt!IofCallDriver+5f
89082996 ff548838        call    dword ptr [eax+ecx*4+38h]

TRAP_FRAME:  cfd79934 -- (.trap 0xffffffffcfd79934)
ErrCode = 00000000
eax=00000000 ebx=8de8bbd8 ecx=0000000d edx=8de90008 esi=e740e21c edi=8de90008
eip=89082996 esp=cfd799a8 ebp=cfd799b8 iopl=0         nv up ei ng nz na po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010283
nt!IofCallDriver+0x5f:
89082996 ff548838        call    dword ptr [eax+ecx*4+38h] ds:0023:0000006c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  avp.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 891dd42c to 89082996

STACK_TEXT:  
cfd799b8 891dd42c 8ef7ea20 8900f030 8900f0c0 nt!IofCallDriver+0x5f
cfd79a1c 890f60c7 8ef7ea20 8dc5a701 00000000 nt!IopMountVolume+0x1ce
cfd79a4c 8927cf4a 8dc5a700 cfd79b70 cfd79b08 nt!IopCheckVpbMounted+0x60
cfd79b28 8926baec 8ef7ea20 00000000 8df59008 nt!IopParseDevice+0x7fe
cfd79bb8 89279084 00000000 cfd79c10 00000040 nt!ObpLookupObjectName+0x5a8
cfd79c1c 8927e7be 1e83f29c 00000000 89254601 nt!ObOpenObjectByName+0x13c
cfd79c90 8928036f 1e83f300 c0100080 1e83f29c nt!IopCreateFile+0x63b
cfd79cdc 986a4b44 1e83f300 c0100080 1e83f29c nt!NtCreateFile+0x34
WARNING: Stack unwind information not available. Following frames may be wrong.
cfd79d30 89088c3a 1e83f300 c0100080 1e83f29c klif+0x2db44
cfd79d30 77705cd4 1e83f300 c0100080 1e83f29c nt!KiFastCallEntry+0x12a
1e83f2f8 00000000 00000000 00000000 00000000 0x77705cd4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
klif+2db44
986a4b44 ??              ???

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  klif+2db44

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: klif

IMAGE_NAME:  klif.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ca58e03

FAILURE_BUCKET_ID:  0x8E_klif+2db44

BUCKET_ID:  0x8E_klif+2db44

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

This one points to klif.sys as being the fault. klif.sys is Kaspersky Lab Internet Firewall so it could explain why the computer BSODs when watching Youtube etc. which are really network intensive tasks. Might be worth trying removing Kaspersky?

 

[noob1]

That sounds highly likely, because when I changed my Broadband provider, not knowing what I was doing, in KIS 11 I set the status of my LAN to "Public Network" (there are 3 possible statuses being "Public", "Local" and "Trusted"). Ever since then I've been seeing this problem.

For the moment I've set the LAN to "Local Network" and I'll bugtest tomorrow. If no improvement then I'll take off KIS.

 

[richc46]

Any ideas are very welcome. This is an art rather than a science. Its been my experience that when you have a menu of causes, it is usually hardware and memory error came up many times.

 

[noob1]

Hi again,

I got rid of Kaspersky and got Macafee instead. Even when my system was running without a firewall I got a BSOD, this time while downloading the Macafee software. Once Macafee was running, nothing appears to have changed as I still get the screen freezes, sometimes accompanied by the BSOD, other times I am just unable to do anything so I perform a forced shutdown.

Maybe it is the dual channel memory which is the offender...

I've attached latest dump.

 

[richc46]

Based upon my experience, your dmps showing AV etc, etc, points to hardware. What is the status of the memory test?

 

[noob1]

memtest was clean - all passes for each stick individually and all working together.

 

[richc46]

One of these dumps points toward network, update your network adapter driver. If still BSODs, we continue with hardware after testing with driver verifier.

 

[noob1]

I have already updated the network adaptor driver (I did it when you suggested updating graphics and network drivers) but the problem persists.

 

[richc46]

Do you know if you are overheating. Ever read the temps?

 

[noob1]

According to Speccy (approximate values): CPU is 58, motherboard is 40 and hard drives are 35.

 

[richc46]

Ok Go to the website of your hard drive mfg (speccy will tell you who that is) and test hard drive.
temps are fine.

 

[noob1]

Okay, I feel confident enough (though slightly cautious) in saying that after 5 days of no BSODs or freezes, I finally found out the problem.

Richc46, my apologies, it was the drivers for my network adaptor after all. I use a Belkin USB wireless network adaptor v.4. Earlier on in the diagnostics I did attempt (and thought I had succeeded) to update the drivers but it turns ou this was not the case. Device manager showed I had the 2007 drivers but I found out on another forum that my particular adaptor had, in 2009, its drivers updated.

I updated the drivers on Sunday and haven't had a problem since.

The problem was, it would appear, precipitated by a new router after I changed my broadband provider. The most notable difference between the new router and the old one is that the new one had wireless N capability.

Thank you so much for taking me through the diagnostics - we finally did solve the problem!

 

[richc46]

Im glad that I was able to help sort out your BSOD problem.