Solved BSOD at Boot.

Lorien · Oct 26, 2010

Hello,

I'm sorry I'm the one who now needs help, but I do.

I ran the BSOD report and it is attached. I could not run the Performance report as it gave me an error that it could not find the path specified.

My system specs are current. The laptop was originally OEM XP Pro, but was upgraded to Vista 18 months ago (with a retail upgrade disk) and I've had no real problems until now. It had been in sleep mode for several days when I decided to reboot and BAM! BSOD. I hope the following helps instead of the performance report:

Product
Windows
Problem
Shut down unexpectedly
Date
10/26/2010 6:51 AM
Status
Not Reported
Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.256.6
Locale ID: 1033
Files that help describe the problem (some files may no longer be available)
Mini102610-03.dmp
sysdata.xml
Version.txt
Extra information about the problem
BCCode: d6
BCP1: 8FC8B000
BCP2: 00000000
BCP3: 8EB3F199
BCP4: 00000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 256_1

If I can provide any additional info, just ask. I'm in Safe Mode with networking right now.

Thanks in advance.

Shadowjk · Oct 26, 2010

STOP Error 0x000000D6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION

STOP error 0xD6 means the driver accessed memory beyond the end of its pool allocation. STOP code 0x000000D6 may also display "DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION" on the same STOP message.

Did you do any Recent Updates? Or have installed any New Programs?

Could you test your Memory for me and Check To see if it comes out Clear (Just to check)

Many Thanks,
Josh

Lorien · Oct 26, 2010

I ran the Windows Memory Test and it said it found no errors. It was supposed to show a report when I rebooted but I got a BSOD and then when I booted into Safe Mode with Networking, no report showed up - but according to the screen I was watching, no problems were detected.

I've installed and uninstalled quite a bit since the last time I rebooted - maybe up to a week ago (and probably some updates too though I haven't checked and have driver updates disabled). I'm tempted to try System Restore and Startup Repair and then an SFC and chkdsk, but I'd rather have advice from here before doing anything in case there's a better solution to try.

So where do we go from here? Was the attached file helpful at all in revealing the problem? Could the inability to generate a perfmon /report be related?

Thanks!

Lorien · Oct 26, 2010

Actually, I'm just going to go ahead and try those other options to see if they help. I don't suppose it can hurt.

Shadowjk · Oct 26, 2010

I would Try that it is most likely Driver Related Issues Try a System Restore to a Point Before you got the Problem then afterwards try a Check disk and SFC Etc

richc46 · Oct 26, 2010

