BSOD happening all the time

Hi all,

My pc was great until a few months ago, running smoothly, perfect. But sundelly he just starting BSDO from time to time and I decided to format it, I put the latest drivers and did windows update and the problem still..

Anyway I processed the dumps and here they are, if anyone is willing analize it I would appreciate it. Thanks a lot..


bugcheck + driver: DRIVER_VERIFIER_DETECTED_VIOLATION tcpip.sys

bugcheck + parameter 1: DRIVER_VERIFIER_DETECTED_VIOLATION 00000000`00000091

koolkat77 said:

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Usra\Downloads\SF_17-03-2014\SF_17-03-2014\031714-18142-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02c12000 PsLoadedModuleList = 0xfffff800`02e556d0
Debug session time: Tue Mar 18 05:16:42.857 2014 (UTC + 6:00)
System Uptime: 0 days 0:47:45.684
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {91, 2, fffffa800905fb50, 0}

*** WARNING: Unable to verify timestamp for kltdi.sys
*** ERROR: Module load completed but symbols could not be loaded for kltdi.sys
Probably caused by : tdx.sys ( tdx!TdxSendConnection+252 )

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

Information Source
kltdi.sys
Kaspersky Network filtering component
Support: http://usa.kaspersky.com/support
Downloads: Free Kaspersky Antivirus Trial | Kaspersky Lab US
Unable to get links from the Global website - sorry!

Please remove Kaspersky for testing purpose. Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

Good and Free system security combination.

Keep us posted.

I just remove Kasp for testing like you suggest, I'll reply in 1 week. Thanks!

Hi again,

Today I was working and suddenly a BSDO happened.. I'm attaching the Dump file.. Thanks.

koolkat77 said:

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Usra\Downloads\031914-26005-01\031914-26005-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02c4a000 PsLoadedModuleList = 0xfffff800`02e8d6d0
Debug session time: Wed Mar 19 09:24:13.609 2014 (UTC + 6:00)
System Uptime: 0 days 0:44:23.811
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80043f7310, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa80043f7310
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002d30d50 to fffff80002cbfbc0

STACK_TEXT:  
fffff880`0a3c2748 fffff800`02d30d50 : 00000000`0000001a 00000000`00041790 fffffa80`043f7310 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0a3c2750 fffff800`02c90e75 : ffffffff`00000000 00000000`0543ffff fffffa80`00000000 fffffa80`0729b840 : nt! ?? ::FNODOBFM::`string'+0x35084
fffff880`0a3c2910 fffff800`02f9415a : fffff8a0`0b423580 00000000`00000001 00000000`00000000 fffffa80`0729b840 : nt!MmCleanProcessAddressSpace+0x679
fffff880`0a3c2960 fffff800`02f786b8 : 00000000`c000004b 00000000`00000001 00000000`fffdb000 00000000`00000000 : nt!PspExitThread+0x56a
fffff880`0a3c2a60 fffff800`02cbee53 : fffffa80`0a582060 fffff880`c000004b fffffa80`0729b840 fffffa80`00008000 : nt!NtTerminateProcess+0x138
fffff880`0a3c2ae0 00000000`77be157a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0019de68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77be157a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+35084
fffff800`02d30d50 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+35084

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

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

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

ok I'll post results as soon as possible

thx again

essenbe said:

night21, It is always better to buy matched sets of memory. Most makor manufacturers test memory modules to work together in a kit. 2 memory modules from different manufacturers or even the same specd modules from the same manufacturer will sometimes cause problems.

Yes.. the memories are Markivision, next time I'll buy G-skill or even Kingston.

Topic solved.

Thx