Solved BSOD on new HP DV8t-1200

[0pTicaL]

I've had my fair share of problems after receiving and reformating this new laptop with my own copy of win7 x64 ultimate. Everything is up and working except the touch sensitive eject button.

Now the fun part, I've gotten 2 BSODs and from looking at the reports from WinDBG, both BSODs seem to target a different problem but other than that I cannot figure out exactly what the problem is. Problem with RAM? Drivers? hardware?

I would appreciate any help or opinions anyone can provide. Using:

1) Formatted OEM (Home Premium) and installed Win7 x64 (latest updates)

2) Installed all necessary drivers from hp support site except I did not use hp's nvidia drivers, downloaded nvidia drivers directly from nvidia.com

HP dv8t-1200

Intel i5 450M

6GB (3GBx2) 1066MHz

nVidia GT 230M

HDD 640GB (320GBx2)

The 1st BSOD happened when I was viewing a 1hr 30min 1080p video on youtube.

The 2nd BSOD happened when I launched a second WinDBG window to load the 2nd crash dump.

 

[zigzag3143]

I've had my fair share of problems after receiving and reformating this new laptop with my own copy of win7 x64 ultimate. Everything is up and working except the touch sensitive eject button.

Now the fun part, I've gotten 2 BSODs and from looking at the reports from WinDBG, both BSODs seem to target a different problem but other than that I cannot figure out exactly what the problem is. Problem with RAM? Drivers? hardware?

I would appreciate any help or opinions anyone can provide. Using:

1) Formatted OEM (Home Premium) and installed Win7 x64 (latest updates)

2) Installed all necessary drivers from hp support site except I did not use hp's nvidia drivers, downloaded nvidia drivers directly from nvidia.com

HP dv8t-1200

Intel i5 450M

6GB (3GBx2) 1066MHz

nVidia GT 230M

HDD 640GB (320GBx2)

The 1st BSOD happened when I was viewing a 1hr 30min 1080p video on youtube.

The 2nd BSOD happened when I launched a second WinDBG window to load the 2nd crash dump.

Several problems


First remove 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


Second update drivers

vpcnfltr.sys        fffff880`01df9000    0x00015000    0x49e5755d    4/15/2009 01:49:17            fffff880`01de4000                
[COLOR=Red]vpchbus.sys        fffff880`066b8000    0x0003c000    0x49e57560    4/15/2009 01:49:20            fffff880`0667c000 [/COLOR]               
[COLOR=Red]vpcusb.sys        fffff880`01637000    0x0001d000    0x49e57560    4/15/2009 01:49:20            fffff880`0161a000      [/COLOR]          
vpcvmm.sys        fffff880`044b5f00    0x00056f00    0x49e57562    4/15/2009 01:49:22            fffff880`0445f000                
spldr.sys        fffff880`01f79000    0x00008000    0x4a0858bb    5/11/2009 12:56:27            fffff880`01f71000                
amdxata.sys        fffff880`0121b000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59            fffff880`01210000                
[COLOR=Red]nvraid.sys        fffff880`00e9f000    0x00029000    0x4a13a5ac    5/20/2009 02:39:40            fffff880`00e76000  [/COLOR]              
enecir.sys        fffff880`04448000    0x0001d000    0x4a48243a    6/28/2009 22:17:30            fffff880`0442b000                
Accelerometer.sys        fffff880`0659d000    0x0000c000    0x4a54e862    7/8/2009 14:41:38            fffff880`06591000                
hpdskflt.sys        fffff880`01d68000    0x0000a000    0x4a54e862    7/8/2009 14:41:38            fffff880`01d5e000

