Tech Support Forum - View Single Post - Help with Inspiron 6400 /w int. bluetooth

You are viewing a conversation about Help with Inspiron 6400 /w int. bluetooth. To view the entire conversation, or to join in, click here: Thread: Help with Inspiron 6400 /w int. bluetooth

View Single Post
Old 03-29-2009, 02:07 AM  
jcgriff2
Administrator
Manager, Microsoft Support
Acting Manager, Security
BSOD Kernel Dump Expert
Microsoft Windows Insider MVP
 
jcgriff2's Avatar

Microsoft Most Valuable Professional
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 34,338
OS: Windows 10, 8.1 + Windbg :)



Hi Tim -

I ran the 6 mini kernel dumps. The bugchecks -

Code:

BugCheck 100000D1, {203a737d, 2, 0, ededdcea}
Probably caused by : klif.sys ( klif+7cea )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 10000050, {d2d50120, 0, 80523b30, 0}
Probably caused by : memory_corruption ( nt!MiLocateAddressInTree+4 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000000A, {5c19fb34, 2, 1, 806e4a2a}
Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireResourceExclusive+20 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 100000C5, {1b18f296, 2, 1, 8054afd2}
Probably caused by : klif.sys ( klif+c3b9 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 10000050, {b90ac859, 0, 804ed0d1, 0}
Probably caused by : ntkrpamp.exe ( nt!FsRtlLookupPerStreamContextInternal+4b )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000008E, {c0000005, 8054a51a, b80d4adc, 0}
Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+23a )

0xd1 = DRIVER_IRQL_NOT_LESS_OR_EQUAL - a kernel-mode driver tied to access paged memory at when it should not have (IRQL too high). Kaspersky is the culprit here (flagged in stack text).

2 BSODs - 0x50 = PAGE_FAULT_IN_NONPAGED_AREA - invalid system memory has been referenced. One BSOD listed the NT Kernel as probable cause; the other memory corruption - but under NT. 0x50 usually caused by faulty hardware - specifically RAM. Among other causes - video, newly installed hardware, newly installed or modified system service (like Kaspersky)

0xa = IRQL_NOT_LESS_OR_EQUAL - basically same as 0xd1, but includes Microsoft drivers in addition to kernel mode drivers. Interesting to not that p/c listed as ntfs.sys - which I usually only see with 0x24 bugcheck. Based on what I see in program instruction that failed, NTFS attempted to acquire a resource exclusively (lock it), but could not. HDD could be problem here and I suggest that you run chkdsk /r, but I think this is more related to the ntfs.sys driver itself, which I have explained below.

0x8e = KERNEL_MODE_EXCEPTION_NOT_HANDLED - a kernel mode app threw an exception not caught by error handler. The exception here is the 1st parm - 0xc0000005 = a memory access violation. NT Kernel named probable cause, but my money is once again on Kaspersky. It has the power running in kernel mode to escape detection and probably "hid" under the expansive memory address range of the NT Kernel; hence the NT Kernel left at scene of crash to take blame.

0xc5 = DRIVER_CORRUPTED_EXPOOL - basically same as 0x8e w/ 0xc0000005 exception, but in addition to memory access violation, the rogue driver corrupted the system pool. Kaspersky nailed once again in stack text.

.

Hardware failure may certainly be the problem here - and tends to be with varying bugchecks. However, from the software end, I see an old XP SP2 installation that appears not to have had Windows Updates applied in years, based on the loaded driver listing (drivers loaded into RAM at time of BSOD). The NT Kernel has timestamp = 2005; DirectX Kernel and GUI = 2004. These are from the very early days of SP2. I did take note of your comment that only SP3 is waiting for you in Windows Updates, which makes sense to me as SP3 would include the missing Windows Updates through 2008.

Microsoft NT Kernel - June 2005
MS DirectX Graphics Kernel - August 2004
MS GUI - August 2004
Code:
804d7000 806e2000   nt       ntkrpamp.exe Wed Jun 22 20:05:46 2005 (42B9FCDA)

bf9c1000 bf9d2580   dxg      dxg.sys      Wed Aug 04 02:00:51 2004 (41107B93)

bf800000 bf9c0380   win32k   win32k.sys   Wed Aug 04 02:17:30 2004 (41107F7A)
.

Your ATI video (remember the 0x50) and Bluetooth drivers are dated 2006 - newer than the NT & DX Kernels -

ATI Video - May 2006
Code:
bf9d3000 bfa16000   ati2dvag ati2dvag.dll Tue May 23 22:06:53 2006 (4473BFBD)
bfa16000 bfa5b000   ati2cqag ati2cqag.dll Tue May 23 21:25:51 2006 (4473B61F)
bfa5b000 bfa9d000   atikvmag atikvmag.dll Tue May 23 21:32:14 2006 (4473B79E)
bfa9d000 bfd3d920   ati3duag ati3duag.dll Tue May 23 21:51:27 2006 (4473BC1F)
bfd3e000 bfee9900   ativvaxx ativvaxx.dll Tue May 23 21:45:21 2006 (4473BAB1)
Bluetooth - May 2006
Code:
f65d2000 f661fd40   btaudio  btaudio.sys  Wed May 24 21:07:17 2006 (44750345)
f6775000 f6840ba0   btkrnl   btkrnl.sys   Wed May 24 21:04:02 2006 (44750282)
f785a000 f7860e40   btport   btport.sys   Wed May 24 21:01:34 2006 (447501EE)
f7802000 f78077a0   btserial btserial.sys Wed May 24 21:05:26 2006 (447502D6)
eddf2000 ede0f1a0   btwdndis btwdndis.sys Wed May 24 20:58:17 2006 (44750129)
f786a000 f7870dc0   btwmodem btwmodem.sys Wed May 24 21:01:22 2006 (447501E2)
f76c2000 f76d19e0   btwusb   btwusb.sys   Wed May 24 21:00:50 2006 (447501C2)
.

Now add high octane fuel to this fire - a completely updated KIS 2009 - by far, the newest drivers in your system -
Code:
ee1eb000 ee227000   klif     klif.sys     Thu Jan 29 07:48:43 2009 (4981A5AB)
f6cec000 f720b000   kl1      kl1.sys      Mon Jul 21 10:33:37 2008 (48849E41)
f7562000 f756d000   klbg     klbg.sys     Mon Dec 15 11:41:09 2008 (494688A5)
f7722000 f772b000   klfltdev klfltdev.sys Thu Mar 13 11:02:27 2008 (47D94203)
f77ca000 f77d2000   klim5    klim5.sys    Wed Apr 30 10:06:33 2008 (48187CE9)
.


I would suggest that you install XP SP3. It is very possible that SP3 in addition to updated drivers from Dell may end the BSODs. Take some precautions 1st. These are recommended steps to help ensure successful SP3 install and are not mandatory by any means.

1. Remove KIS 2009 using Kaspersky Removal Tool (KRT). These products tend to interfere with Service Pack installs. You can always re-install after SP3 is in. I have seen KIS, NIS, McAfee do great damage in Vista and Windows 7 systems because of the firewall, but am told OK to use in XP. You will have to be ultimate judge on this. If you re-install and encounter app crashes, app hangs or BSODs, KIS should be looked at. Be sure to reset the Windows Firewall to default settings after KIS removal.
KRT - https://support.kaspersky.com/faq/?qid=208279463
Use the KAVremover9.exe method.

2. Run the System File Checker/repair utility - SFC. You will need an XP SP2 slipstreamed CD for this.
START | Run | cmd | type sfc /scannow into the cmd/DOS screen. Re-boot upon completion to allow in-use system files to be repaired.

3. Temporary file cleaning - Use a product like CCleaner. Be careful of the boxes that you check. For example, do not check the boxes for Windows Logs or Dump files as they will be deleted.
https://www.filehippo.com/download_ccleaner/

4. Defrag HDD - Use product like Auslogics -
https://www.auslogics.com/en/software...efrag/download

Go to Windows Updates and allow SP3 to install. Re-boot upon completion. Go to Dell driver support and download any available updates. I don't know if ATI and Bluetooth came from Dell originally. If not, go to manufacturer's sites and obtain driver updates. Do the same for Ethernet and wifi (if applicable) along with audio. If BIOS update available, post back with information and let the Hardware experts here advise you on that one.

Use your Dell service tag to search support site for updates. One way to find out service tag is to run Belarc advisor - look on top-right of resulting report.
https://www.belarc.com/free_download.html

Dell driver support -
https://support.dell.com/support/down...=us&l=en&s=gen


I hope this information is helpful in solving your BSOD situation. Please post back with any questions and the results. I would appreciate knowing the outcome and do hope that you don't experience hardware failures.

A more detailed bugcheck summary is below; the full dump dbug logs are attached.

Regards. . .

jcgriff2

.

Bucgcheck Summary
Code:

Built by: 2600.xpsp.050622-1524
Debug session time: Fri Mar 27 21:33:44.046 2009 (GMT-4)
System Uptime: 0 days 0:06:26.753
BugCheck 10000050, {d2d50120, 0, 80523b30, 0}
Probably caused by : memory_corruption ( nt!MiLocateAddressInTree+4 )
PROCESS_NAME:  BTSTAC~1.EXE
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp.050622-1524
Debug session time: Fri Mar 27 15:10:31.640 2009 (GMT-4)
System Uptime: 0 days 0:04:16.356
BugCheck 1000000A, {5c19fb34, 2, 1, 806e4a2a}
Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireResourceExclusive+20 )
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp.050622-1524
Debug session time: Fri Mar 27 05:17:42.390 2009 (GMT-4)
System Uptime: 0 days 0:05:44.100
BugCheck 100000C5, {1b18f296, 2, 1, 8054afd2}
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : klif.sys ( klif+c3b9 )
PROCESS_NAME:  firefox.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp.050622-1524
Debug session time: Fri Mar 27 05:11:41.125 2009 (GMT-4)
System Uptime: 0 days 0:50:28.832
BugCheck 10000050, {b90ac859, 0, 804ed0d1, 0}
Probably caused by : ntkrpamp.exe ( nt!FsRtlLookupPerStreamContextInternal+4b )
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 2600.xpsp.050622-1524
Debug session time: Fri Mar 27 02:45:06.421 2009 (GMT-4)
System Uptime: 0 days 0:45:11.125
BugCheck 1000008E, {c0000005, 8054a51a, b80d4adc, 0}
Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+23a )
PROCESS_NAME:  CLI.exe

jcgriff2
March 29, 2009
03:59 EDT (GMT-5)
jcgriff2 is offline