Constant bluescreens after new build

Page 2 of 2 FirstFirst 12

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

    More often now, the computer shows graphical corruption, then just restarts instead of showing a blue screen. Sometimes when it does show a blue screen, it has this message:
    Dump file size too small - requires at least 592732275 bytes.
    Future kernel memory dumps may require larger size.
    Switching to minidump...

    I don't know if it's related, but when the computer starts up and shows the desktop, the mouse and keyboard become unresponsive for a few seconds.
    Last edited by GeoDuck; 17 May 2011 at 17:34. Reason: exact message
      My Computer


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

    GeoDuck said:
    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.
    No BSOD in safe mode and BSOD in normal boot = a driver used in normal boot but not safe (ie video, networking, etc)

    I did also notice some known BSOD causing things (like super adware blocker?) but they dont seem to be involved.
      My Computer


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

    I had it in Safe Mode with Networking, so it must have loaded the networking drivers.
    SuperAntiSpyware? I only got it for its Repair broken Network Connection (WinSock LSP Chain) function.

    I emailed AMD support about my processor, because I can't find ATI support for my video card. I also attached all the mindumps since the last one. There seem to be a lot of 0x0000000a hardware errors now.
      My Computer


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

    GeoDuck said:
    I had it in Safe Mode with Networking, so it must have loaded the networking drivers.
    SuperAntiSpyware? I only got it for its Repair broken Network Connection (WinSock LSP Chain) function.

    I emailed AMD support about my processor, because I can't find ATI support for my video card. I also attached all the mindumps since the last one. There seem to be a lot of 0x0000000a hardware errors now.
    The majority of these were related to your hotspotshield and taphss.sys. I would remove it.


    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\New folder\051711-23821-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`0321f000 PsLoadedModuleList = 0xfffff800`03464650
    Debug session time: Tue May 17 07:07:04.238 2011 (GMT-4)
    System Uptime: 0 days 0:30:57.752
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {fffff9801a5d4cd8, 2, 0, fffff880051e5f61}
    
    Unable to load image taphss.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for taphss.sys
    *** ERROR: Module load completed but symbols could not be loaded for taphss.sys
    Probably caused by : taphss.sys ( taphss+2f61 )
    
    Followup: MachineOwner
    ---------
    
    2: 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: fffff9801a5d4cd8, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff880051e5f61, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034ce100
     fffff9801a5d4cd8 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    taphss+2f61
    fffff880`051e5f61 ??              ???
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff8800319a860 -- (.trap 0xfffff8800319a860)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff8800319aa10 rbx=0000000000000000 rcx=fffff8800319ab10
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880051e5f61 rsp=fffff8800319a9f0 rbp=fffff88003af3960
     r8=0000000000000000  r9=0000000000000000 r10=fffff8800319ad40
    r11=fffff8800319aae0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    taphss+0x2f61:
    fffff880`051e5f61 ??              ???
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8000329e2a9 to fffff8000329ed00
    
    STACK_TEXT:  
    fffff880`0319a718 fffff800`0329e2a9 : 00000000`0000000a fffff980`1a5d4cd8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0319a720 fffff800`0329cf20 : 00000000`00000000 fffff880`0319a900 00000000`00000000 00000000`00020104 : nt!KiBugCheckDispatch+0x69
    fffff880`0319a860 fffff880`051e5f61 : 00000000`00000000 00000000`00000004 00000000`0000000d fffff800`033596db : nt!KiPageFault+0x260
    fffff880`0319a9f0 00000000`00000000 : 00000000`00000004 00000000`0000000d fffff800`033596db 00000000`00000000 : taphss+0x2f61
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    taphss+2f61
    fffff880`051e5f61 ??              ???
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  taphss+2f61
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: taphss
    
    IMAGE_NAME:  taphss.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4aaff1df
    
    FAILURE_BUCKET_ID:  X64_0xD1_taphss+2f61
    
    BUCKET_ID:  X64_0xD1_taphss+2f61
    
    Followup: MachineOwner
    ---------
      My Computer


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

    I uninstalled HotSpot Shield and started getting a bunch of Peer Name Resolution Protocol and Peer Networking Grouping service errors in Event Viewer, but managed to fix it.

    Then I still got a bunch more blue screens (attached). I finally figured out how to use Windbg. Before, I was using a command prompt, which was tedious. Much easier with the GUI .
    I see two new errors: "amdppm.sys" is probably related to my CPU, and "MijXfilt.sys" is for connecting my PS3 controller.

    Code:
    BugCheck A, {4d16, d, 1, fffff800032aafd5}
    
    Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    
    ---------------------
    
    BugCheck 1E, {0, 0, 0, 0}
    
    Unable to load image MijXfilt.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for MijXfilt.sys
    *** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
    Probably caused by : MijXfilt.sys ( MijXfilt+394b )
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Last edited by GeoDuck; 18 May 2011 at 13:47.
      My Computer


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

    Good going. If you are interested in learning BSOD's PM me.

    Meanwhile update the two drivers you found.
      My Computer


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

    I didn't have a BSoD all day

    I think it might have been CPU, RAM, and HT Link frequencies set in the BIOS. If I loaded Failsafe defaults, the CPU FSB Frequency would be at 200, but when I would restart it would have automatically increased to 240 and I couldn't change it. This would overclock all the other frequencies.

    So I wrote down all the Failsafe Default frequencies, and when it restarted I decreased all the ratios to try to match the previous values. Hopefully this has really fixed it.

    Update: No bluescreens for 5 days. It was either the DRAM Frequency or the HT Link Frequency being auto-overclocked in the BIOS.
    Last edited by GeoDuck; 23 May 2011 at 17:59.
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 15:51.
Find Us