BSOD on computer after motherboard upgrade

Page 11 of 16 FirstFirst ... 910111213 ... LastLast

  1. Posts : 26,863
    Windows 11 Pro
       #101

    Try putting the ram in the blue slots and enable driver verifier again.

       Warning
    Be sure to create a System Restore point before proceeding further System Restore Point - Create


    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
       Information

    What is Driver Verifier:
    It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.


    What you will notice:
    It will tend to make the computer rather slow and sluggish because the drivers are being stressed.
       Warning

    Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.


       Tip





    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


  2. Posts : 90
    windows 7 pro 64bit sp1
    Thread Starter
       #102

    Ok i will do that then
      My Computer


  3. Posts : 26,863
    Windows 11 Pro
       #103

    Same thing you did before.
      My Computer


  4. Posts : 90
    windows 7 pro 64bit sp1
    Thread Starter
       #104

    upon bootup after switching ram slots got this bsod
      My Computer


  5. Posts : 26,863
    Windows 11 Pro
       #105

    It still says
    Code:
    Use !analyze -v to get detailed debugging information.
    BugCheck 7F, {8, 80050031, 406f8, fffff800034b0918}
    Probably caused by : memory_corruption
    Followup: memory_corruption
    But looking farther says a double trap

    Code:
    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
    I'll get some help with this. Just hold on.
      My Computer


  6. Posts : 26,863
    Windows 11 Pro
       #106

    It's USBSERVIEC E which is from Crystal Rich Ltd USB Safely Remove assistant service

    Code:
    BUGCHECK_STR:  0x7f_8
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    PROCESS_NAME:  USBSRService.e
      My Computer


  7. Posts : 90
    windows 7 pro 64bit sp1
    Thread Starter
       #107

    Ok i have removed any sort of usb safely eject programs so it is back to default windows removal i also happen to notice when i use my usb wifi adapter sometimes my browser will crash i have firefox and chrome if one crashes it will not open back up untill i reboot computer normally i just use the other browser in mean time that is which ever one did not crash at that time for some reason i have a sneaky suspicion that usb might have something to do with alot of my crashes but not sure if it would be bad drivers or something else
      My Computer


  8. Posts : 90
    windows 7 pro 64bit sp1
    Thread Starter
       #108

    Anyway to test/stress usb ports and or drivers to see if it causes any subsiquent crashes
      My Computer


  9. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #109

    EDIT: A double fault with driver verifier enabled.
    Code:
    Verify Flags Level 0x00000000
    
      STANDARD FLAGS:
        [X] (0x00000000) Automatic Checks
    Which points to memory corruption.
    Code:
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    Gives a high notion that the issue is a hardware related.

    Test your RAM modules for possible errors. Run memtest86+ for at least 8 consecutive passes.

    If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

    Stress test the Graphics Card using Furmark. Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

    Stress test the CPU. It saves the result as a .txt file in the prime95's folder. Upload the file for us.

    Disable any overclocks.

    Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

    Let us know the results.
    Last edited by Arc; 09 Jan 2015 at 11:42.
      My Computer


  10. Posts : 3,187
    Main - Windows 7 Pro SP1 64-Bit; 2nd - Windows Server 2008 R2
       #110

    Do everything the others have suggested first - it is good advice. :)

    After that, you might try this: See if you can beg, borrow, buy, or steal a pair of RAM modules and re-test everything with them. You may have all good hardware, just RAM and a motherboard that don't get along. You might also try UNDERclocking your RAM and see what happens. If you're not sure how to do that just ask.
      My Computer


 
Page 11 of 16 FirstFirst ... 910111213 ... 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 03:35.
Find Us