TechSpot

HELP $$ Will Paypal You $25 ... Page Fault Error BSOD !!!

By I_Love_my_BSOD
Aug 28, 2006
Topic Status:
Not open for further replies.
  1. Hello everyone,

    This board rocks for getting bugs figured out.

    I want to send $25 to the first person that can help me to *correctly* indentify what the problem is. I'll send it to your paypal right away.

    Here's the deal. I built a new computer with the following specs:

    ASUS K8N-DL mobo
    2 x AMD Opteron 265
    4 x 1G Corsair XMS3200R 1024MB 3.3.3.8
    4 x WD Raptor 10k 36Gig Drives in RAID 0
    XFX Extreme Edition Geforce 7950 GX2
    Antec TruePower Trio 650 PSU
    XP Pro SP2 Version: 6.0.2900.2180.xpsp_sp2_gdr.050301-1519
    4 massive fans keeping it cool. Even does it with the sides off. It seems to happen when I make a query on the computer.

    I get a Page Fault on non paged area BSOD referencing FastFat.sys.

    I have attached 10 minidumps. If someone can let me know what the problem is, I'll make a donation to their paypal for 25 bucks.

    Im going nuts over here trying to figure this out, and I need to get back work.

    I just built this computer from scratch. Could it possilble that some the parts arent compatible?

    I have removed the ram and I'm testing one module at a time. So far 3 of them in slot 1 have failed.

    Thanks so much.
     
  2. JMMD

    JMMD TechSpot Chancellor Posts: 1,177

  3. I_Love_my_BSOD

    I_Love_my_BSOD TS Rookie Topic Starter

    Thanks, Im reading those now.

    I also decrypted my .dmp files for review. Can someone let me know what is the problem?



    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 804fe385, The address that the exception occurred at
    Arg3: 8a36bb5c, Trap Frame
    Arg4: 00000000


    ---------------------------


    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 804fe385, The address that the exception occurred at
    Arg3: 89b60404, Trap Frame
    Arg4: 00000000

    Debugging Details:


    ---------------------------

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffffc, memory referenced.
    Arg2: 00000001, value 0 = read operation, 1 = write operation.
    Arg3: ae687447, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 00000000, (reserved)

    Debugging Details:



    ----------------------------


    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 804fe385, The address that the exception occurred at
    Arg3: 8a36bb5c, Trap Frame
    Arg4: 00000000

    Debugging Details:


    -------------------------------


    That was just the tops of them. All of them are viewable in attachment.

    Thanks
     
  4. Skaarj Warrior

    Skaarj Warrior TS Rookie

    I see that you've got some corsair memory with some fairly tight timings.
    Have you adjusted your VDIMM voltage to Corair's recommended setting?
    Don't rely on the Auto setting to do this, it probably wont.
    I've just wasted 3 days of my life trying to install XP, with much the same BSODs that you've experienced. MS Knowledge Base is a complete waste of time. I didn't discover the VDIMM setting until a flashed a new BIOS.
    Hope thta helps.
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.