BSOD new machine

toozie

New member
Local time
7:12 AM
Messages
3
I have received several different BSOD on my new win 7. They seemed to start after installing some of the software, but I reset to earlier date and though it was fixed but as still getting them some.
I have Win7 pro x64 new Dell Latitude E6510 - new in Nov but not really even used until now. Ordered with Win 7 pro, but added security software and Office after received. Accidently loaded Cisco VPN client 4.8 when moving files from old system. Tried to unstall, but can not finish it succesusfully, seem to have pieces hanging out there, not sure if it is causing the BSOD or not. Tried to load ESET security software but every install attempt led to BSOD, contacted their help and tried various things, but then gave up and now have Kaspersky loaded with no problems that I know of. However, still occasional BSOD. Please Help
attached are reports
 

My Computer

Computer Manufacturer/Model Number
Dell Latitude E6510
OS
Windows 7 pro x64
CPU
Intel i5-520M Dual Core
Memory
8 GB DDR3-1333 SDRAM, 2 Dimm
Graphics Card(s)
512mb Nvida NVS 3100M
Sound Card
IDT Audio
Monitor(s) Displays
15.6 HD anti Glare for Latitude 6510 - Generic PnP Monitor
Hard Drives
250G 9.5MM, 7200rpm drive for Latitude
I have received several different BSOD on my new win 7. They seemed to start after installing some of the software, but I reset to earlier date and though it was fixed but as still getting them some.
I have Win7 pro x64 new Dell Latitude E6510 - new in Nov but not really even used until now. Ordered with Win 7 pro, but added security software and Office after received. Accidently loaded Cisco VPN client 4.8 when moving files from old system. Tried to unstall, but can not finish it succesusfully, seem to have pieces hanging out there, not sure if it is causing the BSOD or not. Tried to load ESET security software but every install attempt led to BSOD, contacted their help and tried various things, but then gave up and now have Kaspersky loaded with no problems that I know of. However, still occasional BSOD. Please Help
attached are reports

DNE driver remove it (dne64.sys)

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

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
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
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e8ee50
Debug session time: Fri Jan 28 18:21:39.795 2011 (GMT-5)
System Uptime: 0 days 7:58:08.371
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80069fae30, fffff80000b9c518, fffffa800cde9510}

*** WARNING: Unable to verify timestamp for dne64x.sys
*** ERROR: Module load completed but symbols could not be loaded for dne64x.sys
Probably caused by : dne64x.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80069fae30, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa800cde9510, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa800cde9510

DEVICE_OBJECT: fffffa800a86c050

DRIVER_OBJECT: fffffa800a181e70

IMAGE_NAME:  dne64x.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  42c35c9e

MODULE_NAME: dne64x

FAULTING_MODULE: fffff880041d3000 dne64x

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d30273 to fffff80002cc1740

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02d30273 : 00000000`0000009f 00000000`00000003 fffffa80`069fae30 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02ccd29e : fffff800`00b9c600 fffff800`00b9c600 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`00b9c570 fffff800`02cccdd6 : fffff880`05e4fad0 fffff880`05e4fad0 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02ccd4be : 00000042`cb9a2563 fffff800`00b9cc58 00000000`001c0f8a fffff800`02e3f3c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02ccccb7 : 0000000f`9dd73ec3 0000000f`001c0f8a 0000000f`9dd73e9c 00000000`0000008a : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02cc9eea : fffff800`02e3be80 fffff800`02e49c40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_dne64x.sys

BUCKET_ID:  X64_0x9F_IMAGE_dne64x.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80069fae30, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa800cde9510, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa800cde9510

DEVICE_OBJECT: fffffa800a86c050

DRIVER_OBJECT: fffffa800a181e70

IMAGE_NAME:  dne64x.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  42c35c9e

MODULE_NAME: dne64x

FAULTING_MODULE: fffff880041d3000 dne64x

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d30273 to fffff80002cc1740

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02d30273 : 00000000`0000009f 00000000`00000003 fffffa80`069fae30 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02ccd29e : fffff800`00b9c600 fffff800`00b9c600 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`00b9c570 fffff800`02cccdd6 : fffff880`05e4fad0 fffff880`05e4fad0 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02ccd4be : 00000042`cb9a2563 fffff800`00b9cc58 00000000`001c0f8a fffff800`02e3f3c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02ccccb7 : 0000000f`9dd73ec3 0000000f`001c0f8a 0000000f`9dd73e9c 00000000`0000008a : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02cc9eea : fffff800`02e3be80 fffff800`02e49c40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_dne64x.sys

BUCKET_ID:  X64_0x9F_IMAGE_dne64x.sys

Followup: MachineOwner
---------
Also old drivers from as far back as 2005

Code:
dne64x.sys    6/29/2005 21:44:46    0x42c35c9e    fffff880`03000000    fffff880`03026000        0x00026000                    
mdmxsdk.sys    6/19/2006 16:27:26    0x449716be    fffff880`03e9e000    fffff880`03ea2280        0x00004280                    
PBADRV.sys    1/7/2008 14:12:13    0x4782798d    fffff880`0169b000    fffff880`016a7000        0x0000c000                    
CAX_CNXT.sys    2/13/2009 16:19:32    0x4995e3e4    fffff880`07ee8000    fffff880`07fb3000        0x000cb000                    
CAXHWAZL.sys    2/13/2009 16:20:54    0x4995e436    fffff880`07b60000    fffff880`07bb2000        0x00052000                    
CAX_DPV.sys    2/13/2009 16:24:50    0x4995e522    fffff880`07c30000    fffff880`07da4000        0x00174000                    
XAudio64.sys    4/29/2009 13:21:07    0x49f89a93    fffff880`0953e000    fffff880`09546000        0x00008000                    
spldr.sys    5/11/2009 11:56:27    0x4a0858bb    fffff880`01693000    fffff880`0169b000        0x00008000                    
amdxata.sys    5/19/2009 12:56:59    0x4a12f2eb    fffff880`01221000    fffff880`0122c000        0x0000b000                    
esihdrv.sys    7/7/2009 6:40:49    0x4a533441    fffff880`099da000    fffff880`099fd000        0x00023000
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 Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
 

My Computer

Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
tried uninstalling - more BSOD

I went to the site for the dne driver and tried to remove it with their instructions and I get more blue screens or it won't even come up in Normal mode. I disabled the Cisco VPN in startup servies hoping to help, but I still get BSOD. Sometimes after it has been sitting a while, sometimes on shutdown.
I ran more reports on the latest BSOD and they are attached. I am scared to use this new laptop much until this is resolved.
 

My Computer

Computer Manufacturer/Model Number
Dell Latitude E6510
OS
Windows 7 pro x64
CPU
Intel i5-520M Dual Core
Memory
8 GB DDR3-1333 SDRAM, 2 Dimm
Graphics Card(s)
512mb Nvida NVS 3100M
Sound Card
IDT Audio
Monitor(s) Displays
15.6 HD anti Glare for Latitude 6510 - Generic PnP Monitor
Hard Drives
250G 9.5MM, 7200rpm drive for Latitude
Back
Top