I'm getting sick and tired of random BSOD crashes, even when IDLE.

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by TroHax, Mar 14, 2010.

  1. TroHax

    TroHax New Member

    Joined:
    Mar 14, 2010
    Messages:
    8
    Likes Received:
    0
    I don't even remember when this problem started, it's been a while

    My windows, drivers and everything are up to date.

    What pisses me off the most is that this happens when I'm gaming for an extended period of time, I tried monitoring my hardware temperature using my G15 LCD and none of my hardware ever overheats and yet it still crashes. I dunno, maybe it's related and maybe it's not.

    I tried analyzing using WhoCrashed and what I got really didn't help. I would copy pasta it here but for some reason that is not even working.

    note: My pc is 101% virus/trojan/worm free as I scan it and maintain it every day with Avira premium.


    Edit: My computer specs:

    Asus P5Q mobo
    4GB DDR2 1066MHZ ram
    GTX 295 Gfx
    Core 2 quad Q6600 @ 3.6GHZ stable
    500GB Main HDD
    1.5TB Media HDD
     

    Attached Files:

    #1 TroHax, Mar 14, 2010
    Last edited: Mar 14, 2010
  2. Mitchell_A

    Mitchell_A Excellent Member

    Joined:
    Feb 7, 2009
    Messages:
    5,068
    Likes Received:
    240
    Check out the event viewer also and post info about the crashes.
    Start>>"event">>"View Event Logs">>Custom Views>>Admin Events.
     
  3. TroHax

    TroHax New Member

    Joined:
    Mar 14, 2010
    Messages:
    8
    Likes Received:
    0
    Hi.
    I'm sorry, but can you be more specific? I can't find "view event logs".
     
  4. Mitchell_A

    Mitchell_A Excellent Member

    Joined:
    Feb 7, 2009
    Messages:
    5,068
    Likes Received:
    240
    just type it in the search field, it should be in the results. :)
     
  5. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    Do you have any Bluescreen crashes when you are NOT overclocking ?

    I say this because the standard clock speed is stated as | Intel® Core™2 Quad Processor Q6600 (8M Cache, 2.40 GHz, 1066 MHz FSB)

    and windows debugger shows this as a BugCheck 124 which is nearly always a hardware failure ?

    In this instance debugger shows PROCESS_NAME: BFBC2Game.exe at the time of the crash and then your FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS which means your CPU is failing at some level.

    also you have some really old drivers that pre date windows 7 release and need removing or updating
    I suggest remove speedfan and RivaTuner ??
    also these drivers .................
    • LHidFilt.Sys is your Logitech SetPoint(TM) , Logitech HID Filter Driver , as is LMouFilt.Sys your Logitech Mouse Filter Driver
    • AsIO.sys is a driver in ASUS Probe V and is known to cause bluescreen crashes ?

    the big question is do you have any bluescreen crashes when you run at stock speeds ?
     
    #5 ickymay, Mar 14, 2010
    Last edited: Mar 14, 2010
  6. TroHax

    TroHax New Member

    Joined:
    Mar 14, 2010
    Messages:
    8
    Likes Received:
    0
    That's weird. I've had my CPU overclocked for more than 1 year now and I only experienced such bsod crashes with windows 7 and it did not happen for more than 2 months now.
     
    #6 TroHax, Mar 14, 2010
    Last edited: Mar 14, 2010
  7. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    maybe your overclocking has taken it's toll on your CPU and you posted this yesterday ?
     
  8. TroHax

    TroHax New Member

    Joined:
    Mar 14, 2010
    Messages:
    8
    Likes Received:
    0
    I hope not, I really like the performance boost. :(

    I thought this was caused by my drivers or something but since I was too busy with school and work, I left it for a later time. :/
     
  9. Mitchell_A

    Mitchell_A Excellent Member

    Joined:
    Feb 7, 2009
    Messages:
    5,068
    Likes Received:
    240
    Well, we could of course, always underclock the processor, just for a while, to see if it makes a difference. :)
     

Share This Page

Loading...