Code:

 icrosoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp2_Windows_NT6_BSOD_jcgriff2[1].zip\Windows_NT6_BSOD_jcgriff2\Mini102610-03.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
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0x81c04000 PsLoadedModuleList = 0x81d1bc70
Debug session time: Tue Oct 26 06:46:12.377 2010 (GMT-4)
System Uptime: 0 days 0:00:28.111
Loading Kernel Symbols
...............................................................
..................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D6, {8fc8b000, 0, 8eb3f199, 0}
Unable to load image \SystemRoot\system32\drivers\sthda.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sthda.sys
*** ERROR: Module load completed but symbols could not be loaded for sthda.sys
Probably caused by : sthda.sys ( sthda+f5199 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (d6)
N bytes of memory was allocated and more than N bytes are being referenced.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: 8fc8b000, memory referenced
Arg2: 00000000, value 0 = read operation, 1 = write operation
Arg3: 8eb3f199, if non-zero, the address which referenced memory.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
 
READ_ADDRESS: GetPointerFromAddress: unable to read from 81d3b868
Unable to read MiSystemVaType memory at 81d1b420
 8fc8b000 
FAULTING_IP: 
sthda+f5199
8eb3f199 ??              ???
MM_INTERNAL_CODE:  0
CUSTOMER_CRASH_COUNT:  3
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD6
PROCESS_NAME:  System
CURRENT_IRQL:  0
TRAP_FRAME:  84f759f0 -- (.trap 0xffffffff84f759f0)
ErrCode = 00000000
eax=8fc8affb ebx=84f70023 ecx=8fc8ffff edx=8fc8ae20 esi=84f75b40 edi=8fc8affb
eip=8eb3f199 esp=84f75a64 ebp=84f75a70 iopl=0         nv up ei ng nz ac po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210292
sthda+0xf5199:
8eb3f199 ??              ???
Resetting default scope
LAST_CONTROL_TRANSFER:  from 81c51dd4 to 81c9c38d
STACK_TEXT:  
84f759d8 81c51dd4 00000000 8fc8b000 00000000 nt!MmAccessFault+0x10a
84f759d8 8eb3f199 00000000 8fc8b000 00000000 nt!KiTrap0E+0xdc
WARNING: Stack unwind information not available. Following frames may be wrong.
84f75a60 90204e90 89f89094 84f75b64 84f75a94 sthda+0xf5199
84f75a70 8eb3f113 84f75b40 8fc8affe 00000023 0x90204e90
84f75a94 8eb24329 84f75b40 00000023 0000ffff sthda+0xf5113
84f75b44 8eb24d15 8a122008 84f75b70 00f75b64 sthda+0xda329
84f75b7c 8eb2cc99 89bd62b0 8eb2e872 00000000 sthda+0xdad15
84f75bcc 8eb6e86d 89bd62bc 00000000 00000000 sthda+0xe2c99
84f75bd0 89bd62bc 00000000 00000000 9031edf8 portcls!CPortWaveCyclic::Init+0xab
84f75bec 84f75c28 8eb47973 00000000 89b09c80 0x89bd62bc
00000000 00000000 00000000 00000000 00000000 0x84f75c28
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
sthda+f5199
8eb3f199 ??              ???
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  sthda+f5199
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: sthda
IMAGE_NAME:  sthda.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  44247bed
FAILURE_BUCKET_ID:  0xD6_VRF_sthda+f5199
BUCKET_ID:  0xD6_VRF_sthda+f5199
Followup: MachineOwner
---------
1: kd> lmtsmn
start    end        module name
8d582000 8d58f080   1394BUS  1394BUS.SYS  Sat Jan 19 00:53:27 2008 (47919057)
80690000 806d6000   acpi     acpi.sys     Sat Apr 11 00:19:03 2009 (49E01A37)
807bb000 807c3000   atapi    atapi.sys    Sat Apr 11 00:39:09 2009 (49E01EED)
807c3000 807e1000   ataport  ataport.SYS  Sat Apr 11 00:39:10 2009 (49E01EEE)
8ca0f000 8d197000   atikmdag atikmdag.sys Thu Jan 18 19:03:19 2007 (45B00AC7)
80720000 8072a000   BATTC    BATTC.SYS    Sat Jan 19 00:32:45 2008 (47918B7D)
8d562000 8d572000   bcm4sbxp bcm4sbxp.sys Tue Nov 21 07:25:43 2006 (4562F047)
8d495000 8d50a000   bcmwl6   bcmwl6.sys   Tue Oct 03 22:38:08 2006 (45231E90)
8048b000 80493000   BOOTVID  BOOTVID.dll  Sat Jan 19 02:27:15 2008 (4791A653)
829cb000 829e3000   cdrom    cdrom.sys    Sat Apr 11 00:39:17 2009 (49E01EF5)
804d4000 805b4000   CI       CI.dll       Sat Apr 11 02:25:22 2009 (49E037D2)
82b9d000 82bbe000   CLASSPNP CLASSPNP.SYS Sat Apr 11 00:39:05 2009 (49E01EE9)
80493000 804d4000   CLFS     CLFS.SYS     Sat Apr 11 00:13:51 2009 (49E018FF)
82bfb000 82bfe780   CmBatt   CmBatt.sys   Sat Jan 19 00:32:47 2008 (47918B7F)
8071d000 8071f900   compbatt compbatt.sys Sat Jan 19 00:32:47 2008 (47918B7F)
82bc7000 82bd4000   crashdmp crashdmp.sys Sat Apr 11 00:39:12 2009 (49E01EF0)
82bbe000 82bc7000   crcdisk  crcdisk.sys  Thu Nov 02 04:52:27 2006 (4549B1CB)
82b8c000 82b9d000   disk     disk.sys     Sat Apr 11 00:39:14 2009 (49E01EF2)
8eb87000 8ebac000   drmk     drmk.sys     Sat Jan 19 01:53:02 2008 (47919E4E)
82bdf000 82be7000   dump_atapi dump_atapi.sys Sat Apr 11 00:39:09 2009 (49E01EED)
82bd4000 82bdf000   dump_dumpata dump_dumpata.sys Sat Apr 11 00:39:09 2009 (49E01EED)
8292a000 829cb000   dxgkrnl  dxgkrnl.sys  Thu Sep 24 21:27:14 2009 (4ABC1C72)
82b65000 82b8c000   ecache   ecache.sys   Sat Apr 11 00:40:12 2009 (49E01F2C)
807e1000 807f1000   fileinfo fileinfo.sys Sat Jan 19 00:34:27 2008 (47918BE3)
805b4000 805e6000   fltmgr   fltmgr.sys   Sat Apr 11 00:13:59 2009 (49E01907)
828f7000 82912000   fwpkclnt fwpkclnt.sys Sat Apr 11 00:45:42 2009 (49E02076)
829e3000 829ea000   GEARAspiWDM GEARAspiWDM.sys Mon Aug 07 13:11:27 2006 (44D7743F)
81fbd000 81ff0000   hal      halmacpi.dll Sat Apr 11 00:13:13 2009 (49E018D9)
8d408000 8d495000   HDAudBus HDAudBus.sys Sat Apr 11 00:42:41 2009 (49E01FC1)
8d5be000 8d5d1000   i8042prt i8042prt.sys Sat Jan 19 00:49:17 2008 (47918F5D)
80783000 8078a000   intelide intelide.sys Sat Jan 19 00:49:42 2008 (47918F76)
82912000 82921000   intelppm intelppm.sys Sat Jan 19 00:27:20 2008 (47918A38)
8ca00000 8ca0b000   kbdclass kbdclass.sys Sat Jan 19 00:49:14 2008 (47918F5A)
80403000 8040a000   kdcom    kdcom.dll    Sat Apr 11 02:25:29 2009 (49E037D9)
8dba1000 8dbcb000   ks       ks.sys       Sat Apr 11 00:38:47 2009 (49E01ED7)
82204000 82275000   ksecdd   ksecdd.sys   Mon Jun 15 08:48:53 2009 (4A364335)
8040a000 8047a000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Apr 11 02:23:19 2009 (49E03757)
8ffc2000 8ffcf000   modem    modem.sys    Sat Jan 19 00:57:16 2008 (4791913C)
8d1ef000 8d1fa000   mouclass mouclass.sys Sat Jan 19 00:49:14 2008 (47918F5A)
80798000 807a8000   mountmgr mountmgr.sys Sat Jan 19 00:49:13 2008 (47918F59)
806df000 806e7000   msisadrv msisadrv.sys Sat Jan 19 00:32:51 2008 (47918B83)
8da0e000 8da3d000   msiscsi  msiscsi.sys  Sat Apr 11 00:40:07 2009 (49E01F27)
82380000 823ab000   msrpc    msrpc.sys    Sat Apr 11 00:37:32 2009 (49E01E8C)
8dbcb000 8dbd5000   mssmbios mssmbios.sys Sat Jan 19 00:32:55 2008 (47918B87)
82b56000 82b65000   mup      mup.sys      Sat Apr 11 00:14:12 2009 (49E01914)
82275000 82380000   ndis     ndis.sys     Sat Apr 11 00:45:52 2009 (49E02080)
8daa0000 8daab000   ndistapi ndistapi.sys Sat Jan 19 00:56:24 2008 (47919108)
8daab000 8dace000   ndiswan  ndiswan.sys  Sat Apr 11 00:46:31 2009 (49E020A7)
8ea39000 8ea4a000   NDProxy  NDProxy.SYS  Sat Jan 19 00:56:28 2008 (4791910C)
823ab000 823e6000   NETIO    NETIO.SYS    Sat Apr 11 00:46:21 2009 (49E0209D)
81c04000 81fbd000   nt       ntkrpamp.exe Tue Jun 08 10:36:44 2010 (4C0E557C)
82a05000 82b15000   Ntfs     Ntfs.sys     Sat Apr 11 00:14:34 2009 (49E0192A)
8d572000 8d581300   ohci1394 ohci1394.sys Sat Apr 11 00:43:04 2009 (49E01FD8)
8070e000 8071d000   partmgr  partmgr.sys  Sat Apr 11 00:39:19 2009 (49E01EF7)
807a8000 807ad580   pavboot  pavboot.sys  Thu Jun 19 11:23:00 2008 (485A79D4)
806e7000 8070e000   pci      pci.sys      Sat Apr 11 00:19:16 2009 (49E01A44)
807ae000 807b5000   pciide   pciide.sys   Thu Nov 02 04:51:35 2006 (4549B197)
8078a000 80798000   PCIIDEX  PCIIDEX.SYS  Sat Apr 11 00:39:09 2009 (49E01EED)
8eb5a000 8eb87000   portcls  portcls.sys  Sat Apr 11 00:42:48 2009 (49E01FC8)
8047a000 8048b000   PSHED    PSHED.dll    Sat Apr 11 02:25:32 2009 (49E037DC)
8d400000 8d404480   pxkbf    pxkbf.sys    Thu Oct 21 11:47:41 2010 (4CC0609D)
807b5000 807bab80   pxscan   pxscan.sys   Thu Oct 21 11:47:43 2010 (4CC0609F)
8da89000 8daa0000   rasl2tp  rasl2tp.sys  Sat Jan 19 00:56:33 2008 (47919111)
8dace000 8dadd000   raspppoe raspppoe.sys Sat Apr 11 00:46:30 2009 (49E020A6)
8dadd000 8daf1000   raspptp  raspptp.sys  Sat Jan 19 00:56:34 2008 (47919112)
8daf1000 8db06000   rassstp  rassstp.sys  Sat Apr 11 00:46:40 2009 (49E020B0)
8db06000 8db8f000   rdpdr    rdpdr.sys    Sat Apr 11 00:52:32 2009 (49E02210)
8d5aa000 8d5b0f80   rimmptsk rimmptsk.sys Thu Jul 14 05:58:13 2005 (42D63735)
8d5b1000 8d5bd880   rimsptsk rimsptsk.sys Tue Jul 12 06:00:27 2005 (42D394BB)
8d1a3000 8d1ee300   rixdptsk rixdptsk.sys Thu Jul 14 04:28:37 2005 (42D62235)
8d590000 8d5aa000   sdbus    sdbus.sys    Sat Apr 11 00:19:14 2009 (49E01A42)
82b4e000 82b56000   spldr    spldr.sys    Thu Jun 21 20:29:17 2007 (467B17DD)
8ea4a000 8eb59720   sthda    sthda.sys    Fri Mar 24 19:08:29 2006 (44247BED)
8da3d000 8da7e000   storport storport.sys Sat Apr 11 00:39:19 2009 (49E01EF7)
8db9f000 8dba0380   swenum   swenum.sys   Sat Jan 19 00:49:20 2008 (47918F60)
8d5d1000 8d5fb100   SynTP    SynTP.sys    Mon Nov 06 20:34:46 2006 (454FE2B6)
8280d000 828f7000   tcpip    tcpip.sys    Wed Jun 16 09:45:41 2010 (4C18D585)
8da7e000 8da89000   TDI      TDI.SYS      Sat Jan 19 00:57:10 2008 (47919136)
8db8f000 8db9f000   termdd   termdd.sys   Sat Apr 11 00:51:14 2009 (49E021C2)
82bf2000 82bfb000   tunmp    tunmp.sys    Sat Jan 19 00:55:40 2008 (479190DC)
82be7000 82bf2000   tunnel   tunnel.sys   Thu Feb 18 06:28:13 2010 (4B7D244D)
8dbd5000 8dbe2000   umbus    umbus.sys    Sat Jan 19 00:53:40 2008 (47919064)
8d5fc000 8d5fd700   USBD     USBD.SYS     Sat Jan 19 00:53:17 2008 (4791904D)
8d553000 8d562000   usbehci  usbehci.sys  Sat Apr 11 00:42:52 2009 (49E01FCC)
8ea04000 8ea39000   usbhub   usbhub.sys   Sat Apr 11 00:43:14 2009 (49E01FE2)
8d515000 8d553000   USBPORT  USBPORT.SYS  Sat Apr 11 00:42:55 2009 (49E01FCF)
8d50a000 8d515000   usbuhci  usbuhci.sys  Sat Jan 19 00:53:20 2008 (47919050)
8072a000 80739000   volmgr   volmgr.sys   Sat Jan 19 00:49:51 2008 (47918F7F)
80739000 80783000   volmgrx  volmgrx.sys  Sat Apr 11 00:39:25 2009 (49E01EFD)
82b15000 82b4e000   volsnap  volsnap.sys  Sat Apr 11 00:39:37 2009 (49E01F09)
8ebac000 8ebe8000   VSTAZL3  VSTAZL3.SYS  Tue Jun 20 13:39:49 2006 (449832E5)
8ff0f000 8ffc2000   VSTCNXT3 VSTCNXT3.SYS Tue Jun 20 13:39:37 2006 (449832D9)
8fe0b000 8ff0f000   VSTDPV3  VSTDPV3.SYS  Tue Jun 20 13:41:01 2006 (4498332D)
8d197000 8d1a3000   watchdog watchdog.sys Sat Apr 11 00:22:43 2009 (49E01B13)
80607000 80683000   Wdf01000 Wdf01000.sys Sat Jan 19 00:52:21 2008 (47919015)
80683000 80690000   WDFLDR   WDFLDR.SYS   Sat Jan 19 00:52:19 2008 (47919013)
82921000 8292a000   wmiacpi  wmiacpi.sys  Sat Jan 19 00:32:47 2008 (47918B7F)
806d6000 806df000   WMILIB   WMILIB.SYS   Sat Jan 19 00:53:08 2008 (47919044)

Outdated Drivers: Ignore any MS Drivers

Code:

rimsptsk.sys Tue Jul 12 06:00:27 2005 
rixdptsk.sys Thu Jul 14 04:28:37 2005 
rimmptsk.sys Thu Jul 14 05:58:13 2005 
sthda.sys    Fri Mar 24 19:08:29 2006 
VSTCNXT3.SYS Tue Jun 20 13:39:37 2006 
VSTAZL3.SYS  Tue Jun 20 13:39:49 2006 
VSTDPV3.SYS  Tue Jun 20 13:41:01 2006 
bcmwl6.sys   Tue Oct 03 22:38:08 2006 
pciide.sys   Thu Nov 02 04:51:35 2006 
crcdisk.sys  Thu Nov 02 04:52:27 2006 
SynTP.sys    Mon Nov 06 20:34:46 2006 
bcm4sbxp.sys Tue Nov 21 07:25:43 2006 
atikmdag.sys Thu Jan 18 19:03:19 2007

Sthda.sys
Productname: C-Major Audio
Description: NDRC
Company: SigmaTel, Inc.
Update this driver. The primary cause of the BSOD

The reports that you have submitted reveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receive the more clues are made available improving our chances of finding a solution to your problem. You may have to experience several more BSODs until the final answer is discovered.

If overclocking restore normal settings

SFC /scannow
System Files - SFC Command
Update outdated listed drivers. If I have inadvertently listed any Microsoft Drivers, they can be ignored. issues-drivers.html

Scan with your Anti Virus

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 help you 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
- - 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: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/

After performing all of the above, post back with any new BSOD reports, or indicate that the attempted repairs were successful.

These reports are not definitive but merely point the way to a solution. It is very important to remember that the dump reports only give clues as to the problem and although it is very easy to analyze only one or two, usually more are needed. If you experience additional BSOD after installing a current version of the driver in question, be sure to post so that we can use the additional information to assist you in preventing the BSOD's

Lorien · Oct 26, 2010

I did a Startup Repair - no problems found. Then, instead of System Restore, I rebooted into Last Known Good Configuration and it came back - no BSOD! It had changed my Theme, but that was easily fixed. It had also shut off MSE, but a simple click and it turned on. I'm not sure why that worked (if it was a driver problem, why would last known good configuration make any difference?) - but I plan to do some serious testing to try to find out in case it comes back and to see if I can find out what in the heck happened.

That was very, very scary! I'll also be doing another image backup (even though the one I have is only a week or so old - but I'd rather have a current one) - but not until I see what happened (if I can figure it out) in case the problem still exists and I need the prior backup (I can't fit two on the drive).

Did you learn anything from the attachment - I haven't tried to read it yet (and I'm not familiar with a lot of it to trust myself to pinpoint the problem even if it is staring me in the face). Time for a SFC and a chkdsk and every test known to man. And I need to see exactly what has been installed in the last week or two that might have done this (if that's the cause at all).

But it was SO good to boot normally without the BSOD, I can't tell you. And the "solution" (assuming it fixed the problem and didn't just defer it to another date) isn't one I often see recommended but just on a hunch decided to give it a try as I wanted to avoid a System Restore if I could (yes, it's pretty easy to recover from it, but it can be time-consuming and I did quite a few installations since the last time I actually booted as opposed to just putting it into sleep mode).

