BSOD Fix on German Thinkpad.de forum Please Help Understand
Posted: Sat Oct 01, 2011 2:31 am
BSOD Fix on German Thinkpad.de forum Please Help Understand
http://thinkpad-forum.de/threads/3815-B ... WORK-QUEUE...
Even when I read the translation using Google Chrome translation I am unable to understand
what was happening and what he did to fix it.
Chrome also offers several alternative translations and its still not clear.
Can anyone who understands German please help? I'd appreciate it. Thanks.
PS: Moderators if you think this would get better attention in another sub-forum such as Windows then please feel free to MOVE there
DETAILS of BSOD as posted on forum:
http://forum.thinkpads.com/viewtopic.php?f=30&t=99640
http://forum.thinkpads.com/viewtopic.php?f=30&t=99558
http://thinkpad-forum.de/threads/3815-B ... WORK-QUEUE...
Even when I read the translation using Google Chrome translation I am unable to understand
what was happening and what he did to fix it.
Chrome also offers several alternative translations and its still not clear.
Can anyone who understands German please help? I'd appreciate it. Thanks.
PS: Moderators if you think this would get better attention in another sub-forum such as Windows then please feel free to MOVE there
DETAILS of BSOD as posted on forum:
http://forum.thinkpads.com/viewtopic.php?f=30&t=99640
The whole saga started here..System Information (local)
--------------------------------------------------------------------------------
computer name: X61T-XP-TABLET
windows version: Windows XP Service Pack 2, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU L7500 @ 1.60GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2103660544 total
VM: 2147352576, free: 2047500288
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sat 10/1/2011 9:35:22 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini100111-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22EF7)
Bugcheck code: 0x96 (0xFFFFFFFF890518D0, 0xFFFFFFFF80563780, 0xFFFFFFFF80563780, 0xFFFFFFFF8057596C)
Error: INVALID_WORK_QUEUE_ITEM
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a queue entry was removed that contained a null pointer.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
http://forum.thinkpads.com/viewtopic.php?f=30&t=99558
I did not have any issues as such working 2 HDDs running Win XP & Win 7 (swapping as I needed).
Then my machine started locking/ freezing at bootup.
At first I thought it was Windows based issue so on two separate HDDs that I use where I have WinXP & Win 7x64. Both seem to freeze/lock at certain point when booting up.
I tried every thing including:
- Safemode etc.
- Bootlog mode
- Debugging mode
- DOS based PC Doctor Bootable CD
- Memtest86/+ etc.
- System Restores (on both..Win XP HDD1 and Win 7 HDD2)
- Bunch of Bootable Diagnostic tools (I am wondering if there's some kind of better Hardware Diagnosis tool than PC Doctor and/ or Thinkvantage Toolbox)
I was getting Multicore misconfigured & SMBIOS test failed like this LINK -
http://forum.notebookreview.com/lenovo- ... t61-3.html
Read all of it and I seem to have done everything but its not fixed yet.
After a night of running whole bunch .. Windows came up ONCE.
That time I ran Running ThinkVantage Toolbox (newer replacement for PC Doc)
It showed Multicore as a Misconfigured and suggested I power down and reboot fresh and run again which fixed the Misconfigure.
It showed everything as ALRIGHT! except SMBIOS.
When I looked up SMBIOS I found the PC Doctor link that says its not an issue.
http://pcpitstop.com/faq/smbios.asp
Well.. I figured this was fixed.
Worked for a day..
Next day... Same issues. Now, SMBIOS seems to have flared up again.