1 week old laptop that crashed.

I just started up my Lenovo T400 last Saturday. I do not game or download music or movies. I've had this laptop for a week and during chatting, a noise started coming out from the computer with a blue screen. I manually turned off the computer and when restarting, I could not load properly. Currently in Safe Mode w/ Networking, I tried to System Restore but there was an error as well.

Computer Specs:
CORE 2 DUO PROCESSOR P8800
WIN 7 HM PR 64 US EN
3GB PC3-8500 1067MHZ 2DIMM
250GB HDD/5400RPM
INT.TURBOMEMORY1.6 2GB

berkana said:

I just started up my Lenovo T400 last Saturday. I do not game or download music or movies. I've had this laptop for a week and during chatting, a noise started coming out from the computer with a blue screen. I manually turned off the computer and when restarting, I could not load properly. Currently in Safe Mode w/ Networking, I tried to System Restore but there was an error as well.

Computer Specs:
CORE 2 DUO PROCESSOR P8800
WIN 7 HM PR 64 US EN
3GB PC3-8500 1067MHZ 2DIMM
250GB HDD/5400RPM
INT.TURBOMEMORY1.6 2GB

Hello Welcome to SF,

I guess the problem is with igdkmd64.sys i.e. your Intel Display driver. I would recommend to remove your Drvier completely and reinstall the driver from Vendors wensite and NOT from Windows update. Check whether you have any BIOS updates. Ensure that the machine is adequately cooled.

There are two devices or Program that has caused problems

1. Security Processor Loader Driver
2. Symantec Network Dispatch Driver

I would recommend to Update the Security Processor Loader Driver.
Go To Start > Device Manager > There you can find Yellow mark right click on it and click on Update Driver

Regarding the Symantec i would recommend you to uninstall the complete Symantec pack (If Norton included that as well) follow this link to download the Removal Tool.

Hardware Diagnostic

Run the Memory Diagnostic & HD Diagnostic

Also i would recommend to run System Integrity Checker
Start > Run > CMD >Right Click and Run as administrator > SFC/ SCANNOW

Update these drivers

Code:

Tppwr64v.sys Wed Oct 18 14:10:21 2006
smiifx64.sys Mon May 12 14:31:13 2008
mdmxsdk.sys  Tue Jun 20 02:57:26 2006
e1y60x64.sys Tue Aug 19 03:15:05 2008

Bugcheck Analysis

Code:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000094, The exception code that was not handled
Arg2: fffff880043a0de9, The address that the exception occurred at
Arg3: fffff880031c6ff8, Exception Record Address
Arg4: fffff880031c6850, Context Record Address
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.
FAULTING_IP: 
igdkmd64+2f0de9
fffff880`043a0de9 f77c2428        idiv    eax,dword ptr [rsp+28h]
EXCEPTION_RECORD:  fffff880031c6ff8 -- (.exr 0xfffff880031c6ff8)
Cannot read Exception record @ fffff880031c6ff8
CONTEXT:  fffff880031c6850 -- (.cxr 0xfffff880031c6850)
rax=0000000000000000 rbx=fffffa800235aa20 rcx=0000000000000001
rdx=0000000000000000 rsi=fffffa80023a0b60 rdi=000000000002ccd8
rip=fffff880043a0de9 rsp=fffff880031c7230 rbp=fffff80002c235f8
 r8=0000000000000000  r9=0000000000000004 r10=fffffffffffffffe
r11=fffff880031c7200 r12=fffffa80030481a0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
igdkmd64+0x2f0de9:
fffff880`043a0de9 f77c2428        idiv    eax,dword ptr [rsp+28h] ss:fffff880`031c7258=00000000
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
CURRENT_IRQL:  0
ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.
LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880043a0de9
STACK_TEXT:  
fffff880`031c7230 00000000`00000000 : 00000000`00000297 fffff880`031c7250 fffff880`043a2bed fffffa80`07c21000 : igdkmd64+0x2f0de9

FOLLOWUP_IP: 
igdkmd64+2f0de9
fffff880`043a0de9 f77c2428        idiv    eax,dword ptr [rsp+28h]
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  igdkmd64+2f0de9
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: igdkmd64
IMAGE_NAME:  igdkmd64.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a6f7d42
STACK_COMMAND:  .cxr 0xfffff880031c6850 ; kb
FAILURE_BUCKET_ID:  X64_0x7E_igdkmd64+2f0de9
BUCKET_ID:  X64_0x7E_igdkmd64+2f0de9

Hope this helps,
Captain