If you have any specific suggestions on a test to run or what to look for, I'd welcome any ideas. I plan to do everything I know, but I may omit something helpful.

Thanks for responding and your help. It got me thinking in the right direction. Only a lucky guess made me try Last Known Good Configuration when I saw it instead of going back into Safe Mode.

Well, now for some serious work on my own computer for a change of pace. LOL!

EDIT: Just noticed your post, Richard. I have no clue what that product is. To my knowledge it was never installed (at least not by me) and I don't recall ever having used it. What is sthda.sys?

richc46 · Oct 26, 2010

sthda.sys appears to be some sort of audio driver

richc46 · Oct 26, 2010

It appears that you were able to solve, temporarily, the BSOD. Based upon my experience, it will happen again. To prevent future problems, update the driver in question. If you do not need this driver, just delete or to be on the safe side change the .sys to .bup.
You have a collection of old drivers. I would update. Technolgy has been changing rapidly and your drivers have not. Update them. I have given sufficient information on the best way that this should be done. Do not use the built in update service. Any questions, just ask.

Shadowjk · Oct 26, 2010

You said you had Installed and Uninstalled a few Programs... I would recommend Restarting your Computer after every Uninstall or Install this make sure that all your Programs are "Up to Date"

richc46 · Oct 26, 2010

