locked
BSOD when playing old D3D game in Windows 7 Ultimate x32 RRS feed

  • Question

  • I get a bsod error when playing Counter Strike multi-player. It's an old game, it doesn't use too much resources (Core2Duo T8300, 4 GB ram - 3 Gb usable), and I'm playing using the D3D version.

    Problem signature:

      Problem Event Name: BlueScreen

      OS Version: 6.1.7600.2.0.0.256.1

      Locale ID: 1033

     

    Additional information about the problem:

      BCCode: 1e

      BCP1: C000001D

      BCP2: B0614310

      BCP3: 00000000

      BCP4: 00000000

      OS Version: 6_1_7600

      Service Pack: 0_0

      Product: 256_1

    Can anyone help? I have uploaded the dump files to: http://www.angelfire.com/ab7/laci27/101810-35895-01.dmp

    Thank you.

    Monday, October 18, 2010 8:42 AM

Answers

  • IP = instruction pointer (http://en.wikipedia.org/wiki/Program_counter )

    When this is bad, it is a memory (mostly) or CPU issue. 85° are too hot. Clean the CPU cooler.


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Cloud_TS Friday, October 29, 2010 2:17 AM
    Wednesday, October 20, 2010 11:38 AM

All replies

  • KMODE_EXCEPTION_NOT_HANDLED (1e) - This indicates that a kernel-mode program generated an exception which the error handler did not catch.

    http://msdn.microsoft.com/en-us/library/ff557408%28VS.85%29.aspx


    Arguments:
    Arg1: c000001d , The exception code that was not handled

    //
    // MessageId: STATUS_ILLEGAL_INSTRUCTION
    //
    // MessageText:
    //
    // {EXCEPTION}
    // Illegal Instruction
    // An attempt was made to execute an illegal instruction.
    //
    #define STATUS_ILLEGAL_INSTRUCTION       ((NTSTATUS)0xC000001D L)

    0x1E_c000001d_BAD_IP _tcpip!FlReceiveNetBufferListChain+7c = bad instruction pointer.


    So it looks like your RAM is damaged. Please download memtest86+ [1], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [2] to do this), reboot your PC and scan your RAM 4-5hours for errors. If it detects errors, replace the faulty RAM.

    André

    [1] http://www.memtest.org/download/4.10/memtest86+-4.10.iso.zip
    [2] http://www.imgburn.com/index.php?act=download


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Monday, October 18, 2010 4:42 PM
  • Thank you for the answer, my thought was exactly that and I did burn memtest86+ and run it, it didn't detect any errors. You mentioned that it needs to run 4-5 hours, I did the test twice and it finished in about an hour. Does it matter how long it takes (how many times I need to run the test)? 

    I work on the laptop at least 10 hours a day, and the only time it crashes is when I play that particular game. And it doesn't do it after hours of play, just a few minutes into the game when 'something' happens.

    Tuesday, October 19, 2010 1:16 PM
  • Also test your CPU please with Prime95, please.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, October 19, 2010 11:01 PM
  •  I've run the standard Prime95 test for 2 hours and the only alarming thing I found was that some TZ5 sensor detected 100 C. CPU cores where at 85C constantly and no errors detected.

    From the file I've uploaded can you tell if it's a driver, or something else? I mean, are you sure it's a hardware problem somewhere? If yes, in your reply you highlighted BAD_IP, can the fault be from the wireless adapter? How can I test that? 

    Wednesday, October 20, 2010 8:49 AM
  • IP = instruction pointer (http://en.wikipedia.org/wiki/Program_counter )

    When this is bad, it is a memory (mostly) or CPU issue. 85° are too hot. Clean the CPU cooler.


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Cloud_TS Friday, October 29, 2010 2:17 AM
    Wednesday, October 20, 2010 11:38 AM
  • Thank you for your help.
    Thursday, October 21, 2010 6:06 AM