Various BSOD, at wits end :(

Page 1 of 2 12 LastLast

  1. Posts : 8
    Windows 7 Home Premium x64
       #1

    Various BSOD, at wits end :(


    OK I put my specs in my profile but here is what I have....

    AMD Phenom 9850, ASUS M3A78-EMH HDMI Motherboard, (both bought roughly a year and a half ago) The following items are all brand new. 8G (4x2G) DDR2 800 RAM, NVIDIA GTX 260, ACER GD235HZ, 500W Power supply. Windows 7 HP x64.

    Before buying windows 7 I was getting a few different BSODs under vista x32

    Irql_not_less_or_equal
    Driver Irql_not_less_or_equal
    PFN list or something sorry for not documenting some of these well.
    And a couple others....

    I decided since I bought so many parts and such to upgrade to Windows 7 x64 to utilize all my RAM, and do a clean install because I was going from x32 to x64. I formatted the HD and had A LOT of trouble getting 7 installaion to finish getting BSODs right at completing installation but never actually completing and making me restart the process over and over. Some other BSODs during this process:

    Irql_not_less_or_equal
    Bugcode_?? something I didnt catch it fast enough.

    So randomly don't ask me why I UNPLUGGED the 2 power supply wires from the NVIDIA GTX 260 and plugged the monitor into the built in graphics card on my ASUS MB. Finally windows was able to install. But after it completed some updates I still got BSODs. I tried to use the GTX 260 after windows 7 was installed and it seems I still get BSODs and a couple new ones:

    Maximum_Wait_Objects_Exceeded
    and I get one frequently throughout this whole miserable process that has no "name" its very short some numbers and stuff thats it.

    AFTER spending aroiund 1200 $ in the past 3 weeks and so much frustration I'm going crazy!!! I'm out of money and can't take this thing in to be looked at, can ANYONE help???? Thanks so much to all that reply!!
      My Computer


  2. Posts : 8
    Windows 7 Home Premium x64
    Thread Starter
       #2

    Only have 2 Minidumps cause I just got windows 7 working here is the zipped folder.....
      My Computer


  3. Posts : 28,845
    Win 8 Release candidate 8400
       #3

    PsycoCaptain said:
    OK I put my specs in my profile but here is what I have....

    AMD Phenom 9850, ASUS M3A78-EMH HDMI Motherboard, (both bought roughly a year and a half ago) The following items are all brand new. 8G (4x2G) DDR2 800 RAM, NVIDIA GTX 260, ACER GD235HZ, 500W Power supply. Windows 7 HP x64.

    Before buying windows 7 I was getting a few different BSODs under vista x32

    Irql_not_less_or_equal
    Driver Irql_not_less_or_equal
    PFN list or something sorry for not documenting some of these well.
    And a couple others....

    I decided since I bought so many parts and such to upgrade to Windows 7 x64 to utilize all my RAM, and do a clean install because I was going from x32 to x64. I formatted the HD and had A LOT of trouble getting 7 installaion to finish getting BSODs right at completing installation but never actually completing and making me restart the process over and over. Some other BSODs during this process:

    Irql_not_less_or_equal
    Bugcode_?? something I didnt catch it fast enough.

    So randomly don't ask me why I UNPLUGGED the 2 power supply wires from the NVIDIA GTX 260 and plugged the monitor into the built in graphics card on my ASUS MB. Finally windows was able to install. But after it completed some updates I still got BSODs. I tried to use the GTX 260 after windows 7 was installed and it seems I still get BSODs and a couple new ones:

    Maximum_Wait_Objects_Exceeded
    and I get one frequently throughout this whole miserable process that has no "name" its very short some numbers and stuff thats it.

    AFTER spending aroiund 1200 $ in the past 3 weeks and so much frustration I'm going crazy!!! I'm out of money and can't take this thing in to be looked at, can ANYONE help???? Thanks so much to all that reply!!
    Hi and welcome

    at least two of the three listed causes are memory related. We need the actual dmp file created when the system crashed. use these to find and upload them. https://www.sevenforums.com/crash-loc...d-problem.html

    In the mean time try yanking 4 gigs of ram to see if the problem stops.

    You can also download an app called memtestx86 to test your ram. burn it to cd, and run for at least 5 passes

    When adding memory, even if it appears to be identical, it ISNT. any ram in a package is matched, any other package probably wont match the first.
      My Computer


  4. Posts : 8
    Windows 7 Home Premium x64
    Thread Starter
       #4

    Thanks for replying so quickly. I will do that But I have tried this the reason I have new ram is because I thought my old was bad... The reason half of this stuff is new is because of these blue screens I will aslo try to get the card working again and generally do what I planned and then put up the dumps when I get them.

    O and yes the 2 RAM are OCZ
    and next day I bought the other 2 which are PNY
    but all 4 are 2G DDR2 800 ect ect
      My Computer


  5. Posts : 28,845
    Win 8 Release candidate 8400
       #5

    PsycoCaptain said:
    Thanks for replying so quickly. I will do that But I have tried this the reason I have new ram is because I thought my old was bad... The reason half of this stuff is new is because of these blue screens I will aslo try to get the card working again and generally do what I planned and then put up the dumps when I get them.

    O and yes the 2 RAM are OCZ
    and next day I bought the other 2 which are PNY
    but all 4 are 2G DDR2 800 ect ect
    PC

    I understand what you say. The problem with ram (especially on 64 bit systems) is that if you picked up 2 identical packages of OCZ at the same time in the same place they still might not match and give you BSOD's.

    A prime example of that is the PFN fault. That is almost always caused by mismatched ram.

    Let us know the results and good luck
      My Computer


  6. Posts : 8
    Windows 7 Home Premium x64
    Thread Starter
       #6

    Ok here is the minidump I just got after Plugging the NVIDIA card back in and rebooting, it never got through before until now now but got this first and 2nd boot went through....
      My Computer


  7. Posts : 28,845
    Win 8 Release candidate 8400
       #7

    PsycoCaptain said:
    Ok here is the minidump I just got after Plugging the NVIDIA card back in and rebooting, it never got through before until now now but got this first and 2nd boot went through....
    Doing it now


    This one was caused by peauth.sys part of the win 7 OS.

    since it is an OS file I would run a system file check
    (type cmd in search>right click and run as admin>sfc /scannow)

    Let us know the results

    Also I would download the app memtestx86, burn it to cd, and run it for at least 5 passes to test your ram.

    Let us know if you need help with these

    Ken

    Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

    Code:
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Thu May 27 02:08:22.124 2010 (GMT-4)
    System Uptime: 0 days 0:00:21.434
    BugCheck 50, {fffff88802faf108, 0, fffff88005331ef4, 5}
    *** WARNING: Unable to verify timestamp for peauth.sys
    *** ERROR: Module load completed but symbols could not be loaded for peauth.sys
    Probably caused by : peauth.sys ( peauth+44ef4 )
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
      My Computer


  8. Posts : 8
    Windows 7 Home Premium x64
    Thread Starter
       #8

    Windows Resource Protection did not find any Integrity Violations. Also installed NVIDIA Drivers had to restart when it tells me to, got 3 more blue screens. But I guess they were out of windows cause it did not generate a dump for any of them? One said SYSTEM_SERVICE something... I'm so sorry about all this I think my PC is possessed. ALSO is that a borg cat?? I want one :)
      My Computer


  9. Posts : 8
    Windows 7 Home Premium x64
    Thread Starter
       #9

    Memory testing did not find any errors. I also did the Hard Drive error test from tools in the properties menu(that took forever to run!!!!) No errors. The problem is I have had 8 different ram chips in this rig throughout this process. I have tried many different configurations. Just one chip, 2 chips, 4 chips. I get these errors reguardless. My uncle who has helped me many time before says its probably the motherboard... Its about a year or so old. Can they go bad so quickly? Of course I have none of the original packaging or receipts. I am told 500w is just barely enough, could that cause this? My PC/Windows would warn me if I was low on power wouldn't it?. My GTX 260 has two power connectors both plugged in but there is a MUCH smaller white connector next to those what is that for? I will attach a ZIPPED folder with all the dumps and I made it so it doesn't automatically restart and have started writting down all the info too. Please help me If its hardware I need to replace tell me what I JUST WANT THIS OVER. Thanks again
    Last edited by PsycoCaptain; 29 May 2010 at 02:38.
      My Computer


  10. Posts : 28,845
    Win 8 Release candidate 8400
       #10

    PsycoCaptain said:
    Memory testing did not find any errors. I also did the Hard Drive error test from tools in the properties menu(that took forever to run!!!!) No errors. The problem is I have had 8 different ram chips in this rig throughout this process. I have tried many different configurations. Just one chip, 2 chips, 4 chips. I get these errors reguardless. My uncle who has helped me many time before says its probably the motherboard... Its about a year or so old. Can they go bad so quickly? Of course I have none of the original packaging or receipts. I am told 500w is just barely enough, could that cause this? My PC/Windows would warn me if I was low on power wouldn't it?. My GTX 260 has two power connectors both plugged in but there is a MUCH smaller white connector next to those what is that for? I will attach a ZIPPED folder with all the dumps and I made it so it doesn't automatically restart and have started writting down all the info too. Please help me If its hardware I need to replace tell me what I JUST WANT THIS OVER. Thanks again
    Ok

    Memory testing. what app did you use and for how long did you run it?

    I still suspect the problem is one of mixed ram and till that is resolved you are going to get these random BSOD's

    It could be the ram slotws on the mobo, but since you have purchased additional ram that is much more likely the cause.

    500 watts is barely, ever enough. No your PC would not warn you as there is no mechanism to do so.

    Take a snip of the other white connector, upload it and we can tell you what it is for.

    the DMPS are going to be somewhat vague as you have 5 different causes. I suspect they are all masked memory problems how ever.

    where do you stand on running memtest? how many passes on which chips, in what slots.

    Let us know

    Ken


    Code:
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat May 29 02:51:54.943 2010 (GMT-4)
    System Uptime: 0 days 0:22:39.940
    BugCheck 3B, {c0000096, fffff80002a8b873, fffff88005a24f30, 0}
    Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXSave+70 )
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  iexplore.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat May 29 02:27:29.707 2010 (GMT-4)
    System Uptime: 0 days 1:16:06.315
    BugCheck 1E, {0, 0, 0, 0}
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Fri May 28 07:07:05.378 2010 (GMT-4)
    System Uptime: 0 days 0:01:50.688
    BugCheck A, {fffffa7f91d4e044, 2, 1, fffff80002a8952c}
    Probably caused by : hardware ( nt!KiTimerExpiration+16c )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Fri May 28 07:01:59.786 2010 (GMT-4)
    System Uptime: 0 days 0:04:52.096
    BugCheck 1E, {0, 0, 0, 0}
    Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Fri May 28 06:12:20.182 2010 (GMT-4)
    System Uptime: 0 days 0:02:57.507
    BugCheck A, {fffff880071d45f0, d, 0, fffff80002ac41ce}
    Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd
All times are GMT -5. The time now is 15:27.
Find Us