TY Josh for the kind words and rep. It was very nice of you.

Shadowjk · Oct 26, 2010

No problem I did Miss your Fantastic Answers

richc46 · Oct 26, 2010

I missed posting, too. But the time that I had in Europe was a once in a lifetime. I had a great time.

Shadowjk · Oct 26, 2010

I Hope you enjoyed it We aren't the Warmest Continent in the world but we do carry a few Monuments..etc

We as in Europe

Lorien · Oct 26, 2010

Thanks, Richard.

I've already found the update for the driver in question - it was available on the Dell site - the modified date changed only from 6/24/06 to 6/25/06 but the create date now says 8/30/2009. Plus it isn't available anywhere else except for sites where you need to pay to get driver updates - but one I found is only $30 for an annual subscription (which I will cancel before it renews) so I may give it a shot anyway as it identified available updates for many of the drivers you identified as obsolete (including the one that caused the problem which the driver update program still says is obsolete even though I used the most recent Dell update!). It seems finding updates for each individually (for free) is close to impossible and I've checked both the computer manufacturer, device manufacturer, the site you provided, and a search through Bing for almost all of them (which led me to this product).

Thanks very much for your help.

======================================================

Shadow,

I usually do reboot but I got lazy. I won't let that happen again.

Thanks to you as well!

Shadowjk · Oct 26, 2010

I usually Leave my Computer on and when I don't use it throughout the Day I put it into Sleep then at the End of the Day I Shut it down That works for me some may beg to differ

richc46 · Oct 26, 2010

Lorien,
Thanks for letting me help. We all get our satisfaction from helping strangers, but the feeling is even better when helping friends. Thanks for the generous rep.

Lorien · Oct 26, 2010

Shadowjk said:
I usually Leave my Computer on and when I don't use it throughout the Day I put it into Sleep then at the End of the Day I Shut it down That works for me some may beg to differ

I never put it in sleep mode during the day - I'm always either on it or checking it.

At night, I put it in Sleep mode. I have been doing this since my CPU usage dropped and it works again. I rarely reboot unless forced to by an update. But now I will do so after installs and uninstalls (and if I notice some updates installed without needing to boot). I like the fact that it starts faster and with all my applications opened to exactly where I want them (my "standard" setup). Still, I don't want to go through this again, so I'll reboot when changes occur to be on the safe side.

We each have our preferences - and they each have their positives and negatives. But I think with care (more than I had exercised before), either approach is perfectly acceptable though yours is possibly less taxing on the machine and possibly a bit safer.

Lorien · Oct 26, 2010

richc46 said:
Lorien,
Thanks for letting me help. We all get our satisfaction from helping strangers, but the feeling is even better when helping friends. Thanks for the generous rep.

