10 Blue Screens of Death and counting, Vista.

[nerp]

Cool 'n' Quiet can be disabled in the BIOS. It generally shouldn't cause problems but some motherboards might not react as well as others. It is always highly recommended to be turned off when you're overclocking -- you're not doing that in this case, but still, it's worth a shot.

 

[ChronoReverse]

CnQ is in the bios, should just be a matter of turning it to disabled. It's still a good idea to update the drivers though.

 

[hooterville]

Ok,
There was a new update for the Nvidia 6150 and when I search motherboard driver update on the Nvidia site there shows one from July 07.

I do not have an Nvidia motherboard so do I need this driver also?

 

[MrPickins]

Originally posted by: hooterville
Ok,
There was a new update for the Nvidia 6150 and when I search motherboard driver update on the Nvidia site there shows one from July 07.

I do not have an Nvidia motherboard so do I need this driver also?

You do have an Nvidia motherboard (it is the 6150). You should definitely install the most recent drivers for it.

 

[MrPickins]

I also recommend a clean wipe and reinstall if drivers don't fix the issue. Some of the original bloatware may not have uninstalled properly.

 

[hooterville]

Originally posted by: MrPickins
I also recommend a clean wipe and reinstall if drivers don't fix the issue. Some of the original bloatware may not have uninstalled properly.

The only discs I have are the restore ones I made with the computer and I think they will put all that bloatware right back on the system.

I'm hoping the new drivers will fix my problem.

 

[Czar]

Its definetly most likely some broken driver, check out the mini dump file
http://support.microsoft.com/kb/315263

 

[dclive]

Stash and Czar have given you the right advice.

You can also read my website for another (simpler) guide to reading the memory dump, complete with a few examples. Read up on it, and then post the output from !analyze -v here for a few of the dumps so we can all read about it. (By the time you do that the culprit may be obvious to you.)

 

[hooterville]

OK, I'll read up on the memory Dumps and post themASAP.

I installed a driver for the 6150LE from Nvidia site that was realeased on 12-20-07 and now windows update is trying to download and install an Nvidia driver from 11-20.

Should I let this one install?

 

[dclive]

Originally posted by: hooterville
OK, I'll read up on the memory Dumps and post themASAP.

I installed a driver for the 6150LE from Nvidia site that was realeased on 12-20-07 and now windows update is trying to download and install an Nvidia driver from 11-20.

Should I let this one install?

Please analyze your dumpfiles before doing anything else.

 

[hooterville]

OK, When trying to open the minidump with WinDbg it says I do not have permission to open this file.

How do I get past this?

 

[dclive]

Can you copy the minidump files to your desktop?

 

[hooterville]

I moved it to the desktop and this is all I get:

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Desktop\Mini010208-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:

I only have one dump file in the minidump.

I have no idea what I'm doing

 

[hooterville]

I got a little more.


Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Desktop\Mini010208-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x82400000 PsLoadedModuleList = 0x82511e10
Debug session time: Wed Jan 2 16:04:11.886 2008 (GMT-5)
System Uptime: 0 days 7:47:47.202
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000B8, {824f8300, 8e3bc3a0, 824f2000, 0}

*** WARNING: Unable to verify timestamp for HSX_CNXT.sys
*** ERROR: Module load completed but symbols could not be loaded for HSX_CNXT.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ndis.sys -
***** Kernel symbols are WRONG. Please fix symbols to do analysis.


I searched and see that HSX_CNXT.sys is a modem driver.
This machine is on a dial up connection so how would I find a newer driver for this modem?

 

[dclive]

Originally posted by: hooterville
I got a little more.


*** WARNING: Unable to verify timestamp for HSX_CNXT.sys
*** ERROR: Module load completed but symbols could not be loaded for HSX_CNXT.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ndis.sys -
***** Kernel symbols are WRONG. Please fix symbols to do analysis.


I searched and see that HSX_CNXT.sys is a modem driver.
This machine is on a dial up connection so how would I find a newer driver for this modem?

I don't see you running !analyze -v; I think you need to re-read the BSOD page on my website, but I agree that it's most likely that the hsx_cnxt.sys driver is causing the problem; an analysis would confirm that.

