Hi
Yesterday, I was having about 5+ BSODs so I decided to reimage W7 from an existing W7 image. However, when I was asleep last night, 3 BSODs occured. I ran the W7 Mem Diagnostics without any problems. I have a Lenovo T61 with NVS 140m. Is this a hardware or software problem? Thanks in advance
CHKDSK shows no errors.
Does this have to do with it?
NVIDIA DISASTER: thousands of GPUs faulty
Hi and welcome
I have a feeling that you problem stem from both the old drivers, and some damaged OS files.
Microsoft recommended clean installs and that wold have helped here but.
I would update all the drivers and run a system file check to verify and repair your system files
To do that type cmd in search>right click and run as admin>sfc /scannow
Let us know if you need help
Ken
OLD DRIVERS THAT NEED UPDATING
Code:
mdmxsdk.sys fffff880`08232000 fffff880`08236280 0x00004280 0x449716be 6/19/2006 4:27:26 PM
secdrv.SYS fffff880`0a341000 fffff880`0a34c000 0x0000b000 0x4508052e 9/13/2006 8:18:38 AM
Tppwr64v.sys fffff880`03ff7000 fffff880`03ffd000 0x00006000 0x4535e875 10/18/2006 3:40:21 AM
xaudio64.sys fffff880`0a3a1000 fffff880`0a3a9000 0x00008000 0x456cd810 11/28/2006 7:45:04 PM
CAX_CNXT.sys fffff880`07a31000 fffff880`07af9000 0x000c8000 0x458c403a 12/22/2006 3:29:46 PM
CAXHWAZL.sys fffff880`06182000 fffff880`061d6000 0x00054000 0x458c4077 12/22/2006 3:30:47 PM
CAX_DPV.sys fffff880`07836000 fffff880`079b0000 0x0017a000 0x458c4114 12/22/2006 3:33:24 PM
PxHlpa64.sys fffff880`01287000 fffff880`01292380 0x0000b380 0x45c3ac06 2/2/2007 4:24:22 PM
psadd.sys fffff880`05d46000 fffff880`05d51000 0x0000b000 0x45d9f2e5 2/19/2007 1:56:37 PM
lmimirr.sys fffff880`05c69000 fffff880`05c70000 0x00007000 0x461c108d 4/10/2007 5:32:45 PM
rimspx64.sys fffff880`05635000 fffff880`0564c000 0x00017000 0x46a886a0 7/26/2007 6:33:52 AM
rixdpx64.sys fffff880`053a7000 fffff880`053fe000 0x00057000 0x46a9ccde 7/27/2007 5:45:50 AM
SscRdCls.sys fffff880`00d9c000 fffff880`00daa000 0x0000e000 0x473df68d 11/16/2007 2:59:09 PM
RaInfo.sys fffff880`08218000 fffff880`0821f000 0x00007000 0x477e818a 1/4/2008 1:57:14 PM
rimmpx64.sys fffff880`05620000 fffff880`05635000 0x00015000 0x47bcd2c3 2/20/2008 8:24:19 PM
smiifx64.sys fffff880`04119000 fffff880`04120000 0x00007000 0x48280759 5/12/2008 4:01:13 AM
adfs.SYS fffff880`08200000 fffff880`08218000 0x00018000 0x48640195 6/26/2008 3:52:37 PM
LMIRfsDriver.sys fffff880`0821f000 fffff880`08232000 0x00013000 0x487b7e50 7/14/2008 11:26:56 AM
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\New folder (3)\031210-16879-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c46e50
Debug session time: Fri Mar 12 01:21:48.446 2010 (GMT-5)
System Uptime: 0 days 1:20:37.506
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
.....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, fffffa800130fd80, fffffa80013107d0, 4a56510}
GetPointerFromAddress: unable to read from fffff80002cb10e0
GetUlongFromAddress: unable to read from fffff80002c1f1b0
Probably caused by : ntkrnlmp.exe ( nt!CcWriteBehind+5bc )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa800130fd80, The pool entry we were looking for within the page.
Arg3: fffffa80013107d0, The next pool entry.
Arg4: 0000000004a56510, (reserved)
Debugging Details:
------------------
GetUlongFromAddress: unable to read from fffff80002c1f1b0
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: fffffa800130fd80
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002bac6d3 to fffff80002a7af00
STACK_TEXT:
fffff880`0c812a98 fffff800`02bac6d3 : 00000000`00000019 00000000`00000020 fffffa80`0130fd80 fffffa80`013107d0 : nt!KeBugCheckEx
fffff880`0c812aa0 fffff800`02a6e55c : fffff800`02cb3800 00000000`00000000 fffffa80`63536343 fffff800`00000000 : nt!ExFreePool+0xda4
fffff880`0c812b50 fffff800`02a6ed60 : fffff880`041bcd00 fffff880`0c812c58 00000000`00000000 fffff880`00000000 : nt!CcWriteBehind+0x5bc
fffff880`0c812c00 fffff800`02a88161 : fffffa80`03c38930 fffff800`02d74504 fffff800`02c80140 fffffa80`00000002 : nt!CcWorkerThread+0x1c8
fffff880`0c812cb0 fffff800`02d1e166 : fffff880`0bbe9400 fffffa80`08998880 00000000`00000080 fffffa80`03babb30 : nt!ExpWorkerThread+0x111
fffff880`0c812d40 fffff800`02a59486 : fffff880`009ea180 fffffa80`08998880 fffffa80`061b7b60 fffff880`01424bf0 : nt!PspSystemThreadStartup+0x5a
fffff880`0c812d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!CcWriteBehind+5bc
fffff800`02a6e55c 4c8b9c24b8000000 mov r11,qword ptr [rsp+0B8h]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!CcWriteBehind+5bc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x19_20_nt!CcWriteBehind+5bc
BUCKET_ID: X64_0x19_20_nt!CcWriteBehind+5bc
Followup: MachineOwner
---------