Re: Vista crashing, I need a way to know whats wrong
- From: "Abubakar" <noemail@xxxxxxxxxxx>
- Date: Sat, 16 May 2009 15:20:50 +0900
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.
"Frank Holman" <holmanf@xxxxxxxxxxxx> wrote in message news:0nfr055mrkcdv4rui0j75hpn78eetvgtil@xxxxxxxxxx
"Abubakar" <noemail@xxxxxxxxxxx> wrote:
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?
"Rick Rogers" <rick@xxxxxxxx> wrote in message
news:ehK6LPU1JHA.5684@xxxxxxxxxxxxxxxxxxxxxxx
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
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com
"Timothy Davis [MSFT]" <tidavis@xxxxxxxxxxxxx> wrote in message
news:e7718ZS1JHA.6056@xxxxxxxxxxxxxxxxxxxxxxx
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.
"Timothy Davis [MSFT]" <tidavis@xxxxxxxxxxxxx> wrote in message
news:02554C2D-C66B-48F6-9C1A-C259E0C7F8E3@xxxxxxxxxxxxxxxx
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.
"Abubakar" <noemail@xxxxxxxxxxx> wrote in message
news:eTZbHHL1JHA.140@xxxxxxxxxxxxxxxxxxxxxxx
right now i'm on this page:
http://www.microsoft.com/whdc/DevTools/Debugging/symbolpkg.mspx
"R. C. White" <rc@xxxxxxxxxxxxx> wrote in message
news:E7F22AF9-EB44-44FB-BECB-A4A8EF2E8D03@xxxxxxxxxxxxxxxx
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
rc@xxxxxxxxxxxxx
Microsoft Windows MVP
Windows Live Mail 2009 (14.0.8064.0206) in Win7 Ultimate x64 RC 7100
"Abubakar" <noemail@xxxxxxxxxxx> wrote in message
news:#BWe02J1JHA.2656@xxxxxxxxxxxxxxxxxxxxxxx
"Rick Rogers" <rick@xxxxxxxx> wrote in message
news:uZBiv5H1JHA.4632@xxxxxxxxxxxxxxxxxxxxxxx
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
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com
"Abubakar" <noemail@xxxxxxxxxxx> wrote in message
news:%23x3gRDF1JHA.140@xxxxxxxxxxxxxxxxxxxxxxx
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
.
- References:
- Vista crashing, I need a way to know whats wrong
- From: Abubakar
- Re: Vista crashing, I need a way to know whats wrong
- From: Abubakar
- Re: Vista crashing, I need a way to know whats wrong
- From: R. C. White
- Re: Vista crashing, I need a way to know whats wrong
- From: Abubakar
- Re: Vista crashing, I need a way to know whats wrong
- From: Timothy Davis [MSFT]
- Re: Vista crashing, I need a way to know whats wrong
- From: Timothy Davis [MSFT]
- Re: Vista crashing, I need a way to know whats wrong
- From: Rick Rogers
- Re: Vista crashing, I need a way to know whats wrong
- From: Frank Holman
- Vista crashing, I need a way to know whats wrong
- Prev by Date: Mass Storage Controller Driver
- Next by Date: Vista 64-bit
- Previous by thread: Re: Vista crashing, I need a way to know whats wrong
- Next by thread: Vista laptop stop detecting usb mouses
- Index(es):
Relevant Pages
|
Loading