Vista crashing, I need a way to know whats wrong

[Timothy Davis [MSFT]]

Are you saying that he won't be able to upgrade to RTM? Why not?

 

[Frank Holman]

Are you saying that he won't be able to upgrade to RTM? Why not?

REALLY?

Where in the heck did I get the idea that it couldn't!?

 

[Curious]

See FAQ in the following link:

http://www.microsoft.com/windows/windows-7/faq.aspx

 

[Frank Holman]

See FAQ in the following link:

http://www.microsoft.com/windows/windows-7/faq.aspx

AHA!! I WAS RIGHT! For a minute there, that "MVP" had me wondering
if I was dreaming.

Quoting from that FAQ:

"When you install the final version of Windows 7, you'll need to do a
clean installation. So plan on backing up your data then reinstalling
your applications and restoring your data."

 

[Curious]

Even worse he is a MSFT employee and not a MVP and was not aware of the RC1
restrictions that have been posted at many websites.

 

[Frank Holman]

Even worse he is a MSFT employee and not a MVP and was not aware of the RC1
restrictions that have been posted at many websites.

SHEESH. One of those things that make you go "hmmm....".

 

[Abubakar]

You ARE aware that when the final release comes out, your RC1 setup

will be worthless, right?

actually the good news for me was that rc1 is valid for one year from now,
that and since the quality of the os is so good that i'm not worried about
rtm.

oh thats nasty. Vista should have some rules to detect such patterns and
prompt the user. Or maybe some setting which we could turn on to enable
UAC
like prompts if anything goes in n out of such critical folders.

Anyway I have already migrated 90% of my stuff to Windows 7 rc1, but this
installation of Vista is also going to be used for some time.

You ARE aware that when the final release comes out, your RC1 setup
will be worthless, right?

Randomly named .sys files, especially those located under
C:\Windows\System32\Drivers, are usually trojans. These certainly have
been known to cause these kernel crashes.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

Bugcheck IRQL_NOT_LESS_OR_EQUAL has several reasons to be thrown. This
particular instance was caused by a kernel driver dereferencing a null
pointer.

Unfortunately, I don't see an obvious culprit in the crash dump file -
as
the binary that dereferenced the pointer is Win32k.sys. In situations
like this, Win3k.sys is most likely the victim of another kernel driver
doing something bad.

To see what kinds of drivers/software you may have recently installed,
you can look at the [%windir%\inf\setupapi.*.log] files.

It appears that you do not have a driver loaded for your display
adapter - but instead are using VGA.sys. Is there a reason for this?

Also, I could not find any information on the kernel driver
awgqdlyk.sys,
which is loaded on your machine. You can find this file in your
[%windir%\system32\drivers] folder. You might want to see what that
file
is, and where it came from.


Hi Abubakar,

Please upload the crash dump file to the following URL:

https://sftus.one.microsoft.com/choosetransfer.aspx?key=1fa89359-ae3c-444f-8f40-cbd3adb352c8


Please note: This file transfer session will be removed once you
upload
the file.

right now i'm on this page:
http://www.microsoft.com/whdc/DevTools/Debugging/symbolpkg.mspx

Hi, Abubakar.

Rick is the expert here, not me. But I think the heart of your
problem is here:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 00000000
BCP2: 0000001B
BCP3: 00000001
BCP4: 83043A7F
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Your "BCCode: a" corresponds to Stop Code 0x0A. My starting point
for
researching Stop Codes is:
TROUBLESHOOTING WINDOWS STOP MESSAGES
http://www.aumha.org/a/stop.htm

One of the first listings there is:
0x0000000A: IRQL_NOT_LESS_OR_EQUAL

There are many possible causes and solutions for this error,
"Typically due to a bad driver, or faulty or incompatible hardware
or
software."

This should give you some ideas of the kinds of questions Rick will
need you to answer in your next post.

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP
Windows Live Mail 2009 (14.0.8064.0206) in Win7 Ultimate x64 RC 7100


Hi,

The details of the blue screen are crucial to identifying the
problem. Error codes, parameters, and any modules involved can all
provide clues. Check the event log for details and post them.

The second "crash" sounds more like a hardware freeze, not an
operating system issue but rather a problem component. Could also
be
related to overheating.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

Hi,

