Vista crashing, event log no help.

  • Thread starter Thread starter Evan Platt
  • Start date Start date
E

Evan Platt

Vista RC1..

She likes to crash. Blue screen, only visible for about a second.

Event log:

General:
The previous system shutdown at 7:54:18 PM on 9/8/2006 was unexpected.

Details:

- <Event
xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2006-09-09T02:55:56.000Z" />
<EventRecordID>4102</EventRecordID>
<Channel>System</Channel>
<Computer>desktop</Computer>
<Security />
</System>
- <EventData>
<Data>7:54:18 PM</Data>
<Data>9/8/2006</Data>
<Data />
<Data />
<Data>33149</Data>
<Data />
<Data />

<Binary>D6070900050008001300360012001003D60709000600090002003600120010033C0000003C000000000000000000000000000000000000000100000000000000</Binary>
</EventData>
</Event>


That's about it.

I can put the zip file up on my webserver if it would help..

Any suggestions: Is the above enough to go on?

Thanks.

Evan
 
Hi Evan,

No, it's not enough to go on. Questions:

Has this happened right from the start or after you installed something?
Are you set to create dump files on system crash?
Are you set to autorestart on system failure?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
 
Evan Platt said:
Vista RC1..

She likes to crash. Blue screen, only visible for about a second.
Click to expand...

Need more information. Is this during install, post install, what were
you doing when it happened?

I don't have a specific answer, but look at this article below.
This is new since the 5536 version.

http://www.aeroxp.org/board/index.php?showtopic=5647

We've all had to deal with it. You know your computer has an inexplicable issue when it hangs
mid-air while doing some important or resource-consuming task. It has been a problem for as
long as anyone could remember, but nothing was really done to help the user or even the geeky
computer technician pinpoint the exact problem behind that mysterious random STOP error or
hid-air hang.

Expect that to change. In the pre-RC1 and RC1 builds of Windows Vista, people have noticed
something new. Machines which would often never STOP when running Vista would all of a sudden
shut down with a mysterious error code 0x1A. Already there has been a fiasco over why build
5600 was certified as RC1 when this particular error would constantly rear its ugly head.

The error is triggered by a new bugcheck which was added into the RC1 branch and merged into
the RTM line of builds. When Windows normally requests a zeroed page of memory, the memory
manager tells your machine to completely zero out a page of memory before allocating the zeroed
memory to the thread requesting it. In all OSes prior to Vista 5536, this process would go
unchecked. However, a recently added check to 5536 involves actually checking whether or not
the pages which were to be zeroed actually were zeroed out. Should the check find memory pages
which were supposed to be zeroed out but in fact were not, it would trigger your 0x1A STOP
error or any other error dealing with memory corruption. By RTM, it will have its own error
code (TBA) and name: PAGE_NOT_ZEROED.

The problems which cause this error are almost always hardware related. It will most likely be
one of three things: poorly seated DIMMs, bad RAM, or bad memory management on your
motherboard(Intel) or processor(AMD). It could arise from bad drivers, though the odds of that
are unlikely. Should you see the error, follow the usual hardware reseating guidelines such as
checking for dust or burned contact points. Even your power supply could be the source of the
issue.

Good, well-seated hardware makes for less hangs, and in the future, less blue screens in Vista.
 
Hi Evan,

No, it's not enough to go on. Questions:

Has this happened right from the start or after you installed something?
Click to expand...

Right from the start. All was well with the previous beta.
Are you set to create dump files on system crash?
Are you set to autorestart on system failure?
Click to expand...

Not sure. Where would I enable / disable these options?

Would I want to NOT autorestart on system failure?

(Yes, the computer boots right back up to the login screen).

Side / related question:

Is there a way to have a program automatically start before logging in
to windows?

(Mdameon mail server).

I put it in my startup, but doesn't launch until I log in.

Thanks. :)
 
Hi Evan,
Right from the start. All was well with the previous beta.
Click to expand...

Then either you have a bad image or there was change and something in your
system is no longer compatible.
Not sure. Where would I enable / disable these options?
Click to expand...

System properties/Advanced system settings/Startup and Recovery settings.
Would I want to NOT autorestart on system failure?
Click to expand...

If you want to read the blue screen error, yes. Afterwards, reset.
(Yes, the computer boots right back up to the login screen).

Side / related question:

Is there a way to have a program automatically start before logging in
to windows?
Click to expand...

If it's capable of running as a service, yes.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
 
Then either you have a bad image or there was change and something in your
system is no longer compatible.
Click to expand...

I'm hoping that's not the case. :(
System properties/Advanced system settings/Startup and Recovery settings.


If you want to read the blue screen error, yes. Afterwards, reset.
Click to expand...

AHh. Yep, it crashed again, and I was able to read it. No information
that was of any use (ie no device name listed or application or .sys
file).
If it's capable of running as a service, yes.
Click to expand...

That's what I was looking for. Thanks. :)
 
Hi Evan,

There were a number of changes to supported hardware with RC1, I would urge
that you run a compatibility check. Might also run verfier.exe (run as
administrator) to check the driver set.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
 
Vista RC1..

She likes to crash. Blue screen, only visible for about a second.
Click to expand...

Well this morning, (2AM), she crashed again. Upon reboot, I had a BIOS
error - well a BIOS beep.

1 long beep (well, 1 second or so), and a 2 second pause.

I'm trying to google to find the beep codes for that MoBo/ Bios.

Any ideas?

Thanks.

Evan
 
Back
Top