randon bsod every couple days

Page 1 of 2 12 LastLast

  1. Posts : 15
    win7 professional x64
       #1

    randon bsod every couple days


    every so often i get randon bsod from ntoskrnl.exe


    im on windows 7 professional x64

    here is a copy of the dumps

    thanks in advance for your help guys.
      My Computer


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

    Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.
    Code:
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.21490.amd64fre.win7_ldr.130318-1533
    Learn how to install Windows 7 Service Pack 1 (SP1)
    Service Pack Center - Microsoft Windows

    Upload your MSINFO32.nfo file as we need some more information.

    1. Click on the start button
    2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
    3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
    4. Give the time for processing, it will save a .nfo file on your desktop.
    5. Zip it, and upload it following the instruction.
      My Computer


  3. Posts : 15
    win7 professional x64
    Thread Starter
       #3

    i get errors everytime i try to install sp1 so havent installed it
      My Computer


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

    According to Carrona.org, STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
    Usual causes:
    Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack

    You have a lot of possible causes present. But let minimize the possibilities step by step.

    Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus.
    5. Apply > OK
    6. Accept then restart.

    Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

    1. Right click on "my computer" icon and click "manage" on the context menu.
    2. It will open the "computer management" window.
    3. Select "Device Manager" in the left pane, It will list all the existing devices up.
    4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
    5. Select one Intel device item under it, right click, uninstall.
    6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
    7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

    * Uninstall the SCSI adapter that is put by Virtual Clone Drive. I mean uninstall that program.

    No code has to be inserted here.

    Let us know the results.
    _____________________________________________________________________________
    BSOD ANALYSIS:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {8, 80050033, 406f8, fffff800024dc262}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050033
    Arg3: 00000000000406f8
    Arg4: fffff800024dc262
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x7f_8
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff800024ca2e9 to fffff800024cad80
    
    STACK_TEXT:  
    fffff880`02463ce8 fffff800`024ca2e9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
    fffff880`02463cf0 fffff800`024c87b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`02463e30 fffff800`024dc262 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff880`025da000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAcquireInStackQueuedSpinLock+0x2
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiDoubleFaultAbort+b2
    fffff800`024c87b2 90              nop
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5147dc90
    
    FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    
    BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    
    Followup: MachineOwner
    ---------
    comodo
      My Computer


  5. Posts : 15
    win7 professional x64
    Thread Starter
       #5

    ill use this config for a few days and update ifcit happens again. thanks guys.

    now ive just got to figure out how to install sp1 without it restarting pc at15% then bootloop
      My Computer


  6. Posts : 24,479
    Windows 7 Ultimate X64 SP1
       #6

    Some hardware tests to run.

    Hard drive(s)test(s):
    Pick one for your HDD brand or use Seatools.
    7 Free Hard Drive Testing Software Tools

    RAM (memory) test:
    This will require memtest on a bootable CD or USB stick.
    RAM - Test with Memtest86+


    To better help us to help you would you please add your systems specs? Here's the correct way to do it. :SystemInfo See Your System Specs Under System Manufacturer/Model Number add whether it is a desktop or laptop and whether self built. Very important

    Log in to Seven Forums and you will be able to transfer the info directly to the specs page in your profile from within the System Info app.

    After doing this your specs will be available in each of your posts.
    Click on My system Specs in the lower left of this post to see how it should look.:)
    Full instructions are in the tutorial.

    Mainly I want to see what RAM you have. Stop overclocking if you are until we find a solution.
      My Computer


  7. Posts : 15
    win7 professional x64
    Thread Starter
       #7

    Britton30 said:
    Some hardware tests to run.

    Hard drive(s)test(s):
    Pick one for your HDD brand or use Seatools.
    7 Free Hard Drive Testing Software Tools

    RAM (memory) test:
    This will require memtest on a bootable CD or USB stick.
    RAM - Test with Memtest86+


    To better help us to help you would you please add your systems specs? Here's the correct way to do it. :SystemInfo See Your System Specs Under System Manufacturer/Model Number add whether it is a desktop or laptop and whether self built. Very important

    Log in to Seven Forums and you will be able to transfer the info directly to the specs page in your profile from within the System Info app.

    After doing this your specs will be available in each of your posts.
    Click on My system Specs in the lower left of this post to see how it should look.:)
    Full instructions are in the tutorial.

    Mainly I want to see what RAM you have. Stop overclocking if you are until we find a solution.
    did the memtest for 8 hours while i slept, then ive just tried using crystal info and its saying health 100% (as i would exspect for an ssd under 6 months old)
    Last edited by shanky887614; 21 Jun 2013 at 12:14.
      My Computer


  8. Posts : 15
    win7 professional x64
    Thread Starter
       #8

    still getting bsod after doing above. here is new dump
      My Computer


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

    According to Carrona.org, STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
    Usual causes:
    Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack
    Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.
    Code:
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.21490.amd64fre.win7_ldr.130318-1533
    Learn how to install Windows 7 Service Pack 1 (SP1)
    Service Pack Center - Microsoft Windows

    And, you haven't done it all. Intel RST is still present there. Follow my previous post to uninstall it.

    Let us know after doing these two.
    ___________________________________________________________________________
    BSOD ANALYSIS:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {8, 80050033, 406f8, fffff800024c5757}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050033
    Arg3: 00000000000406f8
    Arg4: fffff800024c5757
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x7f_8
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff800024c02e9 to fffff800024c0d80
    
    STACK_TEXT:  
    fffff880`009c5ce8 fffff800`024c02e9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
    fffff880`009c5cf0 fffff800`024be7b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`009c5e30 fffff800`024c5757 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff880`025d9fe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeferredReadyThread+0x2f7
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiDoubleFaultAbort+b2
    fffff800`024be7b2 90              nop
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5147dc90
    
    FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    
    BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    
    Followup: MachineOwner
    ---------
      My Computer


  10. Posts : 15
    win7 professional x64
    Thread Starter
       #10

    i cant install sp1.

    because i get a bsod everytime.

    ive posted that earlier. ive installed all other updates already.

    and talking about intel driver i missed it earlier and have done it now
      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 18:51.
Find Us