Random BSOD in the past couple of days - Please Help!


  1. Posts : 5
    Windows 7 Professional 64bit
       #1

    Random BSOD in the past couple of days - Please Help!


    I've had no issues with my desktop from the time it was built until the last couple of days. Now I'm getting random BSOD pretty regularly. So far this is what I've done to try to resolve the problem, but nothing's worked out.

    • Updated video card driver
    • Ran Windows Memory Checker on Start Up
    • Ran Windows Error Checking on Hard Drive


    The BSOD's are usually DRIVER_IRQL_LESS_NOT_EQUAL, SYSTEM_SERVICE_EXCEPTION, ataport.sys.

    The PERFORM.html and BSOD Dump & File Collection data is attached.

    This is my work computer so I've lost a couple of days just trying to get this thing running again. Any help is appreciated. Thanks!

    Built April 2010
    Windows 7 Professional - 64bit - OEM
    Intel i5 - 750
    ATI Radeon HD5670
    8GB RAM (4 x 2GB)
    WD Caviar Black 500 GB
      My Computer


  2. Posts : 5
    Windows 7 Professional 64bit
    Thread Starter
       #2

    Can anybody be of any help with my BSOD's? I need to get my computer up and running safely asap
      My Computer


  3. Posts : 5
    Windows 7 Professional 64bit
    Thread Starter
       #3

    I just got another BSOD with a different error than I've had in the past.

    snapman.sys
    PAGE_FAULT_NOT_IN_NONPAGED_AREA

    Can anybody help me with this?
      My Computer


  4. Posts : 1
    Windows 7 Pro x64
       #4

    Hey, perhaps you've sorted this by now? I've been getting similar BSODs ever since installing 4 sticks of 2GB ram (previously had 2x2GB with no BSODs ever). Like you the BSODs differ and I recognise all the ones you've had. Obviously it may not be your ram, but I saw you were also using 4 sticks. The more I OC them, the quicker it crashes. And it's not the dimms as I've run for hours using different combinations. My next change is to up the NB & FSB voltage and see if it helps. If you do still have this problem I'd recommend running with 2 sticks and see if you still BSOD. J
      My Computer


  5. Posts : 13,354
    Windows 7 Professional x64
       #5

    To the OP:

    It appears ThreatFire/PC Tools is the problem. Please remove it, using Microsoft Security Essentials as a replacement.

    MSE: http://www.microsoft.com/security_essentials

    If the BSODs persist, run driver verifier: Driver Verifier - Enable and Disable

    ...Summary of the dumps:
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Dec 27 13:59:04.076 2010 (UTC - 5:00)
    System Uptime: 0 days 0:09:44.497
    Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )
    BUGCHECK_STR:  0x1E_c0000005
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!RtlImageNtHeaderEx+3f
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Dec 27 13:47:39.167 2010 (UTC - 5:00)
    System Uptime: 0 days 0:06:19.587
    Probably caused by : ataport.SYS ( ataport!memmove+64 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xD1_ataport!memmove+64
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Dec 27 13:39:37.857 2010 (UTC - 5:00)
    System Uptime: 0 days 2:07:39.903
    Probably caused by : ntkrnlmp.exe ( nt!KiApcInterrupt+1f1 )
    BUGCHECK_STR:  0x1E_c0000005
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  rundll32.exe
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiApcInterrupt+1f1
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Dec 27 10:54:36.957 2010 (UTC - 5:00)
    System Uptime: 0 days 0:03:04.003
    Probably caused by : PCTCore64.sys ( PCTCore64+c28b )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  WerFault.exe
    FAILURE_BUCKET_ID:  X64_0x3B_PCTCore64+c28b
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Mon Dec 27 10:50:23.950 2010 (UTC - 5:00)
    System Uptime: 0 days 0:07:20.386
    Probably caused by : ataport.SYS ( ataport!memmove+64 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xD1_ataport!memmove+64
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Dec 23 18:33:03.769 2010 (UTC - 5:00)
    System Uptime: 0 days 0:02:05.205
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    BUGCHECK_STR:  0x7f_8
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  AtBroker.exe
    FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Dec 23 18:27:01.801 2010 (UTC - 5:00)
    System Uptime: 0 days 0:13:39.847
    Probably caused by : ataport.SYS ( ataport!memmove+64 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xD1_ataport!memmove+64
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Dec 23 18:11:47.757 2010 (UTC - 5:00)
    System Uptime: 0 days 1:11:44.803
    Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+226 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xA_nt!KeSetEvent+226
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
    I apologize your thread was overlooked.
      My Computer


  6. Posts : 5
    Windows 7 Professional 64bit
    Thread Starter
       #6

    I ended up formatting and reinstalling Windows. So far no issues with it.
      My Computer


  7. Posts : 5
    Windows 7 Professional 64bit
    Thread Starter
       #7

    Running MSE too btw. Good product.
      My Computer


  8. Posts : 13,354
    Windows 7 Professional x64
       #8

    Alright, let us know if you need anything else! We will do our best to answer within a couple of hours; if not, don't hesitate to PM me.
      My Computer


 

  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 22:41.
Find Us