BSOD cash randomly hapen after a litle time my desktop PC is on rest

Hi -

No .dmps in the attachment.

Configure system to generate small memory .dmps (minidumps) following: Dump Files - Configure Windows to Create on BSOD next time you get a BSOD, grab all, zip and upload.

Problematic software:

Code:

Start Menu\Programs\Panda Global Protection 2013	Public:Start Menu\Programs\Panda Global Protection 2013	Public
Start Menu\Programs\Panda Global Protection 2013\Herramientas adicionales	Public:Start Menu\Programs\Panda Global Protection 2013\Herramientas adicionales	Public
Start Menu\Programs\Panda Security	Public:Start Menu\Programs\Panda Security	Public
Start Menu\Programs\Panda Security\Panda Cloud Cleaner	Public:Start Menu\Programs\Panda Security\Panda Cloud Cleaner	Public
Start Menu\Programs\Panda Security\Panda Secure Vault	Public:Start Menu\Programs\Panda Security\Panda Secure Vault	Public
Start Menu\Programs\Panda Security\Panda USB Vaccine	Public:Start Menu\Programs\Panda Security\Panda USB Vaccine	Public

Code:

Probably caused by : NETTDI64.SYS ( NETTDI64+3633 )

Driver Description: Panda Internet Security TDI Filter
Your BSOD's were caused by your antivirus. Please remove it using its removal tool from here: Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase. If no uninstaller is available, uninstall using the Free version of Revo Uninstaller free in advanced mode and delete registry leftover of the program: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

We recommended Microsoft Security Essentials from a strict BSOD perspective. Is most compatible & provides most stability compared to other antivirus app/Internet Security Software.

• Microsoft Security Essentials, Free antivirus for windows
• Malwarebytes Anti-Malware Free
• Good and Free system security combination

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

System Optimisers

Please remove the following software:

Code:

Start Menu\Programs\Advanced SystemCare 6	Public:Start Menu\Programs\Advanced SystemCare 6	Public
Start Menu\Programs\PC Tools Registry Mechanic	Public:Start Menu\Programs\PC Tools Registry Mechanic	Public
Start Menu\Programs\ParetoLogic	pc-PC\pc:Start Menu\Programs\ParetoLogic	pc-PC\pc
Start Menu\Programs\ParetoLogic\RegCure Pro	pc-PC\pc:Start Menu\Programs\ParetoLogic\RegCure Pro	pc-PC\pc

This software is a known cause of BSOD's. The windows 7 operating system does not require these registry cleaning software. They often tune-down rather than tune-up and can wreck the OS beyond repair. Microsoft have improved Windows 7 significantly and it is much better at organising and optimising itself than its predecessors. Check this, this and this thread for evidence.

If you feel the need to use a registry cleaning or optimisation software, most of us recommend the use of CCleaner - PC Optimization and Cleaning - Free Download but make sure you back up the registry before making letting ccleaner delete anything.

• 10 Tips on How to Properly Maintain Your Computer

Perform a System File Check to check the integrity of all protected Windows 7 :

1. Click on the start
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type
   Code:

   SFC /scannow

Full tutorial here:

• SFC /Scannow Command - System File Checker

Check your hard drive(s) for errors by running chkdsk

• Check your hard disk for errors
• Disk Check

Number down items at start-up. Keep only your anti-virus, this also improves the time for logging into windows.

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

Hope this helps for now. Keep us posted of the results and further BSOD reports if you have them :)

Analysis:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {405000000b0, 2, 0, fffff880028da633}

*** WARNING: Unable to verify timestamp for NETTDI64.SYS
*** ERROR: Module load completed but symbols could not be loaded for NETTDI64.SYS
Probably caused by : NETTDI64.SYS ( NETTDI64+3633 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000405000000b0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880028da633, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800040f7100
GetUlongFromAddress: unable to read from fffff800040f71c0
 00000405000000b0 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
NETTDI64+3633
fffff880`028da633 4839a9b0000000  cmp     qword ptr [rcx+0B0h],rbp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880061cada0 -- (.trap 0xfffff880061cada0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800af22cb0 rbx=0000000000000000 rcx=0000040500000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880028da633 rsp=fffff880061caf30 rbp=fffffa8013f474d0
 r8=fffffa8013f47480  r9=0000000000000000 r10=fffffa800da0b010
r11=fffffa800cae7b40 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
NETTDI64+0x3633:
fffff880`028da633 4839a9b0000000  cmp     qword ptr [rcx+0B0h],rbp ds:00000405`000000b0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003ebe1e9 to fffff80003ebec40

STACK_TEXT:  
fffff880`061cac58 fffff800`03ebe1e9 : 00000000`0000000a 00000405`000000b0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`061cac60 fffff800`03ebce60 : fffffa80`15e405e0 00000000`00000000 00000000`00000000 fffff880`02904f20 : nt!KiBugCheckDispatch+0x69
fffff880`061cada0 fffff880`028da633 : fffff880`061cb114 fffffa80`106d47b6 00000000`00000000 fffff880`028d98b2 : nt!KiPageFault+0x260
fffff880`061caf30 fffff880`061cb114 : fffffa80`106d47b6 00000000`00000000 fffff880`028d98b2 00000000`00000144 : NETTDI64+0x3633
fffff880`061caf38 fffffa80`106d47b6 : 00000000`00000000 fffff880`028d98b2 00000000`00000144 00000000`00000820 : 0xfffff880`061cb114
fffff880`061caf40 00000000`00000000 : fffff880`028d98b2 00000000`00000144 00000000`00000820 fffffa80`13f474d0 : 0xfffffa80`106d47b6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETTDI64+3633
fffff880`028da633 4839a9b0000000  cmp     qword ptr [rcx+0B0h],rbp

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  NETTDI64+3633

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETTDI64

IMAGE_NAME:  NETTDI64.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4abcb367

FAILURE_BUCKET_ID:  X64_0xD1_NETTDI64+3633

BUCKET_ID:  X64_0xD1_NETTDI64+3633

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

0: kd> lmvm NETTDI64
start             end                 module name
fffff880`028d7000 fffff880`02918000   NETTDI64 T (no symbols)           
    Loaded symbol image file: NETTDI64.SYS
    Image path: \??\C:\Windows\system32\Drivers\NETTDI64.SYS
    Image name: NETTDI64.SYS
    Timestamp:        Fri Sep 25 18:11:19 2009 (4ABCB367)
    CheckSum:         000341AD
    ImageSize:        00041000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

There's no attachment.

Hard to say anything from this dump. Have you performed all the steps in my other post?

Upload a screenshot of your hard disk using CrystalDiskInfo:

• CrystalDiskInfo Standard Edition
• How to Upload and Post a Screenshot and File in Seven Forums

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

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

• RAM - Test with Memtest86+

   Note

Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial:

• Memory Diagnostics Tool

HI koolkat77 ! ...

I perform all your post recommendations, thanks very much.

I still continue getting BSOD'S..I'll attach my new one MINIDUMP file, Also I attach the results test of Crystal Report performed yesterday and an SF /scan. I continue testing my HD and Memory.

We stay in touch
Thanks very much


jruiz24

Let us know the results.