Constant bluescreens after new build

Page 1 of 2 12 LastLast

  1. Posts : 10
    Windows 7 Professional x64
       #1

    Constant bluescreens after new build


    - Win7 Pro x64
    - Not the original installed OS on the system (XP then 7 Pro 32-bit)
    - Full retail version (burned ISO from university's ELMS MSDNAA program)

    - Age of system (hardware): hard drives, DVD drive, case, speakers, keyboard (4 years), monitor (2 years), mouse (1 year), else (2 months)
    - Age of OS installation: 2 months

    I built a new computer about a 2 months ago and at first it wouldn't even start up, but now it's at the point where I just get many blue screens every day.

    Sometimes it crashes when I'm in a game or Firefox, but sometimes it's immediately after startup just on the desktop. The most common are 0x0000001e and 0x0000003b (atikmdag.sys/atikmpag.sys). Ususally the screen has graphical corruption just before the BSoD. I tried uninstalling Catalyst Control Center and reseating the GPU, but it didn't help.

    After some stress testing:
    Video Card: Min 32°C, Max 53°C
    CPU: Min 19°C, Max 33°C
    Primary hard drive: Min 34°C, Max 35°C
    Motherboard: Min 29°C, Max 43°C

    I tried getting Debugging Tools for Windows (x64) but I really don't know what the information it provides means. I ran Windows Memory Diagnostic for 7 passes on Extended and it showed no errors until I cancelled it, at which point it said Windows failed to start and recommened Startup Repair. When I logged in it gave an error message:
    regsvr32.exe - Ordinal Not Found
    The ordinal 344 could not be located in the dynamic link library COMCTL32.dll.

    I have a feeling it could be the video card, RAM, or wireless card, but don't know what to do about it. Any help would be appreciated.
    Last edited by GeoDuck; 12 May 2011 at 01:51.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    GeoDuck said:
    - Win7 Pro x64
    - Not the original installed OS on the system? (XP then 7 Pro 32-bit)
    - Full retail version (burned ISO from university's ELMS MSDNAA program)

    - Age of system (hardware): hard drives, DVD drive, case, speakers, keyboard (4 years), monitor (2 years), mouse (1 year), else (2 months)
    - Age of OS installation: 2 months

    I built a new computer about a 2 months ago and at first it wouldn't even start up, but now it's at the point where I just get many blue screens every day.

    Sometimes it crashes when I'm in a game or Firefox, but sometimes it's immediately after startup just on the desktop. The most common are 0x0000001e and 0x0000003b (atikmdag.sys/atikmpag.sys). Ususally the screen has graphical corruption just before the BSoD. I tried uninstalling Catalyst Control Center and reseating the GPU, but it didn't help.

    After some stress testing:
    Video Card: Min 32°C, Max 53°C
    CPU: Min 19°C, Max 33°C
    Primary hard drive: Min 34°C, Max 35°C
    Motherboard: Min 29°C, Max 43°C

    I tried getting Debugging Tools for Windows (x64) but I really don't know what the information it provides means. I ran Windows Memory Diagnostic for 7 passes on Extended and it showed no errors until I cancelled it, at which point it said Windows failed to start and recommened Startup Repair. When I logged in it gave an error message:
    regsvr32.exe - Ordinal Not Found
    The ordinal 344 could not be located in the dynamic link library COMCTL32.dll.

    I have a feeling it could be the video card, RAM, or wireless card, but don't know what to do about it. Any help would be appreciated.

    The majority of these were Related to cFos_Software Internet acceleration program related. Note: May be necessary for the software to work properly. Note: Located in \%Program Files%\cFosSpeed\

    Please remove it to test.


    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\051011-29468-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`0321e000 PsLoadedModuleList = 0xfffff800`03463e90
    Debug session time: Tue May 10 05:00:28.895 2011 (GMT-4)
    System Uptime: 0 days 0:22:59.988
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {7073688b, 2, 0, fffff88005841c14}
    
    Unable to load image \SystemRoot\system32\DRIVERS\cfosspeed.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for cfosspeed.sys
    *** ERROR: Module load completed but symbols could not be loaded for cfosspeed.sys
    Probably caused by : cfosspeed.sys ( cfosspeed+11c14 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 000000007073688b, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88005841c14, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034cf0e8
     000000007073688b 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    cfosspeed+11c14
    fffff880`05841c14 80b92802000000  cmp     byte ptr [rcx+228h],0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff80000b9c1d0 -- (.trap 0xfffff80000b9c1d0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8005df51a8 rbx=0000000000000000 rcx=0000000070736663
    rdx=0000000000150e90 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88005841c14 rsp=fffff80000b9c360 rbp=fffff80000b9c530
     r8=0000000000000000  r9=fffff80000b9c2f8 r10=fffff88005944310
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    cfosspeed+0x11c14:
    fffff880`05841c14 80b92802000000  cmp     byte ptr [rcx+228h],0 ds:4300:00000000`7073688b=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8000329dbe9 to fffff8000329e640
    
    STACK_TEXT:  
    fffff800`00b9c088 fffff800`0329dbe9 : 00000000`0000000a 00000000`7073688b 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff800`00b9c090 fffff800`0329c860 : fffff880`05941f80 00000000`00000000 00000000`00000000 fffffa80`05df5190 : nt!KiBugCheckDispatch+0x69
    fffff800`00b9c1d0 fffff880`05841c14 : 00000000`00000018 fffff880`059110a5 ffffffff`fff85ee0 fffff800`00000000 : nt!KiPageFault+0x260
    fffff800`00b9c360 00000000`00000018 : fffff880`059110a5 ffffffff`fff85ee0 fffff800`00000000 fffff880`05943b60 : cfosspeed+0x11c14
    fffff800`00b9c368 fffff880`059110a5 : ffffffff`fff85ee0 fffff800`00000000 fffff880`05943b60 00000000`00000000 : 0x18
    fffff800`00b9c370 ffffffff`fff85ee0 : fffff800`00000000 fffff880`05943b60 00000000`00000000 fffffa80`05df5190 : cfosspeed+0xe10a5
    fffff800`00b9c378 fffff800`00000000 : fffff880`05943b60 00000000`00000000 fffffa80`05df5190 fffff880`058ef0e6 : 0xffffffff`fff85ee0
    fffff800`00b9c380 fffff880`05943b60 : 00000000`00000000 fffffa80`05df5190 fffff880`058ef0e6 fffffa80`05e86470 : 0xfffff800`00000000
    fffff800`00b9c388 00000000`00000000 : fffffa80`05df5190 fffff880`058ef0e6 fffffa80`05e86470 fffff800`00b9c530 : cfosspeed+0x113b60
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    cfosspeed+11c14
    fffff880`05841c14 80b92802000000  cmp     byte ptr [rcx+228h],0
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  cfosspeed+11c14
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: cfosspeed
    
    IMAGE_NAME:  cfosspeed.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4aeacc83
    
    FAILURE_BUCKET_ID:  X64_0xD1_cfosspeed+11c14
    
    BUCKET_ID:  X64_0xD1_cfosspeed+11c14
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm cfosspeed
    start             end                 module name
    fffff880`05830000 fffff880`05967000   cfosspeed T (no symbols)           
        Loaded symbol image file: cfosspeed.sys
        Image path: \SystemRoot\system32\DRIVERS\cfosspeed.sys
        Image name: cfosspeed.sys
        Timestamp:        Fri Oct 30 07:22:43 2009 (4AEACC83)
        CheckSum:         0013484C
        ImageSize:        00137000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 10
    Windows 7 Professional x64
    Thread Starter
       #3

    Thanks for the reply. I uninstalled cFosSpeed, but had another 0x0000001e, a 0x0000003b ndis.sys, a 0x000000d1, and a 0x0000007f bluescreen. I attached the minidumps.
    Last edited by GeoDuck; 12 May 2011 at 01:51.
      My Computer


  4. Posts : 10
    Windows 7 Professional x64
    Thread Starter
       #4

    Lately the computer's also been just freezing and the sound holds one tone, like a blue screen, but with no blue screen.
    It usually happens when I'm watching videos or playing games. I don't know if that's just because I do a lot of that, or it's actually related.
      My Computer


  5. Posts : 28,845
    Win 8 Release candidate 8400
       #5

    GeoDuck said:
    Lately the computer's also been just freezing and the sound holds one tone, like a blue screen, but with no blue screen.
    It usually happens when I'm watching videos or playing games. I don't know if that's just because I do a lot of that, or it's actually related.

    As usual when you start getting BSOD's its usually more than just one problem. You are still showing at least two more

    1-these crashes are related to your video driver. A re-install of the newest rev using these instructions should help

    When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

    Or Phyxion.net - Driver Sweeper

    When it is removed then download and install the fresh copy.

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\051111-22838-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Machine Name:
    Kernel base = 0xfffff800`03265000 PsLoadedModuleList = 0xfffff800`034aa650
    Debug session time: Wed May 11 23:56:56.911 2011 (GMT-4)
    System Uptime: 0 days 4:10:01.441
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................................
    Loading User Symbols
    Loading unloaded module list
    ...............................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {1, 2, 8, 1}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedInsertTailList+47 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000001, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: 0000000000000001, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003514100
     0000000000000001 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    +60f3952f02f5daa0
    00000000`00000001 ??              ???
    
    PROCESS_NAME:  System
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    TRAP_FRAME:  fffff880031fb530 -- (.trap 0xfffff880031fb530)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=000000000000000e
    rdx=000000000000000c rsi=0000000000000000 rdi=0000000000000000
    rip=0000000000000001 rsp=fffff880031fb6c0 rbp=0000000000000000
     r8=fffffa8004938db8  r9=0000000000000000 r10=0000000000000000
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    00000000`00000001 ??              ???
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800032e42a9 to fffff800032e4d00
    
    FAILED_INSTRUCTION_ADDRESS: 
    +60f3952f02f5daa0
    00000000`00000001 ??              ???
    
    STACK_TEXT:  
    fffff880`031fb3e8 fffff800`032e42a9 : 00000000`0000000a 00000000`00000001 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
    fffff880`031fb3f0 fffff800`032e2f20 : fffffa80`046c72c0 fffff880`01064f4f 00000000`0000003c fffff880`031fb740 : nt!KiBugCheckDispatch+0x69
    fffff880`031fb530 00000000`00000001 : fffff880`031fb740 fffffa80`05d464f0 fffffa80`0446eea0 fffff880`02f7111b : nt!KiPageFault+0x260
    fffff880`031fb6c0 fffff880`031fb740 : fffffa80`05d464f0 fffffa80`0446eea0 fffff880`02f7111b 00000000`00000000 : 0x1
    fffff880`031fb6c8 fffffa80`05d464f0 : fffffa80`0446eea0 fffff880`02f7111b 00000000`00000000 fffffa80`05d45000 : 0xfffff880`031fb740
    fffff880`031fb6d0 fffffa80`0446eea0 : fffff880`02f7111b 00000000`00000000 fffffa80`05d45000 fffffa80`0446ef80 : 0xfffffa80`05d464f0
    fffff880`031fb6d8 fffff880`02f7111b : 00000000`00000000 fffffa80`05d45000 fffffa80`0446ef80 fffffa80`04467ea0 : 0xfffffa80`0446eea0
    fffff880`031fb6e0 fffffa80`04a7b1b0 : fffffa80`04a7b1b0 00000000`00000000 fffffa80`04a7b060 00000000`ffffffff : dxgmms1!VidSchiInterlockedInsertTailList+0x47
    fffff880`031fb730 fffffa80`04a7b1b0 : 00000000`00000000 fffffa80`04a7b060 00000000`ffffffff 00000000`00000009 : 0xfffffa80`04a7b1b0
    fffff880`031fb738 00000000`00000000 : fffffa80`04a7b060 00000000`ffffffff 00000000`00000009 fffffa80`06ab1010 : 0xfffffa80`04a7b1b0
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    dxgmms1!VidSchiInterlockedInsertTailList+47
    fffff880`02f7111b 488b5c2450      mov     rbx,qword ptr [rsp+50h]
    
    SYMBOL_STACK_INDEX:  7
    
    SYMBOL_NAME:  dxgmms1!VidSchiInterlockedInsertTailList+47
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1
    
    FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_dxgmms1!VidSchiInterlockedInsertTailList+47
    
    BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_dxgmms1!VidSchiInterlockedInsertTailList+47
    
    Followup: MachineOwner
    ---------
    
    3: kd> lmvm dxgmms1
    start             end                 module name
    fffff880`02f61000 fffff880`02fa7000   dxgmms1    (pdb symbols)          c:\symbols\dxgmms1.pdb\0901C357E9E846EE8C2FBCC8107163201\dxgmms1.pdb
        Loaded symbol image file: dxgmms1.sys
        Mapped memory image file: C:\Symbols\dxgmms1.sys\4CE799C146000\dxgmms1.sys
        Image path: \SystemRoot\System32\drivers\dxgmms1.sys
        Image name: dxgmms1.sys
        Timestamp:        Sat Nov 20 04:49:53 2010 (4CE799C1)
        CheckSum:         00047A89
        ImageSize:        00046000
        File version:     6.1.7601.17514
        Product version:  6.1.7601.17514
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     dxgmms1.sys
        OriginalFilename: dxgmms1.sys
        ProductVersion:   6.1.7601.17514
        FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
        FileDescription:  DirectX Graphics MMS
        LegalCopyright:   © Microsoft Corporation. All rights reserved.


    2-Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.

    They use a driver, found in your dmp,sptd.sys, that is notorious for causing BSODs.

    Use this SPTD uninstaller DuplexSecure - Downloads

    when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place. MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor


    3- other items of note.

    Your fsecure email interceptor is often a cause.

    Some what less often is Related to saskutil64.sys SCM PCMCIA Smart Card Reader from SCM Microsystems, Inc
      My Computer


  6. Posts : 10
    Windows 7 Professional x64
    Thread Starter
       #6

    1- I downloaded Phyxion.net - Driver Sweeper 3.0, removed AMD - Display, restarted, installed the latest driver 11.5, and restarted.

    2- I closed PowerISO and stopped it from running on startup. I downloaded and ran the SPTD uninstaller.

    3- I uninstalled Shaw Secure (which is just a rebranded F-Secure) and installed Comodo.

    Then when I was Alt-F4ing out of a game, I got a 0x0000003b dxgmms1.sys error. BlueScreenView also highlighted atikmdag.sys as a cause.
    I also got a 0x1000007e while trying to start a game.
    Last edited by GeoDuck; 13 May 2011 at 19:53. Reason: new bluescreen
      My Computer


  7. Posts : 28,845
    Win 8 Release candidate 8400
       #7

    GeoDuck said:
    1- I downloaded Phyxion.net - Driver Sweeper 3.0, removed AMD - Display, restarted, installed the latest driver 11.5, and restarted.

    2- I closed PowerISO and stopped it from running on startup. I downloaded and ran the SPTD uninstaller.

    3- I uninstalled Shaw Secure (which is just a rebranded F-Secure) and installed Comodo.

    Then when I was Alt-F4ing out of a game, I got a 0x0000003b dxgmms1.sys error. BlueScreenView also highlighted atikmdag.sys as a cause.
    I also got a 0x1000007e while trying to start a game.
    Blue screen view is a decent enough tool but it often gets "confused"

    We need to examine the DMP with a better tool. Please upload it.
      My Computer


  8. Posts : 10
    Windows 7 Professional x64
    Thread Starter
       #8

    Here they are, with another 3b atikmpag.sys when I was playing a game.
    Last edited by GeoDuck; 13 May 2011 at 22:52.
      My Computer


  9. Posts : 28,845
    Win 8 Release candidate 8400
       #9

    GeoDuck said:
    Here they are, with another 3b atikmpag.sys when I was playing a game.

    All three point to memory corruption (exception) caused by a driver. In your case the video driver, or card.

    I see you have installed the april, 2011 driver.

    Do the crashes happen in safe mode?
      My Computer


  10. Posts : 10
    Windows 7 Professional x64
    Thread Starter
       #10

    There were no blue screens in safe mode, but the computer did freeze up twice. However, no dumps were created from the unresponsiveness.
    I attached a dump from just before I put it in safe mode.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:42.
Find Us