Close
Showing results 1 to 8 of 8
  1. #1
    Member
    Join Date
    Jun 2008
    Location
    Fremantle, Western Australia
    Posts
    406

    Default Random Crashing & BSOD's

    Looking at the Event Viewer, I am seeing this error on more than one occasion:


    Code:
        - System           
    
        - Provider     
    
    
    [  Name]  Microsoft-Windows-Kernel-Power    
    
    
    [  Guid]  {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
        
    
        
    EventID 41    
    
        
    Version 2    
    
        
    Level 1    
    
        
    Task 63    
    
        
    Opcode 0    
    
        
    Keywords 0x8000000000000002    
    
        - TimeCreated     
    
    
    [  SystemTime]  2010-10-23T00:03:43.452817400Z
        
    
        
    EventRecordID 5790    
    
        
    Correlation    
    
        - Execution     
    
    
    [  ProcessID]  4    
    
    
    [  ThreadID]  8
        
    
        
    Channel System    
    
        
    Computer Admin-PC    
    
        - Security     
    
    
    [  UserID]  S-1-5-18
    
            - EventData           
    
    BugcheckCode 0    
    
    BugcheckParameter1 0x0    
    
    BugcheckParameter2 0x0    
    
    BugcheckParameter3 0x0    
    
    BugcheckParameter4 0x0    
    
    SleepInProgress false    
    
    PowerButtonTimestamp 0



    I am not sure how to figure out what exactly is going wrong.

    Here is a link to my specs with CPU-Z, maybe it can give more information. But something isn't right with my system.

    http://valid.canardpc.com/show_oc.php?id=1444020

    Please let me know if there is more information in which I can provide.

  2. #2

  3. #3
    Member
    Join Date
    Jun 2008
    Location
    Fremantle, Western Australia
    Posts
    406

    Default

    I know that it's not my power supply, seeing as I just replaced mine. And, with a brand new PSU, the same issue still happens.

    But the strange thing, is that it's not happening when I am gaming. It happens more or less, when I am at the desktop.

  4. #4
    Member
    Join Date
    Jul 2008
    Location
    In a van, down by the river.
    Posts
    754
    Blog Entries
    1

    Default

    Could it possibly be a heat issue? I recently replaced an older HD for example, with a newer one, and even though it had a fan going, when I closed my case up, it ran fine for about an hour then overheated.

    I opened the case back up, re did my wiring, and everything seems fine now.

    Outside of that, you might try checking the sleep settings, and possibly, the USB settings. Windows 7 has a thing that will turn on and off USB ports, unless you tell it not to.

    Just a few ideas off the top of my head. hope you get it up and running though.

    Stephen logs off humming Bruces Philosophy song now.
    "You cannot exaggerate about the Marines. They are convinced to the
    point of arrogance, that they are the most ferocious fighters on earth
    - and the amusing thing about it is that they are."- Father Kevin
    Keaney, Chaplain, Korean War

  5. #5

    Default

    Quote Originally Posted by F9thRet View Post
    Could it possibly be a heat issue? I recently replaced an older HD for example, with a newer one, and even though it had a fan going, when I closed my case up, it ran fine for about an hour then overheated.

    I opened the case back up, re did my wiring, and everything seems fine now.

    Outside of that, you might try checking the sleep settings, and possibly, the USB settings. Windows 7 has a thing that will turn on and off USB ports, unless you tell it not to.

    Just a few ideas off the top of my head. hope you get it up and running though.

    Stephen logs off humming Bruces Philosophy song now.
    Quote Originally Posted by Vociferate View Post
    I know that it's not my power supply, seeing as I just replaced mine. And, with a brand new PSU, the same issue still happens.

    But the strange thing, is that it's not happening when I am gaming. It happens more or less, when I am at the desktop.
    If it was heat related you'd think it'd happen under the highest relative load - while gaming. That's not happening.
    Hardware Lurker

  6. #6
    Member
    Join Date
    Jun 2008
    Location
    Fremantle, Western Australia
    Posts
    406

    Default

    I'll need to take a loot at the USB Settings, but I just can't figure out why Windows 7 would do this sort of shit.

    It's still years ahead of Vista, but BSOD's of this nature just simply shouldn't happen.

  7. #7
    Multiboxologist MiRai's Avatar
    Join Date
    Apr 2009
    Location
    Winter Is Coming
    Posts
    6815

    Default

    I may be missing something in the your initial post but what is the actual blue screen error? If you change your settings to not
    immediately reboot upon a blue screen then you can actually see what the error is and Google it. I'll be honest I really don't know
    what I'm looking at in those pictures in your original post or how they can help. More often than not blue screens are caused by
    hardware (bad drivers, overheating, etc.), of course they can be caused by software as well but it is less likely (as far as I have seen
    throughout my years.)

  8. #8

    Default

    does amd have power saving features on their processors? Perhaps when at desktop, the power saving kicks in and causes a bsod. another thing that comes to mind is a sleep/hibernation problem. A bad driver/program install or a incompatible driver/program was installed and causing the issue.

    what is your cpu termination set at? save your bios settings or write them down and up the vcore or cpu termination a little and retest with whatever overclocking program you use. Do you remember if you recently installed a program or driver? also try going to safe mode and see if it crashes, to get to safe mode push F8 before you see the windows boot logo. Choose safe mode or safe mode with networking, this way no programs/drivers get loaded unless they are required windows files.

    When I was having bsod with my intel system, it was a combination of bad O'C settings, and a faulty motherboard.

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •