BSoD during Startup

Hello,
Often (more than half the time) when I boot up my PC it quickly flashes a blue screen error during startup and then reboots, telling me that I need to run repair mode. Typically after an hour or two of repair attempts (I usually end up having to boot from the Windows DVD) I can get it going again, but it then gives me no information about what caused the crash. This morning, however, when I finally managed to boot into Windows it gave me the following information about the BSoD:

Code:

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

Additional information about the problem:
  BCCode:    be
  BCP1:    FFFFF8800513CED8
  BCP2:    8000000127A58121
  BCP3:    FFFFF88003DB6610
  BCP4:    000000000000000B
  OS Version:    6_1_7600
  Service Pack:    0_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\061910-31839-01.dmp
  C:\Users\Scott\AppData\Local\Temp\WER-80324-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Any ideas what's causing the problem? The computer is basically unusable at this point, and I'd really rather not have to return it.

Thanks,
M. Piedlourde (AKA Scott)

Can you still get into window (sorry, you use the word 'unusable' so I'm not sure what you mean)? If yes, can you please upload the minidump file so that someone here can analyze it for ya
https://www.sevenforums.com/crash-loc...d-problem.html

Regard
Tuan

Hi Tuan,
Sorry for not posting the necessary information. I've attached it to this post. By "unusable" I just meant that I can't really rely on a computer that fails to boot up so often.
Thanks for your quick response.

Your dump file shows an error code of BE

STOP 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY

Usual causes: Device driver, Memory

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff8800513ced8, 8000000127a58121, fffff88003db6610, b}

*** WARNING: Unable to verify timestamp for RtHDMIVX.sys
*** ERROR: Module load completed but symbols could not be loaded for RtHDMIVX.sys
Probably caused by : hardware ( portcls!PcAddToPropertyTable+20f )

Followup: MachineOwner

Try removing 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

Then see how it goes. If you get another BSOD, upload that latest BSOD file(s) and we will go from there.

Hi there
I see that Carl has gone through most important thing in the minidump file. I just realized that you have some old driver, please download and install fresh copy of them:

Code:

sisraid4 sisraid4.sys Thu Oct 02 04:56:04 2008 (48E3F1F4)
SiSRaid2 SiSRaid2.sys Thu Sep 25 01:28:20 2008 (48DA86C4)
lsi_fc   lsi_fc.sys   Wed Dec 10 05:46:09 2008 (493EF531)
iirsp    iirsp.sys    Wed Dec 14 04:47:54 2005 (439F418A)
arc      arc.sys      Fri May 25 04:27:55 2007 (4656035B)
adpu320  adpu320.sys  Wed Feb 28 07:04:15 2007 (45E4C6FF)
adpahci  adpahci.sys  Wed May 02 00:30:09 2007 (46377921)
adp94xx  adp94xx.sys  Sat Dec 06 06:54:42 2008 (4939BF42)

Do what Carl suggest first to see if no more BSod, then please update those drivers

Regard
Tuan

Carl: OK, I deleted Daemon Tools and sptd.sys and restarted a few times without any trouble. Hopefully that's solved it, although the crashes have been pretty unpredictable so it's difficult to tell if it's actually fixed this early on.

Tuan: Sorry to play the role of the dumb noob again, but how do I update those drivers? Should I just google the driver names?

Thanks again for all your help.

Good catch, ttran. I stopped looking after I found sptd. I should have kept going. Thanks, good team work. :)

That driver is an Intel Raid StorPort Driver. I would go to the Intel site and download it from there if there is an updated driver. However, let your system run a while and see how it behaves. Be sure to post back and let us know ether way. I have my fingers crossed! :)

Yes, you can Google the drivers to see what they are.