also @ TechSpot: US BitTorrent traffic decline credited to legal alternatives

TechSpot

WinXP with SP2 - BSOD problem (5 minidumbs attached)

Discussion in 'Windows BSOD, Freezing, Restarting Help' started by miluthui, Apr 2, 2006.

Thread Status:
Not open for further replies.
  1. miluthui Newcomer, in training

    Hi I'm new here :p , my comp has been having BSOD and sometimes it suddenly freezes :dead: I have no idea what is wrong with it o__0, I attached 5 minidumb files and did everything u guys wrote here: http://www.techspot.com/vb/topic35103.html

    I think I dont need to post my system's spec as u guys can figure it out in the minidumb. But basically my comp is not very old but not very new either, it's quite a nice comp and nothing is overclocked ^^

    Hope u guys can help me out thanks in advance :)

    Attached Files:

  2. miluthui Newcomer, in training

    I'm starting to suspect my PSU behind all this... it's an unknown brand 450w PSU made in China if u want to know. Hmm btw does this look fine or not ?

    [IMG]
  3. howard_hopkinso Newcomer, in training

    Hello and welcome to Techspot.

    3 minidumps crash with memory corruption and a bugcheck of 0A.

    2 minidumps crash with an unknown image and a bugcheck of D1.

    I believe you may have a ram or possible psu problem.

    Did you complete all the tests in this link HERE?

    If not, I suggest you do so.

    0x0000000A: IRQL_NOT_LESS_OR_EQUAL

    Typically due to a bad driver, or faulty or incompatible hardware or software. . Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)


    0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

    The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by faulty or mismatched RAM, or a damaged pagefile.

    Regards Howard :wave: :wave:
  4. miluthui Newcomer, in training

    Thanks for the reply ^^. Actually I only did the RAM test long time ago :p and the result seemed fine but it's not a deep test though, I might have to test it again

    So a damaged pagefile can cause BSOD and crash too ? whoa this is new to me, I never thought of that. I'll clean the pagefile and create a new one and see how it goes.

    If it's true that the problem is caused by either faulty RAM or bad PSU then there's nothing I can do about it because I'm out of money, I can't afford anything now :(

    Anyway thanks for the help again, here's a cake for u:

    [IMG]

    Sorry couldnt find a better one :p
Thread Status:
Not open for further replies.