Interesting Problem

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Namakan
    Senior Member
    • May 2007
    • 2893

    #1

    Interesting Problem

    Twice now, when gaming, my PC shuts locks up and I have to restart it with the power switch.

    I checked the event viewer and this happened at about the same time I lost the PC

    Code:
    Error	9/24/2008 3:57:28 PM	WMI	10	None
    
    
    
    Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

    Anybody have any ideas?


    Can't figure it out


    EDIT: These errors happened two minutes before the above one

    Error 9/24/2008 3:55:52 PM HttpEvent 15016 None
    Unable to initialize the security package Kerberos for server side authentication. The data field contains the error number.
    Error 9/24/2008 3:55:53 PM Eventlog 1101 Event processing

    Audit events have been dropped by the transport. The real time backup file was corrupt due to improper shutdown.

    Error 9/24/2008 3:55:52 PM EventLog 6008 None

    The previous system shutdown at 3:48:44 PM on 9/24/2008 was unexpected.
  • Natt
    Member
    • Oct 2006
    • 593

    #2
    Re: Interesting Problem

    Strangely enough the same thing has happened to my PC, once today and once last week sometime. I'm quite sure the server I was playing on crashed at the same time today.
    I checked Event Viewer and didn't find anything useful.

    Comment

    • Namakan
      Senior Member
      • May 2007
      • 2893

      #3
      Re: Interesting Problem

      Originally posted by Natt
      I'm quite sure the server I was playing on crashed at the same time today.
      It did this once in BF2142 and once in TF2

      Don't think that's it

      Comment

      • Warhawk

        #4
        Re: Interesting Problem

        my PC used to COMPLETETLY lock up while a sound file was constantly repeating itself in the background. I couldn't push any buttons or anything. Updating the BIOS fixed the problem for me, it was a BIOSTAR ge force 6100 mobo

        Comment

        • Namakan
          Senior Member
          • May 2007
          • 2893

          #5
          Re: Interesting Problem

          Originally posted by Warhawk
          my PC used to COMPLETETLY lock up while a sound file was constantly repeating itself in the background. I couldn't push any buttons or anything. Updating the BIOS fixed the problem for me, it was a BIOSTAR ge force 6100 mobo
          That's it! the sounds do loop. My BIOS is updated though

          Comment

          • Warhawk

            #6
            Re: Interesting Problem

            you have all the latest drivers for chipset, etc?

            Also try running a memtest or try running your memory in diferrent slots in single channel instead of dual. maybe even try swapping out some memory if possible.

            Comment

            • Namakan
              Senior Member
              • May 2007
              • 2893

              #7
              Re: Interesting Problem

              Originally posted by Warhawk
              you have all the latest drivers for chipset, etc?

              Also try running a memtest or try running your memory in diferrent slots in single channel instead of dual. maybe even try swapping out some memory if possible.
              All latest drivers


              Just ran mem test for 15 hours and 45 minutes, no errors :yay:

              Comment

              • Warhawk

                #8
                Re: Interesting Problem

                hmm, maybe get it swapped out for a different board? could be defective...

                Comment

                • Namakan
                  Senior Member
                  • May 2007
                  • 2893

                  #9
                  Re: Interesting Problem

                  Originally posted by Warhawk
                  hmm, maybe get it swapped out for a different board? could be defective...
                  Hasn't happened lately, I'll try opening a support ticket with ASUS :)

                  Comment

                  • Namakan
                    Senior Member
                    • May 2007
                    • 2893

                    #10
                    Re: Interesting Problem

                    Sorry to bump, ASUS didn't know


                    I'm desperate for answers

                    Comment

                    • .Gunfire
                      OT Vet.
                      • Jan 2007
                      • 974

                      #11
                      Re: Interesting Problem

                      Have you tried seeing if you could get a replacement?

                      Comment

                      • Namakan
                        Senior Member
                        • May 2007
                        • 2893

                        #12
                        Re: Interesting Problem

                        Originally posted by Gunfire
                        Have you tried seeing if you could get a replacement?
                        They said they'd RMA it but it may not be the board after all. :|:

                        Comment

                        • Busby, Paul (Bicci)

                          #13
                          Re: Interesting Problem

                          if memtest and stress testing (use orthos to test your CPU aswell) has come back with no errors its unlikely to be a faulty motherboard. Try testing your graphics card? download ATI tool and run a check for artifacts

                          Comment

                          • Namakan
                            Senior Member
                            • May 2007
                            • 2893

                            #14
                            Re: Interesting Problem

                            I already did a Prime95 test


                            We found it to be a GPU heat issue last night

                            Comment

                            Working...