I know what you mean - and the rep was well deserved as you spent time analyzing my problem and identified the cause (even if I'm going to have to spend $30 to get the updated drivers) and gave me some additional good advice which I have partially completed and will finish the rest before bedtime. I'm lucky what I tried worked - it should have been harder with replacing drivers and other things and I know you'd have helped me through that had it been necessary.

Thanks again!

Shadowjk · Oct 26, 2010

Lorien said:
Shadowjk said:

I usually Leave my Computer on and when I don't use it throughout the Day I put it into Sleep then at the End of the Day I Shut it down That works for me some may beg to differ

Click to expand...

I never put it in sleep mode during the day - I'm always either on it or checking it.

At night, I put it in Sleep mode. I have been doing this since my CPU usage dropped and it works again. I rarely reboot unless forced to by an update. But now I will do so after installs and uninstalls (and if I notice some updates installed without needing to boot). I like the fact that it starts faster and with all my applications opened to exactly where I want them (my "standard" setup). Still, I don't want to go through this again, so I'll reboot when changes occur to be on the safe side.

We each have our preferences - and they each have their positives and negatives. But I think with care (more than I had exercised before), either approach is perfectly acceptable though yours is possibly less taxing on the machine and possibly a bit safer.

As I said some may beg to differ

Solved BSOD at Boot.

Account Suspended

My Computer

Network Enthusiast

My Computer

Account Suspended

My Computer

Account Suspended

My Computer

Network Enthusiast

My Computer

My Computer

Account Suspended

My Computer

My Computer

My Computer

Network Enthusiast

My Computer

My Computer

Network Enthusiast

My Computer

My Computer

Network Enthusiast

My Computer

Account Suspended

My Computer

Network Enthusiast

My Computer

My Computer

Account Suspended

My Computer

Account Suspended

My Computer

Network Enthusiast

My Computer