Google for the driver, download the latest, and typically that will fix your problem. An analysis would let me say that a lot more confidently.

 

[hooterville]

Here is a better report:


Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Desktop\Mini010208-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x82400000 PsLoadedModuleList = 0x82511e10
Debug session time: Wed Jan 2 16:04:11.886 2008 (GMT-5)
System Uptime: 0 days 7:47:47.202
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000B8, {824f8300, 8e3bc3a0, 824f2000, 0}

*** WARNING: Unable to verify timestamp for HSX_CNXT.sys
*** ERROR: Module load completed but symbols could not be loaded for HSX_CNXT.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ndis.sys -
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************


Probably caused by : HSX_CNXT.sys ( HSX_CNXT+2fef8 )

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

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

ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: 824f8300, Original thread which is the cause of the failure
Arg2: 8e3bc3a0, New thread
Arg3: 824f2000, Stack address of the original thread
Arg4: 00000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************



FAULTING_MODULE: 82400000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47155cb1

FAULTING_THREAD: 824f8300

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xB8

LAST_CONTROL_TRANSFER: from 824293a7 to 82490e46

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
824f1304 824293a7 824f8300 00000103 864f13f0 nt+0x90e46
824f1364 8bc4eef8 876dddac 00000000 00000000 nt+0x293a7
824f1380 8bc4ef8f 00000001 82532202 824f13a4 HSX_CNXT+0x2fef8
824f1390 8bcc2511 876dd8c0 864f13f0 00000002 HSX_CNXT+0x2ff8f
824f13a4 8bcc0602 876dd8c0 864f13f0 876dd924 HSX_CNXT+0xa3511
824f13c8 82427f83 876dd808 864f13f0 864f13f0 HSX_CNXT+0xa1602
824f13e0 8ab6ba94 864f14f0 876dd430 85c7c740 nt+0x27f83
824f13f4 82427f83 864f14f0 864f13f0 864f13f0 modem!UniWrite+0x4a
824f140c a6f70fe1 85d08064 85ad80e8 82454203 nt+0x27f83
824f1424 a6f71010 859b37f0 85d08064 824f1458 asyncmac!AsyncSendPacket+0xfb
824f1434 806ff5bb 85d0aa30 85c7c738 85d08064 asyncmac!MpSend+0x22
824f1458 8bec3e33 85c6ea28 85c7c738 85d08064 ndis!NdisMTransferDataComplete+0x3d5
824f1484 8bec4619 00000000 a55a7008 00000001 ndiswan!SendOnLegacyLink+0x102
824f14e0 8bec48cf 00000010 85d08dc0 85d08008 ndiswan!FramePacket+0x2f5
824f1518 8bec4b03 a55a7008 00000000 824f154c ndiswan!SendFromProtocol+0xbb
824f1558 8bec52d5 015a7008 8beca000 00000000 ndiswan!SendPacketOnBundle+0x17c
824f1580 8bebea8f 864e33a8 00000000 85fc27a8 ndiswan!NdisWanQueueSend+0x4e6
824f159c 807018eb 864e33a8 824f15e4 00000001 ndiswan!MPSendPackets+0x54
824f15c4 80701732 824f15e8 824f15e4 00000001 ndis!NdisMSendComplete+0x1891
824f162c 8063aae4 878300e8 85c462d0 00000000 ndis!NdisMSendComplete+0x16d8
824f164c 8063ab98 85c462d0 85c462d0 00000000 ndis!NdisMFreeNetBufferSGList+0xfb
824f1664 8c89fe58 887fe538 85c462d0 00000000 ndis!NdisFSendNetBufferLists+0x18
824f16e0 8063ab76 85ce5a10 01c462d0 00000000 pacer!PcFilterSendNetBufferLists+0x232
824f16fc 806fe64a 85c462d0 85c462d0 00000000 ndis!NdisMFreeNetBufferSGList+0x18d
824f1720 8c8908dd 887d6bb8 85c462d0 00000000 ndis!NdisSendNetBufferLists+0x4f
824f1768 8c50b935 85be8768 00000000 824f18ec wanarp!WanIpSendPackets+0x193
824f17a8 8c50cf6a 8c5569c8 00000000 00000000 tcpip!IppFragmentPackets+0x203
824f17e0 8c50c601 8c5569c8 824f18ec 8c5569c8 tcpip!IppDispatchSendPacketHelper+0x259
824f1878 8c50be01 004f18ec 824f1a28 9fc5b008 tcpip!IppPacketizeDatagrams+0x7ea
824f19d0 8c50e2ea 00000000 00000007 8c5569c8 tcpip!IppSendDatagramsCommon+0x4ab
824f19f0 8c4dd5d2 887161f0 824f1a08 887161f0 tcpip!IpNlpSendDatagrams+0x4b
824f1a78 8c4dd52e 887161f0 824f1b58 00000000 tcpip!IppSlowSendDatagram+0x3e
824f1ac8 8c513088 887161f0 824f1b01 824f1b58 tcpip!IpNlpFastSendDatagram+0x3fd
824f1b90 8c502465 00000000 85d72a20 00000002 tcpip!TcpTcbHeaderSend+0x434
824f1bc0 8c5016bc 824f1cc8 824f1c88 00000001 tcpip!TcpFlushDelay+0x122
824f1bf0 824a99d1 88752c98 00000000 061fdbb3 tcpip!TcpPeriodicTimeoutHandler+0x3be
824f1ce8 824a9321 00000000 00000000 001b73ff nt+0xa99d1
824f1d50 824913ee 00000000 0000000e 00000000 nt+0xa9321
824f8740 00000000 824f8748 824f8748 824f8750 nt+0x913ee


