1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

BSOD & Freezing

Discussion in 'Windows XP' started by zeon101, 2008/02/01.

  1. 2008/02/01
    zeon101

    zeon101 Inactive Thread Starter

    Joined:
    2008/02/01
    Messages:
    5
    Likes Received:
    0
    Hey guys, I really hope you can help me! Yesterday I started having problems with my pc. I was gaming, and all of a sudden the game froze, and forced me to restart the pc. I thought it may have had something to do with the video card/games. But it turns out it, it doesn't. I was browsing the web today and got a bluescreen (twice)! Now, I got the following error code in the BSOD!

    0x1000007f (0x0000000d, 0x00000000, 0x00000000, 0x00000000).

    That was the only information that I could find with specific information. The rest was the usual BSOD info. And looked the exact same as this except the technical info (I posted it above) is different>

    http://www.mulsannescorner.com/images/BSOD-1.jpg


    It happens randomly when I am on the pc. There's no warning! I'd really appreciate your help guys.

    I have the memory dumps uploaded incase you need them guys!

    http://rapidshare.com/files/88365305/Minidump.zip.html

    Thanks guys!
     
  2. 2008/02/01
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    zeon101 - Welcome to the Board :)

    0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

    Both essentially the same .....

    So look in Event Viewer for any info.

    Debug a couple of your Memory Dumps following the instructions here ....

    http://www.windowsbbs.com/showthread.php?t=33471

    A caveat ....
     

  3. to hide this advert.

  4. 2008/02/01
    zeon101

    zeon101 Inactive Thread Starter

    Joined:
    2008/02/01
    Messages:
    5
    Likes Received:
    0
    Thanks for the warm welcome :) and your help :) I'll carry out what you suggested. I'm not the best at troubleshooting lol, this has been the first bluescreen i've had in like 2 years. So, i'm sorry if I can't provide information you guys might ask for.

    I really appreciate your fast response :) and your willingness to help :) Thanks guys! I'll let you know what happens! :)
     
  5. 2008/02/01
    zeon101

    zeon101 Inactive Thread Starter

    Joined:
    2008/02/01
    Messages:
    5
    Likes Received:
    0
    I went into event viewer > System and most of the error messages I had were:

    and I used the debugged some of the minidumps like you said, and found the log file. And this is what was in it:

    Thanks guys, I read up there that it might be something to do with memory corruption? Meaning the RAM perhaps? Is that all that it could be?
     
  6. 2008/02/02
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Start by testing your memory. Run Memtest86 or Windows Memory Diagnostic.

    Please note:

     
    Arie,
    #5
  7. 2008/02/02
    zeon101

    zeon101 Inactive Thread Starter

    Joined:
    2008/02/01
    Messages:
    5
    Likes Received:
    0
    Hey, thanks :eek:

    I tried both of them and they couldn't find any errors... :(
     
  8. 2008/02/02
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    As you will have noted from Arie's quote re. Memory Testers, they are not infallible and passing the 'test' does not mean that you do not have a memory problem.

    The dump log indicates ....
    The best method is to physically change the configuration of the memory. If you have 2 sticks and 4 slots move the sticks to the other pair of slots and test - then run with one stick at a time switching between slots. It's a process of elimination and hopefully something will show up in the course of your testing.
     
  9. 2008/02/02
    zeon101

    zeon101 Inactive Thread Starter

    Joined:
    2008/02/01
    Messages:
    5
    Likes Received:
    0
    thanks ill give it a shot, I hope to god its not the motherboard :(
     
  10. 2008/02/09
    debugnt

    debugnt Inactive

    Joined:
    2004/08/05
    Messages:
    13
    Likes Received:
    0
    Memory corruption can also be caused by fellow device drivers stomping on each others address (memory) space. Your system has a couple of aging antivirus software installed on it and it's highly recommended that you choose 1. AVG seems most up to date on your machine, so I would recommend removing McAfee/Norton.

    ba958000 ba9662a0 mvstdi5x mvstdi5x.sys Fri Aug 20 12:43:55 2004 (4125E3FB) McAfee
    b4913000 b492d6e0 naiavf5x naiavf5x.sys Fri Aug 20 12:42:57 2004 (4125E3C1) Norton

    I'd also recommend some testing by removing the following filter driver.
    bab90000 bab97000 GEARAspiWDM GEARAspiWDM.sys Mon Aug 07 18:11:27 2006 (44D7743F)

    I see this thread is almost a week old, I hope you visit and see the response.

    John
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.