At a loss... =(, bluescreens after multiple upgrades...

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Lisa Huang, Jun 7, 2012.

  1. Lisa Huang

    Lisa Huang New Member

    Joined:
    Jun 7, 2012
    Messages:
    22
    Likes Received:
    2
    Hi, everyone... I am receiving the same bsods on my PC even after I have tried upgrading every possible hardware that might of been the culprit.. Please scroll to the bottom for tl;dr.

    I've had this pc for about 2 years now (got it from a friend) and it was working fine until I connected it to the internet... Since then, I have had multiple bsods in which I attempted to fix myself by browsing for information online.

    At first I thought it was the RAM, so I replaced the origanal set of DDR3 Kingston 4 gigs with a new set of DDR3 Corsair Dominator 4 gigs.

    It worked for about 2 days without bsods...but then they came back. I felt bummed out that the ram wasn't the problem. I didn't touch my PC for a few months and then decided to try and fix it again...

    So I thought it might of been a hard drive problem since it could of been faulty. I purchased a new 1000GB Seagate Sata HD to replace the old 500GB. Again, it worked fine for about 2 days without bsods...and then they came back again. A few days later, my PC started having POST problems. My PC would have a blank screen while being connected to my monitor.

    I researched a video on youtube done by NCIX and they said POST problems are usually caused by a faulty video card...

    But before I invested any more money in to my PC, I decided it would be safer to take it to a PC tech and verify the problem. I drove to my local PC repair shop and left it for a few days.

    During the few days it was there, I called the technician and told him that I had already updated all the drivers and I still didn't know what was the problem. He told me that it might be a MOBO problem and that I would probably have to order a new MOBO to fix it.

    He called me later that day and said it wasn't a MOBO problem and the PC was up running again without any bsods..., I asked him what was the problem, and he told me he just simply reseated all the PC components...

    I paid him $80 for his service (what a RIP OFF)...

    I brought the PC home and for the first 3 days, it worked flawlessly. I thought I had finally gotten rid of the bsods. But slowly...day by day...they started coming back... I then noticed that my video card started making weird noises and such. I figured that the video card was definitely the problem so I ordered a new EVGA GTX 550ti from newegg...

    When the video card came, I slipped it in and tried my PC. At first, the resolution was a little off but when I logged on to the PC, everything was the same and fine.

    I started playing a few games with my friend and I would occasionally get bsod...but when I turned my PC back on, I would be fine for a few hours.

    After replacing the RAM, HD, and now Video Card, I feel like I've done everything I could possibly do to fix the problem. =( However the problem still exists.

    I feel like...there's nothing left I can do. The only thing I can think of now is a faulty slot on the RAM or Video card slot which means I would have to buy a new mobo...

    I don't want to spend any more money on something if I don't know if it will fix it.... please... I need help... I think I've done everything I can possibly think of =(

    I've learned so much from just researching on my own and I never thought I would learn this much... but I'm at a wall. I don't know what's causing my pc to bsod... =(

    ----

    tl;dr:

    Problem: Receiving blue screens.

    Steps taken to troubleshoot: Have replaced origanl RAM, Hard Drive, and Video Card with all brand new equipment. Have updated bios and all drivers.


    ----

    Here I have attached the following information about my PC: Minidumps, CPU-Z screenshots, and RAMMon html files.
     

    Attached Files:

  2. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Hello and welcome to the forum.
    Let's try two things first.
    Go here ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
    Expand utilities, scroll down to about the 12th one down called ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit that should update this driver
    ASACPI.sys 3/27/2005
    to something a bit more current.
    And second uninstall Norton / Symantec, completely. Use the programs uninstalled or the programs and features applet in the control panel and then follow that up with the vendor specific proprietary removal tool from here https://www-secure.symantec.com/norton-support/jsp/help-solutions.jsp?lg=english&ct=united+states&docid=20080710133834EN&product=home&version=1&pvid=f-home
    Replace it for now with MSE from here Spyware Protection | Free Spyware Protection | Microsoft Security Essentials
    If Blue screens persist. Please attach new ones here by updating your thread.
    Thanks
    Good luck
    Randy
    Code:
    BugCheck 19, {22, 4d000000000000, 0, 0}
    GetPointerFromAddress: unable to read from fffff800030ff100
    GetUlongFromAddress: unable to read from fffff8000306da38
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72d6 )
    BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    Arguments:
    Arg1: 0000000000000022, 
    Arg2: 004d000000000000
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    GetUlongFromAddress: unable to read from fffff8000306da38
    BUGCHECK_STR:  0x19_22
    POOL_ADDRESS:  004d000000000000 
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  Steam.exe
    CURRENT_IRQL:  2
    LAST_CONTROL_TRANSFER:  from fffff80002e5a4ce to fffff80002ed01c0
    STACK_TEXT:  
    fffff880`088123b8 fffff800`02e5a4ce : 00000000`00000019 00000000`00000022 004d0000`00000000 00000000`00000000 : nt!KeBugCheckEx
    fffff880`088123c0 fffff800`02ffc1fa : 00000000`00000000 fffff880`08812510 fffff880`08812490 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x72d6
    fffff880`08812450 fffff800`02ed42e3 : 00000000`a0000003 fffffa80`07955810 fffffa80`0557b7b0 fffff880`00000000 : nt!ExFreePoolWithTag+0x46a
    fffff880`08812500 fffff880`010a1ed6 : fffffa80`04b26030 fffffa80`0557b901 fffffa80`07cb5c10 00000000`00000000 : nt!IopfCompleteRequest+0xa53
    fffff880`088125f0 fffff880`010c12b9 : fffffa80`07955810 fffffa80`04a58010 fffffa80`07955800 fffffa80`04983de0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x556
    fffff880`08812680 fffff800`031c9be5 : 00000000`00000005 fffffa80`074131c8 fffffa80`07364010 00000000`00000000 : fltmgr!FltpCreate+0x2a9
    fffff880`08812730 fffff800`031c6488 : fffffa80`048c4ad0 fffff800`00000000 fffffa80`07413010 fffff880`00000001 : nt!IopParseDevice+0x5a5
    fffff880`088128c0 fffff800`031c76a6 : 00000000`00000000 fffffa80`07413010 fffff880`08812a40 fffffa80`03ab5660 : nt!ObpLookupObjectName+0x588
    fffff880`088129b0 fffff800`031c8fac : fffffa80`07995cb8 00000000`00000000 fffffa80`079fdb01 ffffffff`ffffffff : nt!ObOpenObjectByName+0x306
    fffff880`08812a80 fffff800`031d3c04 : 00000000`0008e2e8 fffff960`80100080 00000000`0008ebb0 00000000`0008e300 : nt!IopCreateFile+0x2bc
    fffff880`08812b20 fffff800`02ecf453 : fffff900`c3091ca0 0000007f`ffffffff 0000000e`00000011 00000980`00000000 : nt!NtCreateFile+0x78
    fffff880`08812bb0 00000000`7753186a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0008e278 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7753186a
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+72d6
    fffff800`02e5a4ce cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+72d6
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f76721c
    FAILURE_BUCKET_ID:  X64_0x19_22_nt!_??_::FNODOBFM::_string_+72d6
    BUCKET_ID:  X64_0x19_22_nt!_??_::FNODOBFM::_string_+72d6
    
    fffff880`08812488  fffff880`07c3d036Unable to load image \SystemRoot\System32\Drivers\N360x64\0502010.003\SRTSP64.SYS, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SRTSP64.SYS
    *** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS
     SRTSP64+0x3d036
    
    fffff880`088124b8  fffff880`0130741aUnable to load image \SystemRoot\system32\drivers\N360x64\0502010.003\SYMEFA64.SYS, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SYMEFA64.SYS
    *** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS
     SYMEFA64+0xbf41a
     
  3. Lisa Huang

    Lisa Huang New Member

    Joined:
    Jun 7, 2012
    Messages:
    22
    Likes Received:
    2
    Hi, Randy!

    Thanks for responding. =)

    I've downloaded and installed ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit from Asus.

    I've uninstalled and removed Norton and replaced it with MSE.

    I am however still getting blue screens. =\

    While looking through bluescreen view, the last 5 drivers to cause bluescreens were:

    nvlddmkm.sys (nVidia related) I have the latest video driver installed.
    ataport.SYS
    tcpip.sys
    dxgmms1.sys (DirectX related) I have hardware and 3d acceleration turned on.
    ntoskrnl.exe

    80% of my stop errors are: KMODE_EXCEPTION_NOT_HANDLED
    and almost always ends with 0x0000001e

    This happens most frequently while playing a game. Happens sometimes while watching youtube. And rarely will happen if just browsing through the internet.

    ---

    Below I have attatched a txt report of bluescreen view.

    If you need something else attatched, just let me know. Thanks! =)
     

    Attached Files:

  4. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    We really don't need to see the report. What might be more helpful would be any new dump files (.dmp) that you may have gotten since making the changes above.
    Thanks
    Randy
     
  5. Lisa Huang

    Lisa Huang New Member

    Joined:
    Jun 7, 2012
    Messages:
    22
    Likes Received:
    2
    Hi, Randy.

    I have attached the new dumps below.

    Also, I have updated my realtek driver and uninstalled AMD Catalyst. I figured AMD Catalyst might of been conflicting with nVidia.

    I use a program called Driver Detective to update all my drivers. It appears the program may of been downloading conflicting drivers... (I think)

    Anyways, I've been receiving some new stop error codes I've never seen before:

    watchdog.sys
    Microsoft update related?

    MpFilter.sys
    MSE related?

    Rt64win7.sys
    Seems to be RealTek related. I downloaded the driver but I'm not sure if it installed correctly since there wasn't no exe.


    I'm beginning to think I may have conflicting audio or video drivers. I can attach an image of my Device Manager list if you're interested.

    Thanks.
     

    Attached Files:

  6. Lisa Huang

    Lisa Huang New Member

    Joined:
    Jun 7, 2012
    Messages:
    22
    Likes Received:
    2
    UPDATE:

    I've decided to reformat and do a fresh install. I'm going to install and update the most basic drivers needed for a new pc:

    - Video Card Driver (nVidia)
    - Network Interface Card Driver (Realtek)
    - Audio Driver (VIA HD Audio)
    - USB Keyboard Driver (Microsoft IntelliType Pro)
    - USB Mouse Driver (Razer Lachesis)

    I will keep you updated to see if I receive any bluescreens after the install.
     
  7. Lisa Huang

    Lisa Huang New Member

    Joined:
    Jun 7, 2012
    Messages:
    22
    Likes Received:
    2
    Update:

    After a fresh installation and reformatting my HD, I installed the drivers up above through my Driver Detective program.

    - Video Card
    - Sound Card
    - Chipset
    - Mice USB
    - Keyboard USB
    - Network

    It appears I'm still getting the same bsod from KMODE_EXCEPTION_NOT_HANDLED ntoskrnl.exe

    Here is my new minidump after the fresh installation

    Thank you for your patience.
     

    Attached Files:

  8. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    OK, with only the single new dumpfile since the new install we will start anew.
    First it looks like you have not upgraded to SP1 yet so I would suggest doing that.
    Second I am not a big fan of Driver Detective or other Find You A Driver software suites.
    You newest dump file
    Code:
    BugCheck 1E, {0, 0, 0, 0}
    [COLOR=#ff0000][U][B]Probably caused by : usbohci.sys[/B][/U][/COLOR] ( usbohci!OHCI_ProcessDoneAsyncTd+24 )
    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.
    Arguments:
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
    FAULTING_IP: 
    +6566346566346262
    00000000`00000000 ??              ???
    EXCEPTION_PARAMETER1:  0000000000000000
    EXCEPTION_PARAMETER2:  0000000000000000
    ERROR_CODE: (NTSTATUS) 0 - STATUS_SUCCESS
    BUGCHECK_STR:  0x1E_0
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    EXCEPTION_RECORD:  fffff88002f8b898 -- (.exr 0xfffff88002f8b898)
    ExceptionAddress: fffff880042efec8 (usbohci!OHCI_ProcessDoneAsyncTd+0x0000000000000024)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    TRAP_FRAME:  fffff88002f8b940 -- (.trap 0xfffff88002f8b940)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000000000a rbx=0000000000000000 rcx=fffffa80056ad6a0
    rdx=fffff88002bc4100 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880042efec8 rsp=fffff88002f8bad0 rbp=fffff88002bc4180
     r8=000000004f444601  r9=fffff88002bc4100 r10=00000000ffffffff
    r11=fffff88002f8bb18 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    usbohci!OHCI_ProcessDoneAsyncTd+0x24:
    fffff880`042efec8 ff4e10          dec     dword ptr [rsi+10h] ds:c1a0:00000000`00000010=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002cbf46e to fffff80002cc7710
    STACK_TEXT:  
    fffff880`02f8a988 fffff800`02cbf46e : fffff800`02c57000 00000000`0012fba3 fffff880`02f8b100 fffff800`02cf4668 : nt!KeBugCheck
    fffff880`02f8a990 fffff800`02ced40d : fffff800`02ed5b7c fffff800`02e0fe84 fffff800`02c57000 fffff880`02f8b898 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff880`02f8a9c0 fffff800`02cf4a90 : fffff800`02e16b14 fffff880`02f8aa38 fffff880`02f8b898 fffff800`02c57000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`02f8a9f0 fffff800`02d019ef : fffff880`02f8b898 fffff880`02f8b100 fffff880`00000000 fffff880`02bc4000 : nt!RtlDispatchException+0x410
    fffff880`02f8b0d0 fffff800`02cc6d82 : fffff880`02f8b898 fffffa80`06234a78 fffff880`02f8b940 ff00fa80`045c87c8 : nt!KiDispatchException+0x16f
    fffff880`02f8b760 fffff800`02cc568a : fffffa80`062347b0 00000000`00000000 fffffa80`056ac1a0 fffff880`0430c2c5 : nt!KiExceptionDispatch+0xc2
    fffff880`02f8b940 fffff880`042efec8 : fffffa80`056ac101 fffff880`04325d70 00000000`00000000 fffff880`043250d8 : nt!KiGeneralProtectionFault+0x10a
    fffff880`02f8bad0 fffff880`042efd98 : fffffa80`06234a78 fffff880`02bc4180 00000000`00000000 fffff880`02bc4000 : usbohci!OHCI_ProcessDoneAsyncTd+0x24
    fffff880`02f8bb20 fffff880`042f1737 : fffffa80`062349f0 fffffa80`062347b0 00000000`00000000 fffffa80`056ac1a0 : usbohci!OHCI_PollAsyncEndpoint+0x3ec
    fffff880`02f8bb80 fffff880`042f9e8b : 00000000`00000002 fffffa80`062347b0 fffffa80`056ac1a0 00000000`00000000 : usbohci!OHCI_PollEndpoint+0x3f
    fffff880`02f8bbb0 fffff880`042fe9b1 : 00000000`00000030 00000000`00000004 fffffa80`062347b0 fffffa80`056ac050 : USBPORT!MPf_PollEndpoint+0x9b
    fffff880`02f8bbe0 fffff880`0430a043 : fffffa80`056ac1a0 00000000`00000030 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
    fffff880`02f8bc40 fffff880`042faf89 : fffffa80`056ac050 00000000`00000000 fffffa80`056aca02 fffffa80`056aca10 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1af
    fffff880`02f8bca0 fffff800`02cd2bfc : fffff880`02f63180 fffffa80`056aca10 fffffa80`056aca28 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
    fffff880`02f8bcd0 fffff800`02ccfeea : fffff880`02f63180 fffff880`02f6dfc0 00000000`00000000 fffff880`042fadb0 : nt!KiRetireDpcList+0x1bc
    fffff880`02f8bd80 00000000`00000000 : fffff880`02f8c000 fffff880`02f86000 fffff880`02f8bd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    usbohci!OHCI_ProcessDoneAsyncTd+24
    fffff880`042efec8 ff4e10          dec     dword ptr [rsi+10h]
    SYMBOL_STACK_INDEX:  7
    SYMBOL_NAME:  usbohci!OHCI_ProcessDoneAsyncTd+24
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: usbohci
    IMAGE_NAME:  usbohci.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc06
    FAILURE_BUCKET_ID:  X64_0x1E_0_usbohci!OHCI_ProcessDoneAsyncTd+24
    BUCKET_ID:  X64_0x1E_0_usbohci!OHCI_ProcessDoneAsyncTd+24
    Is complaining about usbohci.sys a microsoft native driver and not likely the actual cause. So go to your motherboard manufacturer's website and get your drivers directly from there. Far less chance of ending up with a one size fits all driver. You should always use the device manufacturer's website to get your hardware drivers whenever possible and seldom if ever rely on something like Driver Finder or Windows Update to install your drivers for you.
    Regards
    Randy
     
  9. Lisa Huang

    Lisa Huang New Member

    Joined:
    Jun 7, 2012
    Messages:
    22
    Likes Received:
    2
    Hi, Randy.

    Thanks for the response.

    I just wanted to give you an update on what I've done so far:

    - Installed System Update Readiness Tool for 64bit (x64) prior to updating to SP1
    - Installed SP1

    - Uninstalled VIA Sound Card that was given from Driver Detective and installed VIA Sound Card from asus website.
    - Uninstalled AMD Chipset that was given from Driver Detective and installed AMD Chipset from asus website.
    - Installed Realtek RTL8112L LAN Driver from asus website.

    Note: I am not sure if asus updates the drivers on their page. Most of the drivers they are offering date back to 09. With Driver Detective, they carry the latest drivers.

    Here is a link to all the drivers for my mobo
    ASUSTeK Computer Inc. -Support- Drivers and Download M4A785T-M

    - Discovered that I never configured the DDRam frequency of my Corsair Dominator ram to 1600MHz, 9-9-9-24, 1.65V. They had been on default this whole time which was at 1200mhz.

    - Appropriately set to 1600MHz(800MHz x 2 ram sticks), 9-9-9-24, 1.65V

    Another thing that you may find interesting is that while looking at my device manager, I discovered an unknown device with a yellow exclamation mark. Upon seeing the properties, the driver indicated it has something to do with ATK0110 (Most likely Asus related).

    For the time being, I have disabled this unknown driver, however, there is an update for this driver available through Windows Update.

    I am not sure if you are familiar with ATK0110 and would like me to enable and update or leave it disabled.

    Thanks!, and I will attach another dump if I get one.
     
  10. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Yes the ATK0110 driver by default generally dated sometime in 2005 has been identified as a Blue Screen culprit.
    Go to your driver page link above and expand utilities and go down about 14 or so down the page and you will see ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit 119,88 (KBytes) 2009.12.07 update. That 2009 driver seems to be fine although there may be even a newer one available that I am not aware of. If you install that one for now it should be fine I believe.
     
  11. nmsuk

    nmsuk Windows Forum Admin
    Staff Member Premium Supporter

    Joined:
    Sep 7, 2009
    Messages:
    2,708
    Likes Received:
    195
    Randy has just requested I find likes to the latest AMD Chipset drivers and they can be grabber from here.
     
  12. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    And the realtek driver for your network adapter should be from here Realtek
    Whenever your MoBo manufacturer seems to have older drivers, always try the actual device manufacturer's website. Actually that should normally be your first go to spot.
     
  13. Lisa Huang

    Lisa Huang New Member

    Joined:
    Jun 7, 2012
    Messages:
    22
    Likes Received:
    2
    Hi, Randy.

    Good news:

    My PC seems to be running more stable. I'm not getting bsod as often...

    Bad news:

    I just got bsod'd again. Here is my most recent dump.

    And I'm going to uninstall my realtek and amd driver and update with the new ones directly from the manufacturers website. I'll update this again when I receive another bsod.
     

    Attached Files:

  14. Lisa Huang

    Lisa Huang New Member

    Joined:
    Jun 7, 2012
    Messages:
    22
    Likes Received:
    2
    I have a question:

    I was wondering if I need the AMD Catalyst installed on my pc? It appears the AMD Catalyst is a driver for my onboard ATi graphics card. The thing is, I'm not using my onboard graphics card because I'm using an nVidia in my PCI-e slot.

    Is it possible that the AMD Catalyst driver is somehow conflicting with my nVidia card? or is that not possible?

    Thanks.
     
  15. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Not exactly sure what you are talking about here, but if you are referrencing the Catalyst Installer, which is part of the package from the AMD link that Rich (nmsuk) linked above, don't worry about it. It's just the installer interface go give you something pretty to look at while the chipset drivers are being installed. It is not going to install drivers for and ATI video card that you don't have enabled.
    Go ahead and get your chipset drivers installed because you are still getting;
    Code:
    BugCheck 1E, {0, 0, 0, 0}
    [COLOR=#ff0000][U][B]Probably caused by : usbohci.sys[/B][/U][/COLOR] ( usbohci!OHCI_ProcessDoneAsyncTd+24 )
    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.
    Arguments:
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    Which is likely linked to this;
    Code:
    fffff880`02ffb0f8  fffff880`045dc1f4Unable to load image usbfilter.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for [COLOR=#ff0000][U][B]usbfilter.sys[/B][/U][/COLOR]
    *** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
     [COLOR=#ff0000][U][B]usbfilter+0x21f4[/B][/U][/COLOR]
    usbfilter.sys AMD USB Filter Driver
    Which is likely linked to your chipset driver
     
  16. Lisa Huang

    Lisa Huang New Member

    Joined:
    Jun 7, 2012
    Messages:
    22
    Likes Received:
    2
    Bsod again... twice. =(

    1)
    NTFS_FILE_SYSTEM

    and

    2) QUOTA_UNDERFLOW

    Minidumps attached below.
     

    Attached Files:

  17. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Time to beat on your hard drive (system drive) for a while. (Back up critical data first)
    Remove or otherwise physically disable / disconnect any hard disk other than the Operating System disk. USB, FireWire, eSATA, (spinners, or Solid State of any kind)
    Launch an elevated command prompt and type
    ChkDsk C: /R
    Answer yes (Y) when prompted and reboot.
    Let it finish all five states and see what that produces in the way of worthwhile information.
    Check with your Hard Drive manufacturer's website and obtain their vendor specific proprietary disk diagnostic utility and use that to perform more extensive / exhaustive (whatever they call it) tests on the drive and see if that finds anything of value.
     
  18. Lisa Huang

    Lisa Huang New Member

    Joined:
    Jun 7, 2012
    Messages:
    22
    Likes Received:
    2
    Hi, Randy!

    I bet you're waiting on this update, huh? :p

    Well I just wanted to say that I've successfully self diagnosed my BSOD problem. It took a lot of hard work...., countless hours of scouring the internet for information... and a lot of trial and error... but I believe my system to be completely stable for the time being.(Been running it for 24 hours, no bsod)


    First things first...
    After the last advice you gave me about running a HD scan, I tried CHKDSK and the Seagate HD tool and I had received no errors. I was gonna come back and ask you what to do next but I decided it would be more efficient to take matters in to my own hands...

    So...

    I downloaded Windows Debugger. I started researching on how to use it and looked back on my prevous minidumps. I tried finding a solution to my usbohci.sys BSOD but kept hitting a wall. Every thread I found on the internet with that same problem was unsolved. I called my friend up and told him to bring his copy of Windows 7 over so I could try a fresh install again. I reformatted my PC with his copy and after Windows was done installing, the first thing I did was disable all windows updates, then, downloaded the AMD chipset driver directly from the AMD website.

    Next, I downloaded my sound card driver(VIA Audio), network interface card driver(Realtek) andlastly my graphics driver all directly from their own websites. Keep in mind, these are all the latest drivers. After rebooting up my pc, I downloaded all the important and recommended windows update excluding the drivers that windows update wanted to install i.e ATK0110 from asus and my mouse, keyboard USB drivers.

    After the windows updates, I installed my Microsoft sidewinder keyboard and Razor Lachesis mouse USB drivers directly from their website.

    I rebooted my pc, used it for a while and still was receiving BSODS. I then downloaded Windows debugger and looked at the most recent minidump....

    This time however, it wasn't the same bsod I was getting before. I was getting new ones like Serial.sys and Usbccgp.sys

    So I thought to myself: "Well I'm doing something right because those are different bsods! I'm going somewhere." :biggrin:

    So I looked up tutorials on how to use Driver Verifier to troubleshoot incompatible drivers. I loaded verifier and checked all third party drivers upon start up. Rebooted my PC and right when after I logged in to windows.... BAM! I got hit with the bluescreen... this time however, it blamed Lachesis.sys

    Odd?I knew right away that was my mouse driver so I rebooted in safemode and uninstalled it. I rebooted back in normal mode and was able to get in. Since I had verifier on, I was confident in my ability to troubleshoot any new bsod that would come up. I kept verifier on and was playing a game, a few hours later I got hit with another BSOD.Verifier identified the problem as Afd.sys

    I googled Afd.sys and found another tech support forum where a person was also having trouble with this bsod. I then found out that Afd.sys is a windows component that deals with networking and if you are receiving this bsod then most likely it is not Afd.sys but the driver that goes through the networking Afd.sys which would be your network interface driver: In my case, Realtek.

    So I thought to myself, "How could this be the case? I have the latest realtek driver from their website..." and then I remember reading an article somewhere that says sometimes motherboard manufacturers will modify or change their drivers they receive from from companies in order to enhance performance and stability.

    I went straight to Asus and downloaded the old 2009 realtek network driver off their website, installed it, and I have not received a single bsod within the last 24 hours. Keep in mind this is with verifier still on :p

    So to conclude this:

    - Latest chipset driver installed
    - Latest graphics driver installed
    - Uninstalled usb mouse driver
    - Latest keyboard driver installed
    - Latest audio driver installed
    - Old manufacturer network driver installed

    I guess we can say that driver updating really is a double edged sword because it can either improve stability or cause incredible instability. The only problem I have now is that after I stopped receiving bsods, I am now experiencing sluggish moments where my audio makes a loud buzzing noise and skips like it's going to bluescreen but doesn't. It also produces high CPU usage and I found the culprit to be audio endpoint builder from looking at my resource monitor but can't find a solution at the moment. :\

    But, yeah! Thank you for sticking with me through this and for anyone else who is reading this in the future:

    MAKE SURE YOU INSTALL YOUR MOBO DRIVERS FIRST AND THEN GRADUALLY UPDATE ONLY IF YOU NEED TO. Also, using windows debugger and verifier helps a whole lot!
     
    Trouble and (deleted member) like this.
  19. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    WOW!
    Thanks for the followup and I'm glad to hear that you have managed to resolve your problem. An excellent job of self troubleshooting, congratulations.
    It's particularly great that you have the self confidence and the skill set to not only install windbg and take a look at your own dumps but that you decided to incorporate DV into your diagnosis.
    Hope to continue to see you around the forum. You can hang out in the BSOD sub-forum and help resolve some crash dumps with your new found skills.
    Best wishes and continued crash free operation.
    Randy
     
    Lisa Huang likes this.
  20. Lisa Huang

    Lisa Huang New Member

    Joined:
    Jun 7, 2012
    Messages:
    22
    Likes Received:
    2
    LOL! Thanks, Randy. :p

    But I'm still a novice and nowhere near to being a tech support expert, yet. :D

    However, I think I'm starting to develop a soft spot for troubleshooting <3
     

Share This Page

Loading...