New
#1
Need help with Windows 7 BSOD on Lenovo T500
My system is crashing several times a day and I need your help in figuring out why.
I have the Windows 7 RTM build installed on a Lenovo T500. The only hardware I've customized is replacing the 160 GB drive with a 320 GB drive.
The system specs are
Lenovo T500
Core 2 Duo T9600 @ 2.8 Ghz
4 GB RAM
2 GB Turbomeory
ATI Mobile Radeon 3650
Intel Wifi 5300 agn
Integrated camera, bluetooth, and WWAN
I am running the latest BIOS: 3.01-1.03.
The laptop came with Vista 32-bit, but I immediately installed Vista Ultimate 64-bit on the 320 GB drive. I had occasonal BSOD's in Vista, mostly while running on battery, and not often enough to be completely annoying (once a week or so).
Since I've installed Windows 7 Ultimate 64-bit, the BSODs are pretty regular (several times a day).
With the exception of two drivers, the only ones I've installed are from Windows 7 or Windows Update. The two I installed were from the Lenovo Windows 7 beta drivers web site to resovle the "unknonw driver" indication in the Devices control panel for a device labeled "PCI Simple Communications Controller" and another similarly named (sorry I didn't write down the exact name).
Below is the WinDBG "analyze" output from the full memory dump. All the dumps look exactly the same: "BugCheck D1, {22, 2, 8, 22}" and the stack trace is the same.
At this point, I don't know what my next steps should be to determine what the issues are. Unfortunately, if I don't figure something out, I'm going to have to go back to Vista or XP, but I don't really want to. My co-workers are losing patience watching reboots in meetings :-(. I'm a software developer for my day job, but not at this low of a level in the software stck. If necessary, I figure I could likely setup a remote kernel debugger, but I thought the memory dump was supposed to have enough to diagnose.
Thoughts, suggestions?
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [L:\200908161904-MEMORY.DMP] Kernel Summary Dump File: Only kernel address space is available Symbol search path is: L:\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`02a0a000 PsLoadedModuleList = 0xfffff800`02c47e50 Debug session time: Sun Aug 16 19:02:43.499 2009 (GMT-5) System Uptime: 0 days 9:17:20.760 Loading Kernel Symbols ............................................................... ................................................................ ................................................. Loading User Symbols Loading unloaded module list ........................ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {22, 2, 8, 22} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) Followup: MachineOwner --------- 1: 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: 0000000000000022, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000008, value 0 = read operation, 1 = write operation Arg4: 0000000000000022, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: 0000000000000022 CURRENT_IRQL: 2 FAULTING_IP: +0 00000000`00000022 ?? ??? PROCESS_NAME: System DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 TRAP_FRAME: fffff88002f1bb10 -- (.trap 0xfffff88002f1bb10) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000050 rbx=0000000000000000 rcx=fffffa8000000001 rdx=fffffa8000000000 rsi=0000000000000000 rdi=0000000000000000 rip=0000000000000022 rsp=fffff88002f1bca0 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=fffff88002f1b9e0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up di pl zr na po nc 00000000`00000022 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a7b469 to fffff80002a7bf00 FAILED_INSTRUCTION_ADDRESS: +0 00000000`00000022 ?? ??? STACK_TEXT: fffff880`02f1b9c8 fffff800`02a7b469 : 00000000`0000000a 00000000`00000022 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx fffff880`02f1b9d0 fffff800`02a7a0e0 : 00000015`b91da5c9 fffffa80`00000002 00000015`b91da5c9 00000abc`b91d9b22 : nt!KiBugCheckDispatch+0x69 fffff880`02f1bb10 00000000`00000022 : 00000000`00000000 00000000`00000000 fffffa80`07684ae0 00000000`00000000 : nt!KiPageFault+0x260 fffff880`02f1bca0 00000000`00000000 : 00000000`00000000 fffffa80`07684ae0 00000000`00000000 fffffa80`07684cf8 : 0x22 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiPageFault+260 fffff800`02a7a0e0 440f20c0 mov rax,cr8 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiPageFault+260 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260 BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260 Followup: MachineOwner ---------
Last edited by dlcrow; 17 Aug 2009 at 11:59. Reason: Added bios level.