BlueScreen Error..............again

mitan14 · 11 Oct 2010

I had had a couple of crashes now with my HP dv3 laptop (which is only a month old)

All of a sudden my machine freezes for a few seconds and then restarts and i would like to know what the cause is and possible solutions.

I think 2 things may have contributed to (but maybe not caused) the problem:
(1) HP's bluetooth adapter wizard
(2) The free 60 days version of Nortons Antivirus given

I am using Windows 7 home (premium?) x64 which came pre-installed.

Here is the error message:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF8800B898BA1
BCP3: FFFFF8800A5929D8
BCP4: FFFFF8800A592240
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\101010-34710-01.dmp
C:\Users\Mitan\AppData\Local\Temp\WER-46644-0.sysdata.xml

I have attached the BSOD dump folder and PERFMON file both in one .zip file for more details.

ANY HELP would be greatly appreciated because I really hope that it isn't a faulty laptop with it being bought recently.

Thanks

zigzag3143 · 11 Oct 2010

mitan14 said:

I had had a couple of crashes now with my HP dv3 laptop (which is only a month old)

All of a sudden my machine freezes for a few seconds and then restarts and i would like to know what the cause is and possible solutions.

I think 2 things may have contributed to (but maybe not caused) the problem:
(1) HP's bluetooth adapter wizard
(2) The free 60 days version of Nortons Antivirus given

I am using Windows 7 home (premium?) x64 which came pre-installed.

Here is the error message:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF8800B898BA1
BCP3: FFFFF8800A5929D8
BCP4: FFFFF8800A592240
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\101010-34710-01.dmp
C:\Users\Mitan\AppData\Local\Temp\WER-46644-0.sysdata.xml

I have attached the BSOD dump folder and PERFMON file both in one .zip file for more details.

ANY HELP would be greatly appreciated because I really hope that it isn't a faulty laptop with it being bought recently.

Thanks

You have several things that could be causing these crashes.

1-SPTD.sys
2-old drivers
3-corrupt L6B3764.sys

1- SPTD?SYS
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
[/quote]
You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

2-old drivers
How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Code:

L6KB3764.sys        fffff880`0d0eb000    fffff880`0d1b5d00    0x000cad00    0x4963e541    1/6/2009 19:12:01                        
btwl2cap.sys        fffff880`0b6a9000    fffff880`0b6b5000    0x0000c000    0x49d6a9bd    4/3/2009 20:28:45                        
spldr.sys        fffff880`01bce000    fffff880`01bd6000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
amdxata.sys        fffff880`01497000    fffff880`014a2000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
Accelerometer.sys        fffff880`05487000    fffff880`05493000    0x0000c000    0x4a54e862    7/8/2009 14:41:38                        
hpdskflt.sys        fffff880`01bf1000    fffff880`01bfb000    0x0000a000    0x4a54e862    7/8/2009 14:41:38

3-corruption

run a system file check

SFC /SCANNOW Command - System File Checker

Let us know the results

Ken

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\Windows_NT6_BSOD_jcgriff2\101010-34710-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols/;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c4e000 PsLoadedModuleList = 0xfffff800`02e8be50
Debug session time: Sun Oct 10 15:45:19.674 2010 (GMT-4)
System Uptime: 0 days 9:22:19.652
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
............
Unable to load image \SystemRoot\System32\Drivers\L6KB3764.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for L6KB3764.sys
*** ERROR: Module load completed but symbols could not be loaded for L6KB3764.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800b898ba1, fffff8800a5929d8, fffff8800a592240}

Probably caused by : L6KB3764.sys ( L6KB3764+19ba1 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800b898ba1, The address that the exception occurred at
Arg3: fffff8800a5929d8, Exception Record Address
Arg4: fffff8800a592240, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
L6KB3764+19ba1
fffff880`0b898ba1 66814b0a0020    or      word ptr [rbx+0Ah],2000h

EXCEPTION_RECORD:  fffff8800a5929d8 -- (.exr 0xfffff8800a5929d8)
ExceptionAddress: fffff8800b898ba1 (L6KB3764+0x0000000000019ba1)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 000000000000000a
Attempt to write to address 000000000000000a

CONTEXT:  fffff8800a592240 -- (.cxr 0xfffff8800a592240)
rax=fffffa800ab27010 rbx=0000000000000000 rcx=fffffa800aef63a8
rdx=0000000000000000 rsi=fffffa800ab27010 rdi=fffffa800aef60b8
rip=fffff8800b898ba1 rsp=fffff8800a592c10 rbp=fffff8800d726e24
 r8=fffffa8004cfac00  r9=0000000000000000 r10=05f90558061c0555
r11=0000000000000000 r12=fffffa8004a28c10 r13=fffffa80097691f0
r14=0000000000000000 r15=fffff80000b96080
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
L6KB3764+0x19ba1:
fffff880`0b898ba1 66814b0a0020    or      word ptr [rbx+0Ah],2000h ds:002b:00000000`0000000a=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  000000000000000a

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef60e0
 000000000000000a 

FOLLOWUP_IP: 
L6KB3764+19ba1
fffff880`0b898ba1 66814b0a0020    or      word ptr [rbx+0Ah],2000h

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffffa80085e99b0 to fffff8800b898ba1

STACK_TEXT:  
fffff880`0a592c10 fffffa80`085e99b0 : fffff880`0d726e24 fffffa80`0467d610 fffffa80`0aef60b8 fffff880`0a592c40 : L6KB3764+0x19ba1
fffff880`0a592c18 fffff880`0d726e24 : fffffa80`0467d610 fffffa80`0aef60b8 fffff880`0a592c40 fffffa80`08546660 : 0xfffffa80`085e99b0
fffff880`0a592c20 fffffa80`0467d610 : fffffa80`0aef60b8 fffff880`0a592c40 fffffa80`08546660 fffffa80`000001b9 : 0xfffff880`0d726e24
fffff880`0a592c28 fffffa80`0aef60b8 : fffff880`0a592c40 fffffa80`08546660 fffffa80`000001b9 00000000`00000000 : 0xfffffa80`0467d610
fffff880`0a592c30 fffff880`0a592c40 : fffffa80`08546660 fffffa80`000001b9 00000000`00000000 00000000`00000000 : 0xfffffa80`0aef60b8
fffff880`0a592c38 fffffa80`08546660 : fffffa80`000001b9 00000000`00000000 00000000`00000000 fffff800`02cc7cff : 0xfffff880`0a592c40
fffff880`0a592c40 fffffa80`000001b9 : 00000000`00000000 00000000`00000000 fffff800`02cc7cff fffff800`00b96080 : 0xfffffa80`08546660
fffff880`0a592c48 00000000`00000000 : 00000000`00000000 fffff800`02cc7cff fffff800`00b96080 00000000`00000000 : 0xfffffa80`000001b9


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  L6KB3764+19ba1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: L6KB3764

IMAGE_NAME:  L6KB3764.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4963e541

STACK_COMMAND:  .cxr 0xfffff8800a592240 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_L6KB3764+19ba1

BUCKET_ID:  X64_0x7E_L6KB3764+19ba1

Followup: MachineOwner
---------

mitan14 · 12 Oct 2010

Thank you so much for your help Ken.

1) I have removed Daemon tools and ran the SPTD uninstaller.

2) The drivers are routinely checked by HP Support Assistant (which runs automatically on my machine) and software updates occur every few weeks through this.

3) I also ran the SFC and you'll the resulting text file attached. It doesn't seem to show up with any issues but if, as you say, I have a corrupt L6B3764.sys, how can it be fixed? (additionally what is it's function?)

Kind Regards

Mit