My vista crashed 2 times today. This is probably the first time
since december 2007 when I bought my laptop with Vista. I know
the
usual question would be to check if I installed some new drivers
or
any hardware device but thats not the case as far as I know. Its
a
Vista Ultimate system, with a cor 2 duo 2.ghz, 2gb ram, wifi etc.
The first time it crashed today was with a blue screen with the
usual bsod stuff printed on it (I know it can be different stuff
written there but right now I dont know the exact stuff other
than
'check for new hardware installation' msg). i was running visual
studio 2005 doing asp.net development with it. The second time
when
it crashed it hanged and the computer made one beep sound, but no
bsod, the computer just didnt reply, and here also I was
debugging
something in asp.net in vs 2k5.

Is there any software that that provide me some information that
may help me find out exactly whats wrong? Some internal
diagnostic
software that maybe ships with vista?

regards.



event log is so huge, there r enteries about every second ! And
search was taking time. I will search for more, but after the
second
crash the following was displayed when i logged in:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 00000000
BCP2: 0000001B
BCP3: 00000001
BCP4: 83043A7F
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini051409-01.dmp
C:\Users\Ab\AppData\Local\Temp\WER-99450-0.sysdata.xml
C:\Users\Ab\AppData\Local\Temp\WER192A.tmp.version.txt

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

The WER* files are not at there mentioned place, but the dump file
is
there. I remember reading someone's blog that the dump file can be
opened with windbg ?

In the meanwhile the system crashed one more time with blue screen.

..ab

 

[Abubakar]

Hi, I booted from windows 7's dvd and from the recovery console I tried to
find the sys file awgqdlyk.SYS but couldnt find it. Since the day I have
reported the crash problem my pc has not crashed.

