Jump to content

Blightmare

Member
  • Posts

    9,624
  • Joined

  • Last visited

Posts posted by Blightmare

  1. Well, idunno about a culture of it but a 'trap' is a (often rude, depending on the individual in question) term for a crossdressing male or transgender female. It's mostly something found in manga and anime but not limited to it by any means, unless he's talking about a different kind of trap. But I do kinda agree with him; I'm in favor of not going there. That word is often used in a heavy fetish sense and some people get very angry over that fact. I believe it's a rather disrespectful term because it implies deceit as motive instead of embracing one's self.

  2. I'm at that stage where my steam library is so large I'm finding games I didn't know I had. I'm guessing those are from game packs I got for like 2 games but had a few others in it. Becuase i distinctly know I never bought or was gifted Dungeon Defenders yet there it is.

  3. Well, he's certainly one of the only people who can use genitalia jokes in excess and still make me laugh so there's that. :P It's just first impression of this guy I see from a lot of people I show is "haha- wait, what?"

     

    OT: Tired and wired. Physically I'm exhausted and would love to go to sleep. Mentally, well... Mile a minute. The root of my insomnia.

  4. It's not rude. You have every right to call him that cuz that's what he is. :P

     

    OT: Playing Starcraft II: Legacy of the Void. The game being fun aside, these achievement names are great. "Warp Tour" "massive Aggressive" "World of Warpcraft" "In Living Khala" and, of course, "Shadow of the Colossus"

     

    Seriously though. Being able to drop down a pylon anywhere then instantly warp an army onto it makes me feel like a GOD.

     

    Edit: forgot one. "Sprinter Cell" love it.

  5. Playing Bloodborne. Just got the Platinum trophy. :o

     

    Also I was convinced that the Bloodletting Beast I fought was the easy first encounter most bosses usually have. Nope. That was the hard one. I skipped over the easy one apparently. I feel oddly proud of myself. I'm now convinced the next time i fight him won't go as smoothly. Serious case of beginners luck?

  6. Ah, DNS trouble. I uh... don't really now anything about those. :( In fact, despite dealing with internet trouble for 7 years I know a surprisingly small amount...

     

    OT: Slightly amused and slightly annoyed. Amused because yay more Youtube drama and annoyed because the subject is basically a big name (Syndicate Project) effectively saying "Fuck animators" and ridiculing someone who did an animation for him who simply wanted some credit.

     

    Like seriously, Syndicate? Who cares how popular you are, there's never any amount of subscribers you can get before it's suddenly okay to be a little shit like that.

  7. Gfx drivers don't affect internet tho. O_o

     

    Sure you're not just having internet trouble in general? Try right clicking the connection icon on the lower right when it goes down and then Troubleshoot problems. Sometimes my wireless spazzes out even when the internet is working and that usually fixes it. Assuming that's the case.

  8. Uploading some Bloodborne boss fights.

     

    Apparently, all the bosses people have trouble with are easy for me and all the fights that everyone does on their first try kick my ass. I think my play style is drastically different than most people. O_o

     

    Edit:

    63Xxl1yEVCk

  9. No, after 5 minutes of idling it stops displaying people as online even if they don't close the window. All that shows is basically who navigated anywhere on the forums in the last 5 minutes.

     

    Forums tend to look less active the smaller that window is too.

  10. Is it doing this even when the game isn't running, and if so, does it happen only after the game is launched once or will it happen any time after the computer is started. Trying to rule out if it's a software related issue or an ill-timed hardware issue.

     

    Also if you want a really detailed report on what's causing it, you can follow this unfortunately lengthy process.

     

     

    Assuming you decide to do this, the next time it crashes I want you to look into a few things next run. This is kinda lengthy but should get the most accurate cause of crash(helped me pinpoint my faulty GPU when nothing else could):

     

    First things first, make sure your computer is set to create minidumps on crash: http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/

     

    Next, go into the event viewer (can be found with search) and check if the crash logged any critical errors. If you don't see anything beyond a kernal event 41(improper shutdown) then one other option may help but requires downloads. One would be windows debugging tools:

    https://msdn.microsoft.com/en-us/library/windows/hardware/ff551063(v=vs.85).aspx

    (Put in code because it isn't linking properly. Also sorry for the generic link, it's been a while since I installed this and don't clearly remember the steps, i just know i started here) or for an easier

     

    For a very slightly less accurate view, use Bluescreenview: http://www.nirsoft.net/utils/blue_screen_view.html

     

    The purpose of these is to find what triggered the bluescreen which helps in finding the source. I recommend the WinDbg because of it's slightly more detailed report but it's kind of a hassle to set up, which is why I recommend bluescreenview.

     

    Now after that, there's 2 folders to look for, both under c:\Windows:

     

    Check if there's a minidump folder and a LivekernelReports. Both of these will contain .dmp files which windows SHOULD create in the event of a bluescreen. You need the above programs to read them.

     

    Like me, you're probably not gonna be able to understand most of it, for example(WinDbg, after !analyze -v command):

     

    FAULTING_IP: 
    atikmpag+b848
    fffff880`04b71848 ??              ???
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
    
    TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b
    
    
    BUGCHECK_STR:  0x117
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`05beb350 fffff880`04a875f7 : fffffa80`18afb010 fffff8a0`1d40599c fffff8a0`1d4e6191 fffff880`04a8733c : watchdog!WdDbgReportRecreate+0xa3
    fffff880`05beb870 fffff880`04a88075 : fffff8a0`1d55cffc fffff8a0`14556390 fffff8a0`1d40599c 00000000`00157660 : dxgkrnl!TdrUpdateDbgReport+0xcb
    fffff880`05beb8c0 fffff880`04a88ce2 : fffffa80`18afb010 fffffa80`18afb010 fffffa80`17b9c010 fffffa80`173e5010 : dxgkrnl!TdrCollectDbgInfoStage1+0x92d
    fffff880`05beb960 fffff880`04b2ff07 : fffffa80`18afb010 00000000`00000000 fffffa80`17b9c010 fffffa80`173e5010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
    fffff880`05beb990 fffff880`04b5dd5a : fffffa80`ffffffff 00000000`004632ee fffff880`05bebaf0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`05beba70 fffff880`04b2b29e : fffffa80`173e5010 ffffffff`feced300 fffffa80`1310d010 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
    fffff880`05bebab0 fffff880`04b57e7a : 00000000`00000000 fffffa80`1310d010 00000000`00000080 fffffa80`173e5010 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
    fffff880`05bebbc0 fffff800`0312d32e : 00000000`064dec4d fffffa80`173ea210 fffffa80`12d5d9e0 fffffa80`173ea210 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`05bebc00 fffff800`02e82666 : fffff800`03003e80 fffffa80`173ea210 fffff800`03011cc0 fffff880`01231384 : nt!PspSystemThreadStartup+0x5a
    fffff880`05bebc40 00000000`00000000 : fffff880`05bec000 fffff880`05be6000 fffff880`06ce6a30 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+b848
    fffff880`04b71848 ??              ???
    
    SYMBOL_NAME:  atikmpag+b848
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  546e9eb6
    
    FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys
    
    BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys
    
    Followup: MachineOwner
    

     

    Mostly you just want to look for BUGCHECK_STR and DEFAULT_BUCKET_ID

     

     

    This will tell you as close to what's causing it as possible from the user end but it won't lead to a fix on it's own, so it's up to you. If you really don't want to go through all that, at least follow the steps up to getting the .dmp file and upload it so I can take a look at it. I can't guarantee a fix but I can hopefully find what's causing the problem.

×
×
  • Create New...

This website uses cookies, as do most websites since the 90s. By using this site, you consent to cookies. We have to say this or we get in trouble. Learn more.