TechSpot

What is wrong with my PC?

By toottoot
Nov 15, 2009
  1. CPU: It is a Pentium 4, 1.8
    Motherboard: Asrock P4S61
    Ram Speed, size and #sticks: DDR 266, 3 sticks for 3 slots (512mb) 1.5 GB total.
    GPU:is this mean graphic card? if so, it ATI 1600
    PSU : Antec 350 watt output
    OS: Windows XP home, SP3


    Hi all, hope you can help me.

    For many months now I would get so many crashes in Firefox. They would happen mostly when I would play a flash game. And you know how flash takes 99% cpu eh? On coreduo or quad would be no prob, but with my computer, kinda sucks, but playable.
    Sometimes utorrent would crash too, once in blue moon...
    And well, I'm getting random reboots as well, which produce a minidump, which is associated with the firefox crashes. I will copy and paste the minidumps here in a minute, just a little more history for y'all.

    Month ago, I reformatted the harddrive, it is a Maxtor 250 GB (IDE). I thought maybe a freshly installed windows would help the crashes. It did not work.

    Just yesterday, I put in a 1 GB stick of DDR 400, to replace the 3 sticks of DDR266.
    The crashes and random reboot still happen.

    I went through the things in the read me, changing aperture to 128, new pagefile, etc. etc.

    I could replace the other hardware but was hoping the minidumps could tell you exactly what it is, and maybe i could narrow it down to 2 things instead of 3 or 4.

    I'll post the latest 2 minidump.



    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 8056795b, a6b4ec7c, 0}

    Probably caused by : ntoskrnl.exe ( nt!PsReturnSharedPoolQuota+58 )

    Followup: MachineOwner
    ---------

    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    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: 8056795b, The address that the exception occurred at
    Arg3: a6b4ec7c, Trap Frame
    Arg4: 00000000

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    FAULTING_IP:
    nt!PsReturnSharedPoolQuota+58
    8056795b 83b9a800000000 cmp dword ptr [ecx+0A8h],0

    TRAP_FRAME: a6b4ec7c -- (.trap 0xffffffffa6b4ec7c)
    ErrCode = 00000000
    eax=e1107018 ebx=89313bf0 ecx=ffffffff edx=e20d9cc0 esi=e20d9cc0 edi=e1107018
    eip=8056795b esp=a6b4ecf0 ebp=a6b4ecfc iopl=0 nv up ei ng nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
    nt!PsReturnSharedPoolQuota+0x58:
    8056795b 83b9a800000000 cmp dword ptr [ecx+0A8h],0 ds:0023:000000a7=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: firefox.exe

    LAST_CONTROL_TRANSFER: from 80567a3f to 8056795b

    STACK_TEXT:
    a6b4ecfc 80567a3f e10694d8 e1107018 0000000c nt!PsReturnSharedPoolQuota+0x58
    a6b4ed44 80567a8a 0000000c 00000001 00000000 nt!PsReturnSharedPoolQuota+0x1da
    a6b4ed58 804de7ec 0000000c 0012e3c4 7c90e514 nt!ExpAllocateHandleTableEntry+0x131
    a6b4ed58 7c90e514 0000000c 0012e3c4 7c90e514 nt!KiFastCallEntry+0xf8
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0012e3c4 00000000 00000000 00000000 00000000 0x7c90e514


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!PsReturnSharedPoolQuota+58
    8056795b 83b9a800000000 cmp dword ptr [ecx+0A8h],0

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!PsReturnSharedPoolQuota+58

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntoskrnl.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a78505a

    FAILURE_BUCKET_ID: 0x8E_nt!PsReturnSharedPoolQuota+58

    BUCKET_ID: 0x8E_nt!PsReturnSharedPoolQuota+58

    Followup: MachineOwner
    ---------

    November 15th:


    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini111509-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\WINDOWS\Symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
    Debug session time: Sun Nov 15 16:23:52.875 2009 (GMT-5)
    System Uptime: 0 days 0:07:34.469
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols

    Unable to load image ati2dvag.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ati2dvag.dll
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 0, a7d5c1ac, 0}

    Probably caused by : ati2dvag.dll ( ati2dvag!FastCopy_DIB8TODFB8+26 )

    Followup: MachineOwner
    ---------

    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    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: 00000000, The address that the exception occurred at
    Arg3: a7d5c1ac, Trap Frame
    Arg4: 00000000

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    FAULTING_IP:
    +26
    00000000 ?? ???

    TRAP_FRAME: a7d5c1ac -- (.trap 0xffffffffa7d5c1ac)
    ErrCode = 00000000
    eax=00000000 ebx=a7d5c7d0 ecx=00000f94 edx=000003e5 esi=e14db080 edi=000007ca
    eip=00000000 esp=a7d5c220 ebp=a7d5c7c0 iopl=0 nv up ei pl nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
    00000000 ?? ???
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: firefox.exe

    LAST_CONTROL_TRANSFER: from bf01ee6a to 00000000

    STACK_TEXT:
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    a7d5c21c bf01ee6a a84540a0 07ab0000 00000f94 0x0
    a7d5c238 00000000 e14db080 00000000 bf85e260 ati2dvag!FastCopy_DIB8TODFB8+0x26


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    ati2dvag!FastCopy_DIB8TODFB8+26
    bf01ee6a ?? ???

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: ati2dvag!FastCopy_DIB8TODFB8+26

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: ati2dvag

    IMAGE_NAME: ati2dvag.dll

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a65e4ad

    FAILURE_BUCKET_ID: 0x8E_ati2dvag!FastCopy_DIB8TODFB8+26

    BUCKET_ID: 0x8E_ati2dvag!FastCopy_DIB8TODFB8+26

    Followup: MachineOwner
    ---------

    Hope you can helps me <3
     
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Your second dump points to the ATI driver ati2dvag.dll

    I suggest doing the following...

    1. Download Driver Cleaner Pro or Driver Sweeper (both have free versions) to your desktop screen and install.

    2. Download the latest diver(s) for your video card but don't install them.

    3. Uninstall your video card drivers and reboot your PC into Safe Mode. Run Driver Cleaner Pro or Driver Sweeper. If it doesn't find any video card drivers that is quite okay.

    4. Reboot and install new video card drivers.


    * The only problem is ATI/AMD no longer support older graphic cards. You may have issues finding the ltest and last released drivers for your card. If you have the installation disk you may want to uninstall and try a fresh install.
     
  3. kimsland

    kimsland Ex-TechSpotter Posts: 14,524

    These old boards with AGP and using an old AGP Video Card can just be faulty hardware
    You can confirm you have the latest Bios Ver2.5 Released 5 years ago (nearly to the day) HERE
    Also, you may as well download: SiS AGP driver ver:1.17 (same link above)

    As well as confirm you using the latest Video drivers from HERE
    But it just may be that your AGP Video card is faulty :(
     
  4. toottoot

    toottoot TS Rookie Topic Starter

    Thank you very much guys for your replies and suggestions.
    I am getting ready for bed in a minute, but will try those things in the morning.

    kimsland: Is it necessary to install the agp driver?(SiS AGP driver ver:1.17) Even though I'm not using onboard video?
    Ya, my Bios was updated years ago, hehe.

    I will follow your instructions tomorrow Route 44.
    If these things do not help, I will take out the ole 9600pro, and try using that for awhile. Will update you all.
    -------------------

    I have a couple questions that came about today while in bios. I took out the 3 sticks of DDR266, cause I thought it might be them right? I put in 1 stick of DDR400(1GB), but in bios it only shows it as DDR333, why is this so?
    In the manual it states that it supports 1GB of DDR400. (1 slot), it's in 1st slot, so i dont think it would make diff in the 2nd or 3rd :p

    Is 1 stick of DDR400 (1GB) better than the 3 sticks of DDR266 (1.5)GB?


    Ok, of I go to bed, I'll update you on my finding and if I need more support


    <3
     
  5. toottoot

    toottoot TS Rookie Topic Starter

    Double post!, Sorry :( please delete this one.
     
  6. kimsland

    kimsland Ex-TechSpotter Posts: 14,524

    Yes 1Gig of a higher speed Ram PC3200 (DDR400) is better than your other much slower Rams PC2100 (DDR266) You can throw them away ;) (or sell them whichever comes first ;))

    Why you Bios reports as 333 when its a 400 I don't know
    Are you sure its a PC3200 (DDR400) Ram card?

    EDIT
    Regarding the "SIS" driver
    Actually I'd uninstall your ATI drivers
    Then Remove the AGP card (you can also blow out the dust whilst you're there - actually the whole computer would be ideal to high compress air blow out)
    Then boot up without the card in (if you don't get Video, then you need to put the card back in, and change Bios to onboard Video, then Save and Exit, then turn off)
    Then (running on the onboard, update the SIS driver
    Then shutdown (also, this time put Bios back to AGP > Save and Exit)
    Then re-fit the AGP card and boot up
    Then update to the latest Video card drivers (drivers only by the way)
    Then test :)
     
  7. toottoot

    toottoot TS Rookie Topic Starter

    Hi :)

    yes, I am completely positive it is DDR400. I have this other computer, and bought a package of 1 GB sticks for it. Only ended up using the RAM for a couple months before the computer went caput. So I basically just use it for parts now. When I did use it, the computer saw it as DDR400's.

    Would it help if I took some pics of bios and posted them here, maybe there is some setting not right.

    I followed your instructions to re install video card drivers. It didn't work out :( I got another reboot/minidump, here it is.



    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini111609-02.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\WINDOWS\Symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
    Debug session time: Mon Nov 16 10:43:49.531 2009 (GMT-5)
    System Uptime: 0 days 0:26:31.116
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ........................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {740b1dd0, 2, 0, 804e92f0}

    Probably caused by : memory_corruption ( nt!MiResolveDemandZeroFault+20 )

    Followup: MachineOwner
    ---------

    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 740b1dd0, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 804e92f0, address which referenced memory

    Debugging Details:
    ------------------


    READ_ADDRESS: 740b1dd0

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!MiResolveDemandZeroFault+20
    804e92f0 8418 test byte ptr [eax],bl

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: firefox.exe

    LAST_CONTROL_TRANSFER: from 804e947d to 804e92f0

    STACK_TEXT:
    a7b8cd04 804e947d 0b1dd000 c002c774 8668c020 nt!MiResolveDemandZeroFault+0x20
    a7b8cd4c 804e1718 00000001 0b1dd000 00000001 nt!MmAccessFault+0x7e8
    a7b8cd4c 7814838a 00000001 0b1dd000 00000001 nt!KiTrap0E+0xcc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    036cfd6c 00000000 00000000 00000000 00000000 0x7814838a


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiResolveDemandZeroFault+20
    804e92f0 8418 test byte ptr [eax],bl

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!MiResolveDemandZeroFault+20

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a78505a

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0xA_nt!MiResolveDemandZeroFault+20

    BUCKET_ID: 0xA_nt!MiResolveDemandZeroFault+20

    Followup: MachineOwner
    ---------
     
  8. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Memory corruption. How does the BIOS recognize your memory?
     
  9. toottoot

    toottoot TS Rookie Topic Starter

  10. toottoot

    toottoot TS Rookie Topic Starter

    it shows the DDR400 as DDR333 , at least it's got the size correct (1GB).

    I bought the DDR400 recently, I also had this stick on another computer, which showed it as a DDR400.
     
  11. toottoot

    toottoot TS Rookie Topic Starter

    I think it's fixed now! no random reboots (BSOD) in past 24 hours.
    Does this make sense?:

    One of the 266 RAM was damaged, I put in 400 but still random reboot.
    I go into BIOS and change the DRAM Frequency setting to 400 from the default setting of AUTO (because was showing it as DDR333. I googled about the 400 RAM not showing up as 400, apparently older motherboards don't always see it correctly or something.)

    Anyways , since I changed it from the default Auto settings to 400, no problems at all.

    I want to thank all who helped guide me through this, it was big help. :)
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...