Various BSODs

  1. #1

    Various BSODs

    Greetings,

    I recently upgraded my computerand installed a fresh copy of Windows XP Professional SP2. I am running an Asus A8N-SLI Deluxe mobo, with an AMD Athlon 64 3800+ processor. I have 1GB DDR3200 Kingston RAM (KVR400/1GR, 1GB PC3200 CL3 184-pin DIMM). I also have an ATI PCI-Express X300SE 128MB video card.

    Unfortunately I am getting various BSODs quite frequently, but at random times. Mostly PAGE_FAULT_IN_NONPAGED_AREA with Win32k.sys being the culprit. I have already parsed through several of the minidumps, which I have attached for your enjoyment :-)...I have more if you'd like!

    Thanks in advance,

    --Jay
    Attached Files


  2. #2
    PS. I have already updated all of my drivers (chipset, graphics card, Ethernet controllers (both of em!), windowsupdate) to the latest version available, but to no avail.

  3. #3
    jephree is offline ¨*·.¸ «.·°·..·°·.» ¸.·*¨
    Welcome to D-A-L

    Will get this analysed asap.

  4. #4
    joehobart is offline Junior Member
    The first dump: PAGE_FAULT_IN_NONPAGED_AREA (50)
    probably caused by memory corruption, i couldnt find the bitflip, but i didnt work hard at it.
    You need to take a look at your memory hardware, this may be the result of corruption from another driver, but not very likely.

    Second dump: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
    Nice, the NX feature in your AMD proc caught TPkd.sys trying to execute memory it shouldnt have. TPkd.sys Tue Apr 16 14:31:04 2002
    Youll need to update that driver or remove it.

    Third dump: PAGE_FAULT_IN_NONPAGED_AREA (50)
    Looks like something bad happened here, the graphics subsystem is trying to lookup who to send this message to, but hes either not there, or the address he passed in is bogus.
    Not much to do with this except to say that it happened.

  5. #5
    Thanks for the info. I've looked into the TPkd.sys error, and it looks like others have run into it as well (see http://www.digimation.com/forums/ind...topic=737.new).

    I actually tried to disable DEP earlier by setting my boot option to "/noexecute", but when I do my computer won't boot 75% of the time, giving me a "services.exe failed to initialize properly", or a "lsass.exe failed to initialize properly" error, leaving me with a windows background and little else.

    Although I am apreciative of the protection DEP gives me, I would actually prefer to disable it, as I'd rather be without BSODs but run the risk of a corrupting virus or program. Any thoughts on why disabling DEP would cause such errors?

    Also, I'm considering returning my memory and purchasing a more compatible brand/model. Would you confirm that consideration or recommend pursuing less drastic measures first?

    Also, any recommended course of action to resolve the third BSOD?

    Thanks as always.

    --Jay

  6. #6
    joehobart is offline Junior Member
    havent seen dep disable make things worse, but for the record, DEP is a good thing, even though it can "cause" crashes. It would not be prudent to disable it rather than identifying and fixing the malfunctioning software.

    Taking the memory back is probably a wise choice at this point

    if i had a recommendation, i wouldnt have held back.

+ Reply to Thread