Third and most important re-install your NETw5s64.sys Intel networking driver for it caused these two crashes

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\110210-33103-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
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03007000 PsLoadedModuleList = 0xfffff800`03244e50
Debug session time: Tue Nov  2 18:32:00.416 2010 (GMT-4)
System Uptime: 0 days 13:16:33.086
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
..............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 1097, 4210010, fffffa800aa55730}

Unable to load image \SystemRoot\system32\drivers\ndis.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
GetPointerFromAddress: unable to read from fffff800032af0e0
Probably caused by : NETw5s64.sys ( NETw5s64+15f02 )

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

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

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001097, (reserved)
Arg3: 0000000004210010, Memory contents of the pool block
Arg4: fffffa800aa55730, Address of the block of pool being deallocated

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


POOL_ADDRESS:  fffffa800aa55730 

FREED_POOL_TAG:  W3Rx

BUGCHECK_STR:  0xc2_7_W3Rx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800031aa60e to fffff80003077740

STACK_TEXT:  
fffff880`0b07def8 fffff800`031aa60e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`04210010 : nt!KeBugCheckEx
fffff880`0b07df00 fffff880`0184cad2 : fffffa80`0b7acfb0 fffff880`05c29f02 00000000`00000100 fffffa80`0aa55750 : nt!ExDeferredFreePool+0x11eb
fffff880`0b07dfb0 fffffa80`0b7acfb0 : fffff880`05c29f02 00000000`00000100 fffffa80`0aa55750 fffffa80`0b45a138 : ndis+0x1ad2
fffff880`0b07dfb8 fffff880`05c29f02 : 00000000`00000100 fffffa80`0aa55750 fffffa80`0b45a138 fffff880`05e0ceb5 : 0xfffffa80`0b7acfb0
fffff880`0b07dfc0 00000000`00000100 : fffffa80`0aa55750 fffffa80`0b45a138 fffff880`05e0ceb5 fffff880`05e0cdf0 : NETw5s64+0x15f02
fffff880`0b07dfc8 fffffa80`0aa55750 : fffffa80`0b45a138 fffff880`05e0ceb5 fffff880`05e0cdf0 fffffa80`077ee100 : 0x100
fffff880`0b07dfd0 fffffa80`0b45a138 : fffff880`05e0ceb5 fffff880`05e0cdf0 fffffa80`077ee100 fffffa80`0b7acfe0 : 0xfffffa80`0aa55750
fffff880`0b07dfd8 fffff880`05e0ceb5 : fffff880`05e0cdf0 fffffa80`077ee100 fffffa80`0b7acfe0 fffff880`05c29f02 : 0xfffffa80`0b45a138
fffff880`0b07dfe0 fffff880`05e0cdf0 : fffffa80`077ee100 fffffa80`0b7acfe0 fffff880`05c29f02 00000000`00000000 : NETw5s64+0x1f8eb5
fffff880`0b07dfe8 fffffa80`077ee100 : fffffa80`0b7acfe0 fffff880`05c29f02 00000000`00000000 fffffa80`0a05a0e0 : NETw5s64+0x1f8df0
fffff880`0b07dff0 fffffa80`0b7acfe0 : fffff880`05c29f02 00000000`00000000 fffffa80`0a05a0e0 fffffa80`077ee100 : 0xfffffa80`077ee100
fffff880`0b07dff8 fffff880`05c29f02 : 00000000`00000000 fffffa80`0a05a0e0 fffffa80`077ee100 fffff880`05c25dfd : 0xfffffa80`0b7acfe0
fffff880`0b07e000 00000000`00000000 : fffffa80`0a05a0e0 fffffa80`077ee100 fffff880`05c25dfd fffff880`06340880 : NETw5s64+0x15f02


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETw5s64+15f02
fffff880`05c29f02 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  NETw5s64+15f02

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETw5s64

IMAGE_NAME:  NETw5s64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ba1b871

FAILURE_BUCKET_ID:  X64_0xc2_7_W3Rx_NETw5s64+15f02

BUCKET_ID:  X64_0xc2_7_W3Rx_NETw5s64+15f02

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

 

[0pTicaL]

Second update drivers

vpcnfltr.sys        fffff880`01df9000    0x00015000    0x49e5755d    4/15/2009 01:49:17            fffff880`01de4000                
[COLOR=Red]vpchbus.sys        fffff880`066b8000    0x0003c000    0x49e57560    4/15/2009 01:49:20            fffff880`0667c000 [/COLOR]               
[COLOR=Red]vpcusb.sys        fffff880`01637000    0x0001d000    0x49e57560    4/15/2009 01:49:20            fffff880`0161a000      [/COLOR]          
vpcvmm.sys        fffff880`044b5f00    0x00056f00    0x49e57562    4/15/2009 01:49:22            fffff880`0445f000                
spldr.sys        fffff880`01f79000    0x00008000    0x4a0858bb    5/11/2009 12:56:27            fffff880`01f71000                
amdxata.sys        fffff880`0121b000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59            fffff880`01210000                
[COLOR=Red]nvraid.sys        fffff880`00e9f000    0x00029000    0x4a13a5ac    5/20/2009 02:39:40            fffff880`00e76000  [/COLOR]              
enecir.sys        fffff880`04448000    0x0001d000    0x4a48243a    6/28/2009 22:17:30            fffff880`0442b000                
Accelerometer.sys        fffff880`0659d000    0x0000c000    0x4a54e862    7/8/2009 14:41:38            fffff880`06591000                
hpdskflt.sys        fffff880`01d68000    0x0000a000    0x4a54e862    7/8/2009 14:41:38            fffff880`01d5e000

Thank you for your input.

Do you mean to update the drivers in red?