locked
Blue screen(s) in Windows 7 Professional (64 bit) RRS feed

  • Question

  • So, I'm having some difficulty with periodic blue screens in Windows 7 Professional (64 bit).  I'm currently running Version 6.1.7600 Build 7600.

    I'm seeing errors periodically, but not in a 100% reproducible manner.  The only real common factor I can see is that it tends to be brought on in 3D graphic applications(like Heroes of Newerth and World of Warcraft).

    Some of the errors I'm receiving are as follows:

    Bug Check String  : KMODE_EXCEPTION_NOT_HANDLED
    Bug Check Code    : 0x0000001e
    Parameter 1       : 00000000`00000000
    Parameter 2       : 00000000`00000000
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ndis.sys
    Caused By Address : ndis.sys+2af4

    Bug Check String  : MEMORY_MANAGEMENT
    Bug Check Code    : 0x0000001a
    Parameter 1       : 00000000`00041790
    Parameter 2       : fffffa80`057743d0
    Parameter 3       : 00000000`0000ffff
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+70740

    Bug Check String  : SYSTEM_SERVICE_EXCEPTION
    Bug Check Code    : 0x0000003b
    Parameter 1       : 00000000`c0000005
    Parameter 2       : fffff880`05af7f66
    Parameter 3       : fffff880`082caf70
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ks.sys
    Caused By Address : ks.sys+19f66

    I've run this machine through the wringer(reinstalling the OS, updating BIOS, video card drivers, switching antivirus solutions, changing memory configurations, etc.).  Nothing seems to touch it.  The only hardware I didn't personally pick out was the power supply, but it should supposedly be rated for well above this machine's capacity...

    I can pull whatever logs might assist, but I'm really starting to suspect something like a memory incompatibility with the motherboard, or an issue with a piece of hardware(like the power supply I mentioned earlier).  It's concerning me that the examples above are Windows system files, not third party drivers.  I haven't reinstalled the OS since early in the process, think it's worth another shot?

    Anyone have thoughts about what might be causing my grief? 

    Thanks for reading!

    Monday, February 7, 2011 6:36 AM

Answers

  • Just a thought, have you try running memtest or windows memory diagnostic since you mention you suspect it could be due to memory? Btw you mention while you play WOW & HON, it tends to have the blue screen and error? What happen if you're not gaming, do you encounter blue screem and error as well?

     

    • Proposed as answer by Andre.Ziegler Monday, February 7, 2011 1:21 PM
    • Marked as answer by Daniel HoEditor Sunday, February 13, 2011 4:06 AM
    Monday, February 7, 2011 7:01 AM
    Answerer

All replies

  • Just a thought, have you try running memtest or windows memory diagnostic since you mention you suspect it could be due to memory? Btw you mention while you play WOW & HON, it tends to have the blue screen and error? What happen if you're not gaming, do you encounter blue screem and error as well?

     

    • Proposed as answer by Andre.Ziegler Monday, February 7, 2011 1:21 PM
    • Marked as answer by Daniel HoEditor Sunday, February 13, 2011 4:06 AM
    Monday, February 7, 2011 7:01 AM
    Answerer
  • this is a RAM error:

    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 00041790, The subtype of the bugcheck.


        The 41790 code is part of our an internal memory manager code but the bugcheck in my experience has almost always indicated hardware issues (RAM errors).

        Source:
        http://social.technet.microsoft.com/Forums/en-US/w7itproperf/thread/68407ce1-7491-4aee-bdef-5ff4bbc56d99/#11ce9f45-7906-4652-9619-a3ad457a87e9


    If the memtest tells no error, please download CPU-Z [1], look in the memory and SPD tab and verify that the current RAM Speed and the Timings match to the values that you see in the SPD tab. If your RAM run at CR (Command Rate) 1T, change the value into 2T in the BIOS. This should fix the crashes.

    André


    [1] http://www.cpuid.com/softwares/cpu-z.html


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Monday, February 7, 2011 1:22 PM