Got a BSOD today

Discussion in 'iMac' started by KrrSplat, May 18, 2011.

  1. KrrSplat macrumors member

    Apr 16, 2009
    Long story short, tried playing BFBC2 and got a BSOD, iMac restarted, tried playing again, got BSOD. Repeat above process, happened agan. Disconnected firewire 800 exteral drive, tried playing BFBC2, got BSOD. Disconnected HDPVR, havent tried playing BFBC2 has not BSOD me yet. Only seems to hppen when i try to play BFBC2. Yes my GPU is OC, however this is the first time it acted funny. Also, this is the first time i tried using my computer with the Firewire and HDPVR connected. I'm goin to try to play some BFBC2 hopefully no BSOD.
  2. mrfoof82 macrumors 6502a

    May 26, 2010
    Lawton, OK
    Post the full STOP error (the entire line, which starts with a hexadecimal error code), and the error itself (this is the line before the "If this is the first time you've seen this stop error screen...").

    Basically, we want all of the stuff in red except the giant paragraph:
  3. KrrSplat thread starter macrumors member

    Apr 16, 2009
    Windows did not give my the first red box.
    Technical information:
    *** STOP: 0x00000050 (0xFFFFF3000A167010,0x0000000000000001,

    Thats all of the info i got. Anyways, after i unplugged my HDPVR, no more BSOD :) I do think it is weird that USB still causes problems.
  4. mrfoof82, May 18, 2011
    Last edited: May 18, 2011

    mrfoof82 macrumors 6502a

    May 26, 2010
    Lawton, OK
    So 0x50 is a page fault in a non-paged area. There's some additional info.
    • 0xFFFFF3000A167010: The address that caused the fault.
    • 1: This indicates it was a write operation (0 indicates a read).
    So what happened is some device was trying to write to an address of a page in memory that was no longer allocated. Usually this is the result of (most likely to least likely):

    • Buggy device drivers.
    • Buggy system service.
    • Anti-virus software.
    • Corrupted NTFS volume.
    • Faulty memory.
    Your case looks like #1, buggy device drivers.

    See if the HDPVR not being connected resolves the issue. If so, hook it up again and see if it recurs. If it does recur, check for updated drivers. If they don't exist, report the issue to the HDPVR manufacturer (I assume this is Hauppauge?) and they'll probably assist you in getting more information so they can address the problem in a driver update.

    If you can get the "this problem seems to be caused by the following file" line, it'll pinpoint the driver that's trying to write to memory addresses that it shouldn't be writing to. This is an extremely useful piece of information, as it'll identify what is probably an offending filter driver which is either written by Hauppauge, or could be something else that's causing the problem to manifest.

Share This Page