BSODs are driving me crazy

Status
Not open for further replies.
Hi,

I have a Lenovo z610 laptop, have been getting random and infrequent BSODs for a while now, which although annoying, I could just about deal with.

Recently however I have been getting them a lot more, some days it wont do it, others, like today, I will get them every 20 mins or so... I am running CAD software, but it reboots itself even if I have no programs running.

The error signature when I get back into windows is now constantly:
BCCode : 1000007f BCP1 : 0000000D BCP2 : 00000000 BCP3 : 00000000
BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

I really dont know what I am doing, but I have put the minidumps into the debugger and get this (or something similar) out.


Loading Dump File [C:\WINDOWS\Minidump\Mini071108-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri Jul 11 13:17:56.859 2008 (GMT+1)
System Uptime: 0 days 0:20:47.683
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.................................................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..........................
Unable to load image ati2mtag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati2mtag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {d, 0, 0, 0}

Probably caused by : ntoskrnl.exe ( nt!vDbgPrintExWithPrefix+11c )

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

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

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x7f_d

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

PROCESS_NAME: pifCrawl.exe

LAST_CONTROL_TRANSFER: from b884a34c to b87d5540

STACK_TEXT:
978d4d94 b884a34c 8003f400 b884a585 10011f22 ati2mtag!_NULL_IMPORT_DESCRIPTOR <PERF> (ati2mtag+0x102540)
978d4d9c b884a585 10011f22 10011f26 1000f001 ati2mtag!_NULL_IMPORT_DESCRIPTOR <PERF> (ati2mtag+0x17734c)
978d4da0 10011f22 10011f26 1000f001 978d4dc4 ati2mtag!_NULL_IMPORT_DESCRIPTOR <PERF> (ati2mtag+0x177585)
WARNING: Frame IP not in any known module. Following frames may be wrong.
978d4da4 10011f26 1000f001 978d4dc4 8050589b 0x10011f22
978d4da8 1000f001 978d4dc4 8050589b 73c742fa 0x10011f26
978d4dac 978d4dc4 8050589b 73c742fa 0000000e 0x1000f001
978d4db0 8050589b 73c742fa 0000000e 00a9ea37 0x978d4dc4
978d4dc4 00000000 00a9ea37 0000001b 00000306 nt!vDbgPrintExWithPrefix+0x11c


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!vDbgPrintExWithPrefix+11c
8050589b ?? ???

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: nt!vDbgPrintExWithPrefix+11c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e5484a

FAILURE_BUCKET_ID: 0x7f_d_nt!vDbgPrintExWithPrefix+11c

BUCKET_ID: 0x7f_d_nt!vDbgPrintExWithPrefix+11c

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

I have tried deleting and reinstalling the ati driver, as well as rolling it back... but the BSODs are still happening. I have got Lenovo System Update installed on the laptop, so I do have all of the latest/recommended drivers for this laptop

I would really appreciate it if someone could give me a hand as I have got no idea what to do!!!!

Thanks
 
Norton AntiVirus (all versions, but you have 2008) has usually been the biggest issue in these types of faults.

Members may ask you to try different drivers, and confirm all security updates are done, also run full Antivirus and Spyware scans.

But in my opinion it's Norton (again!)
 
Thanks kimsland...

Would you suggest I just get rid of Norton and put something else like AVG or Avast or something??? Or just try and turn off some of the features of Norton???
 
My personal opinion, remove Norton and live update.
And use Avast (I don't like how Avira does popups)
Once Avast is fully installed and updated, do a full scan.

AVG free version 8 comes with Spyware protection too (that's good)
But due to this, it can make systems run a little slow (that's bad) but not as slow as Norton slows a system down.

Edit:

I now prefer Avira
 
In addition, I looked up this file> pifCrawl.exe: From Symantec Tech Support: "please note that this is related to Symantec program. This is will be trying to access your Internet in order to search for updates, it is not any kind of virus file. And also you need not to allow the 'pifCrawl.exe' files, you can block the file."

http://www.castlecops.com/t211929-Is_pifCrawl_exe_a_genuine_Symantec_file.html

However, the suggestion to block it seems at cross-purpose to what it does.
 
Status
Not open for further replies.
Back