Unless the crash dump is corrupted (doesn't appear to be), then no, it is
not misspelled.

8dc05000 8dc6b000 awgqdlyk (deferred)
Image path: \SystemRoot\System32\Drivers\awgqdlyk.SYS
Image name: awgqdlyk.SYS
Timestamp: Sun Jun 03 22:12:12 2007 (46639F2C)
CheckSum: 0005673F
ImageSize: 00066000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0

If you boot from your Vista installation DVD (or even the Win7 RC DVD),
there is an option to "repair your PC". If you select this, you should be
able to get to a window that will give you several options - one of which
is to open a command prompt. You can also use a linux live CD to do this.

From there, you can search for this .sys file. If you find it here, but
not when running Windows, then likely you have a virus. If you are able
to find this file, try copying it to a flash drive - I would be interested
in it if you could send it to me.

According to my information I'm using nvidia drivers version 177.84 for
the graphics card geforce 8400m gs.

I searched for the file "awgqdlyk.sys" but couldnt find it in my pc.

I just looked at the log files you mentioned but they are huge and I will
take some time understanding those. I searched for the "awgqdlyk.sys" in
the logs but it could not find it in any log. Any possibility you didnt
misspelled awgqdlyk.sys?

The system has not crashed since more than a day.

Bugcheck IRQL_NOT_LESS_OR_EQUAL has several reasons to be thrown. This
particular instance was caused by a kernel driver dereferencing a null
pointer.

Unfortunately, I don't see an obvious culprit in the crash dump file -
as the binary that dereferenced the pointer is Win32k.sys. In
situations like this, Win3k.sys is most likely the victim of another
kernel driver doing something bad.

To see what kinds of drivers/software you may have recently installed,
you can look at the [%windir%\inf\setupapi.*.log] files.

It appears that you do not have a driver loaded for your display
adapter - but instead are using VGA.sys. Is there a reason for this?

Also, I could not find any information on the kernel driver
awgqdlyk.sys, which is loaded on your machine. You can find this file
in your [%windir%\system32\drivers] folder. You might want to see what
that file is, and where it came from.


Hi Abubakar,

Please upload the crash dump file to the following URL:

https://sftus.one.microsoft.com/choosetransfer.aspx?key=1fa89359-ae3c-444f-8f40-cbd3adb352c8


Please note: This file transfer session will be removed once you
upload the file.

right now i'm on this page:
http://www.microsoft.com/whdc/DevTools/Debugging/symbolpkg.mspx

Hi, Abubakar.

Rick is the expert here, not me. But I think the heart of your
problem is here:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 00000000
BCP2: 0000001B
BCP3: 00000001
BCP4: 83043A7F
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Your "BCCode: a" corresponds to Stop Code 0x0A. My starting point
for researching Stop Codes is:
TROUBLESHOOTING WINDOWS STOP MESSAGES
http://www.aumha.org/a/stop.htm

One of the first listings there is:
0x0000000A: IRQL_NOT_LESS_OR_EQUAL

There are many possible causes and solutions for this error,
"Typically due to a bad driver, or faulty or incompatible hardware or
software."

This should give you some ideas of the kinds of questions Rick will
need you to answer in your next post.

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP
Windows Live Mail 2009 (14.0.8064.0206) in Win7 Ultimate x64 RC 7100


Hi,

The details of the blue screen are crucial to identifying the
problem. Error codes, parameters, and any modules involved can all
provide clues. Check the event log for details and post them.

The second "crash" sounds more like a hardware freeze, not an
operating system issue but rather a problem component. Could also
be related to overheating.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

Hi,

My vista crashed 2 times today. This is probably the first time
since december 2007 when I bought my laptop with Vista. I know the
usual question would be to check if I installed some new drivers
or any hardware device but thats not the case as far as I know.
Its a Vista Ultimate system, with a cor 2 duo 2.ghz, 2gb ram, wifi
etc. The first time it crashed today was with a blue screen with
the usual bsod stuff printed on it (I know it can be different
stuff written there but right now I dont know the exact stuff
other than 'check for new hardware installation' msg). i was
running visual studio 2005 doing asp.net development with it. The
second time when it crashed it hanged and the computer made one
beep sound, but no bsod, the computer just didnt reply, and here
also I was debugging something in asp.net in vs 2k5.

Is there any software that that provide me some information that
may help me find out exactly whats wrong? Some internal diagnostic
software that maybe ships with vista?

regards.



event log is so huge, there r enteries about every second ! And
search was taking time. I will search for more, but after the second
crash the following was displayed when i logged in:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 00000000
BCP2: 0000001B
BCP3: 00000001
BCP4: 83043A7F
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini051409-01.dmp
C:\Users\Ab\AppData\Local\Temp\WER-99450-0.sysdata.xml
C:\Users\Ab\AppData\Local\Temp\WER192A.tmp.version.txt

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

The WER* files are not at there mentioned place, but the dump file
is there. I remember reading someone's blog that the dump file can
be opened with windbg ?

In the meanwhile the system crashed one more time with blue screen.

..ab

 

[Timothy Davis [MSFT]]

Whoa there cowboy - be careful about what your statement implies.

As a Microsoft employee involved in working with the hardware ecosystem on
Win7 readiness, I have access to far more information than the external
FAQs. Keep in mind that it is far easier to publicly state that upgrades
won't be supported when they really are, vs the opposite situation.

I am not saying that upgrades from RC to RTM *will* be supported - I just
happen to know why upgrade was blocked from pre-RC to the RC build. This
reason does not apply from RC to RTM.

 

[Curious]

I totally understand why upgrades from the RC to the RTM will not be
supported and that this it is stated in the following link that they will
not. What I don't understand is why as a MSFT employee you are implying
that they may be.

http://www.microsoft.com/Windows/Windows-7/download.aspx

 

[Abubakar]

I totally understand why upgrades from the RC to the RTM will not be

and I seriously doubt that you *totally understand*, having only read the
faq (for heaven's sake)! He just told you that he has access to far more
*technical* information than you or me. While the upgrade may work perfectly
fine but there are like countless tests after which such a thing is decided,
and in this case Microsoft has not allowed it. There may still be some
undocumented switch (on which of course I'm not counting on) which would
allow it.

I can write a lot here but I decided not to. I just hope you learn something
from this post/thread.

...ab

 

[Curious]

I have read material other then the MS FAQs. I just posted the MS FAQ link
and the MS RC Installation instruction link since these contain the official
MS position and plans for the RTM release.
Both of these stated that you will not be able to upgrade from the RC to the
RTM release and I think a MS employee should not be suggesting this is not
true or that a work around such as the ones being discussed on some sites
may be possible even if the employee knows that they may work especially
when they identify themselves as a MS employees in their post since that
implies that they are speaking for the company.
I would like very much like to be able to upgrade my computer with the RC
release when the RTM release comes out since it would save me a lot of work
without trying to fool the RTM release using one of the kludges I have read
about that will make the RTM release think I have Vista installed and not
the RC.