STACK_COMMAND: .thread 0xffffffff824f8300 ; kb

FOLLOWUP_IP:
HSX_CNXT+2fef8
8bc4eef8 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: HSX_CNXT+2fef8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: HSX_CNXT

IMAGE_NAME: HSX_CNXT.sys

BUCKET_ID: WRONG_SYMBOLS

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

0: kd> lmvm HSX_CNXT
start end module name
8bc1f000 8bcd4000 HSX_CNXT T (no symbols)
Loaded symbol image file: HSX_CNXT.sys
Image path: \SystemRoot\system32\DRIVERS\HSX_CNXT.sys
Image name: HSX_CNXT.sys
Timestamp: Tue Oct 16 20:52:01 2007 (47155CB1)
CheckSum: 000A9923
ImageSize: 000B5000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0

I believe it is the HSX_CNXT.sys that is my problem.

I'm having problems finding the correct drivers for this.

Also does it hurt to delete these dump files?

 

[dclive]

Delete away if you want, but they're so small, why bother?

Google the driver or contact your OEM that supplied you (Dell, Compaq) and they can give you the new drivers.

 

[dclive]

Pretty easy, isn't it? You don't need to guess, you don't need to mess around -- if you have a bluescreen (BSOD), just download the debugger, do an analysis, and you're done (assuming software; if hardware issue, typically you'll just see lots of random crashes)!

 

[hooterville]

Ok,
It says that I have the latest drivers for this modem.

What do I do now?

HSX_CNXT.sys

Conexant Systems

7.69.0.0 10/10/07

Any ideas?

Thanks.

 

[dclive]

What's "it" ?

 

[hooterville]

I had trouble finding the driver on google and tried the device manager and it states that I have the latest driver for this modem.

 

[dclive]

OK, it's a start. So when you called your OEM (HP) what did they say? Do they have a newer driver? If not, call up Conexant.

If you don't have any other recourse, pop out the modem and use another one with a different driver.

 

[hooterville]

I did not call HP yet.
I might just go over to best buy and purchase a new modem.
I wish I could get DSL out here in the woods

 

[hooterville]

Just had my 12th BSOD, this is getting old.

If anyone can find me a new driver for this please post a link?

HSX_CNXT.sys

7.69.0.0 Date 10-10-07

Conexant Systems SOFTK56 Modem Driver

PCI Soft Data Fax Modem with Smart CP.

I've looked all over and can not find anything.

Tomorrow I'll call HP and see what they have to say.

 

[Mem]

Originally posted by: hooterville
I did not call HP yet.
I might just go over to best buy and purchase a new modem.
I wish I could get DSL out here in the woods

dclive has right idea about getting a new modem,you tried removing the driver and disabling it for now to see if your BSOD go away?