Prev: Redirection d'un lien hypertexte vous dit quelque chose ?
Next: Realtek ALC850 audio chipset new drivers
From: Vandervecken on 20 Feb 2010 20:35

The problem is that the dumps don't actually happen! That's what I've been
trying to get help for. The crash happens, but nothing is logged to the
event viewer, and no dumps occur, despite me setting the dump settings so
that they should!

"RCan" wrote:
> It is too complex to explain in a newsgroup how to read that dumps but if
> you anyway want to have a look on your dump file, check the following posts
> if they help you:
> http://thebackroomtech.com/2008/01/31/howto-use-the-windows-debugging-tools-to-analyze-a-crash-dump-bsod/
> http://technet.microsoft.com/en-us/library/cc740105(WS.10).aspx


From: RCan on 21 Feb 2010 16:01
ok - missunderstood you here :-)

Can you please check your system settings :
On Win7 client go to "Control Panel\All Control Panel Items\System" ->
"Advanced System Settings". Then "Advanced" -> "Startup and Recovery" ->
"Settings" -> "System Failure" -> change to "Complete Memory Dump". Remember
the dump location.
+ Also you need to enable your page file in simular size as your physical
RAM in your system. Ideally you leave the automatic setting and let windows
manage this for you.
To enable pagefile again -> "Control Panel\All Control Panel
Items\System" -> "Advanced System Settings" -> "Advanced" ->
"Performance" -> "Advanced" -> "Virtual Memory" -> "Change" -> check
"Automatically ....."

This relies on Windows 7.

PS : there is also a registry key where you can do a "controlled" bluescreen
with a key combination + somethink like "notmyfault.sys" can be used from
sysinternals for producing an dump file.

Hope that helps

Regards
Ramazan

"Vandervecken" <Vandervecken(a)discussions.microsoft.com> wrote in message
news:5D9FF5BD-C3B2-4809-832E-F637267CBEBA(a)microsoft.com...
>
> The problem is that the dumps don't actually happen! That's what I've
> been
> trying to get help for. The crash happens, but nothing is logged to the
> event viewer, and no dumps occur, despite me setting the dump settings so
> that they should!
>
> "RCan" wrote:
>> It is too complex to explain in a newsgroup how to read that dumps but if
>> you anyway want to have a look on your dump file, check the following
>> posts
>> if they help you:
>> http://thebackroomtech.com/2008/01/31/howto-use-the-windows-debugging-tools-to-analyze-a-crash-dump-bsod/
>> http://technet.microsoft.com/en-us/library/cc740105(WS.10).aspx
>
>
From: Vandervecken on 21 Feb 2010 21:08
I am running XP 64 bit.

"RCan" wrote:

> ok - missunderstood you here :-)
>
> Can you please check your system settings :
> On Win7 client go to "Control Panel\All Control Panel Items\System" ->
> "Advanced System Settings". Then "Advanced" -> "Startup and Recovery" ->
> "Settings" -> "System Failure" -> change to "Complete Memory Dump". Remember
> the dump location.
> + Also you need to enable your page file in simular size as your physical
> RAM in your system. Ideally you leave the automatic setting and let windows
> manage this for you.
> To enable pagefile again -> "Control Panel\All Control Panel
> Items\System" -> "Advanced System Settings" -> "Advanced" ->
> "Performance" -> "Advanced" -> "Virtual Memory" -> "Change" -> check
> "Automatically ....."
>
> This relies on Windows 7.
>
> PS : there is also a registry key where you can do a "controlled" bluescreen
> with a key combination + somethink like "notmyfault.sys" can be used from
> sysinternals for producing an dump file.
>
> Hope that helps
>
> Regards
> Ramazan
>
> "Vandervecken" <Vandervecken(a)discussions.microsoft.com> wrote in message
> news:5D9FF5BD-C3B2-4809-832E-F637267CBEBA(a)microsoft.com...
> >
> > The problem is that the dumps don't actually happen! That's what I've
> > been
> > trying to get help for. The crash happens, but nothing is logged to the
> > event viewer, and no dumps occur, despite me setting the dump settings so
> > that they should!
> >
> > "RCan" wrote:
> >> It is too complex to explain in a newsgroup how to read that dumps but if
> >> you anyway want to have a look on your dump file, check the following
> >> posts
> >> if they help you:
> >> http://thebackroomtech.com/2008/01/31/howto-use-the-windows-debugging-tools-to-analyze-a-crash-dump-bsod/
> >> http://technet.microsoft.com/en-us/library/cc740105(WS.10).aspx
> >
> >
> .
>
From: Vandervecken on 23 Feb 2010 00:20
I just had another.
I am running memtest now, but have run it before and found no errors.
Here is the info from the BSOD:

The error is in win32k.sys, PAGE_FAULT_IN_NONPAGED_AREA
STOP 0x00000050 (0xFFFFFA8000928000, 0x0000000000000000, 0xFFFFF97FFF180344,
0x0000000000000000)

win32k.sys - Address FFFFF97FFF180344, base at FFFFF97FFF000000, Datestamp
4a8403c8

Any ideas?

Once again, this is an XP64 system, and I am unable to get minidumps working
to diagnose the problem. This is usually a faulty driver, but I have no idea
which driver, or what is causing it.

"Vandervecken" wrote:

> I am running XP 64 bit.
>
> "RCan" wrote:
>
> > ok - missunderstood you here :-)
> >
> > Can you please check your system settings :
> > On Win7 client go to "Control Panel\All Control Panel Items\System" ->
> > "Advanced System Settings". Then "Advanced" -> "Startup and Recovery" ->
> > "Settings" -> "System Failure" -> change to "Complete Memory Dump". Remember
> > the dump location.
> > + Also you need to enable your page file in simular size as your physical
> > RAM in your system. Ideally you leave the automatic setting and let windows
> > manage this for you.
> > To enable pagefile again -> "Control Panel\All Control Panel
> > Items\System" -> "Advanced System Settings" -> "Advanced" ->
> > "Performance" -> "Advanced" -> "Virtual Memory" -> "Change" -> check
> > "Automatically ....."
> >
> > This relies on Windows 7.
> >
> > PS : there is also a registry key where you can do a "controlled" bluescreen
> > with a key combination + somethink like "notmyfault.sys" can be used from
> > sysinternals for producing an dump file.
> >
> > Hope that helps
> >
> > Regards
> > Ramazan
> >
> > "Vandervecken" <Vandervecken(a)discussions.microsoft.com> wrote in message
> > news:5D9FF5BD-C3B2-4809-832E-F637267CBEBA(a)microsoft.com...
> > >
> > > The problem is that the dumps don't actually happen! That's what I've
> > > been
> > > trying to get help for. The crash happens, but nothing is logged to the
> > > event viewer, and no dumps occur, despite me setting the dump settings so
> > > that they should!
> > >
> > > "RCan" wrote:
> > >> It is too complex to explain in a newsgroup how to read that dumps but if
> > >> you anyway want to have a look on your dump file, check the following
> > >> posts
> > >> if they help you:
> > >> http://thebackroomtech.com/2008/01/31/howto-use-the-windows-debugging-tools-to-analyze-a-crash-dump-bsod/
> > >> http://technet.microsoft.com/en-us/library/cc740105(WS.10).aspx
> > >
> > >
> > .
> >
From: RCan on 24 Feb 2010 14:19
Sorry but the root cause cannot be identified with the provided details here
:-(

Here is also an article for configuring full memory dump on a XP client :
http://support.microsoft.com/kb/316450

Regards
Ramazan

"Vandervecken" <Vandervecken(a)discussions.microsoft.com> wrote in message
news:BEB2E28C-CBBE-42CD-B3EC-75A0261F2F39(a)microsoft.com...
> I just had another.
> I am running memtest now, but have run it before and found no errors.
> Here is the info from the BSOD:
>
> The error is in win32k.sys, PAGE_FAULT_IN_NONPAGED_AREA
> STOP 0x00000050 (0xFFFFFA8000928000, 0x0000000000000000,
> 0xFFFFF97FFF180344,
> 0x0000000000000000)
>
> win32k.sys - Address FFFFF97FFF180344, base at FFFFF97FFF000000, Datestamp
> 4a8403c8
>
> Any ideas?
>
> Once again, this is an XP64 system, and I am unable to get minidumps
> working
> to diagnose the problem. This is usually a faulty driver, but I have no
> idea
> which driver, or what is causing it.
>
> "Vandervecken" wrote:
>
>> I am running XP 64 bit.
>>
>> "RCan" wrote:
>>
>> > ok - missunderstood you here :-)
>> >
>> > Can you please check your system settings :
>> > On Win7 client go to "Control Panel\All Control Panel Items\System" ->
>> > "Advanced System Settings". Then "Advanced" -> "Startup and
>> > Recovery" ->
>> > "Settings" -> "System Failure" -> change to "Complete Memory Dump".
>> > Remember
>> > the dump location.
>> > + Also you need to enable your page file in simular size as your
>> > physical
>> > RAM in your system. Ideally you leave the automatic setting and let
>> > windows
>> > manage this for you.
>> > To enable pagefile again -> "Control Panel\All Control Panel
>> > Items\System" -> "Advanced System Settings" -> "Advanced" ->
>> > "Performance" -> "Advanced" -> "Virtual Memory" -> "Change" -> check
>> > "Automatically ....."
>> >
>> > This relies on Windows 7.
>> >
>> > PS : there is also a registry key where you can do a "controlled"
>> > bluescreen
>> > with a key combination + somethink like "notmyfault.sys" can be used
>> > from
>> > sysinternals for producing an dump file.
>> >
>> > Hope that helps
>> >
>> > Regards
>> > Ramazan
>> >
>> > "Vandervecken" <Vandervecken(a)discussions.microsoft.com> wrote in
>> > message
>> > news:5D9FF5BD-C3B2-4809-832E-F637267CBEBA(a)microsoft.com...
>> > >
>> > > The problem is that the dumps don't actually happen! That's what
>> > > I've
>> > > been
>> > > trying to get help for. The crash happens, but nothing is logged to
>> > > the
>> > > event viewer, and no dumps occur, despite me setting the dump
>> > > settings so
>> > > that they should!
>> > >
>> > > "RCan" wrote:
>> > >> It is too complex to explain in a newsgroup how to read that dumps
>> > >> but if
>> > >> you anyway want to have a look on your dump file, check the
>> > >> following
>> > >> posts
>> > >> if they help you:
>> > >> http://thebackroomtech.com/2008/01/31/howto-use-the-windows-debugging-tools-to-analyze-a-crash-dump-bsod/
>> > >> http://technet.microsoft.com/en-us/library/cc740105(WS.10).aspx
>> > >
>> > >
>> > .
>> >
First  |  Prev  | 
Pages: 1 2
Prev: Redirection d'un lien hypertexte vous dit quelque chose ?
Next: Realtek ALC850 audio chipset new drivers