BSOD ntoskrnl.exe+75c40

Page 3 of 5 FirstFirst 12345 LastLast

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

    Run SFC /SCANNOW Command - System File Checker

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Stress test the CPU.
    Hardware - Stress Test With Prime95

    And, give driver verifier another go, when these three are done.
      My Computer


  2. Posts : 28
    Windows 7 Home Premium x64
    Thread Starter
       #22

    Would be nice if it wouldn't bluescreen before the sfc /scannow was done. here's the last minidump.
      My Computer


  3. Posts : 28
    Windows 7 Home Premium x64
    Thread Starter
       #23

    OK, sfc/ scannow didn't find any integrity violations. Will attempt to Stress the GPU and Processor. only question is should i do these at the same time or individually?
      My Computer


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

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff88002f92ce0, 0, 0}
    
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
    Probably caused by : Rt64win7.sys ( Rt64win7+1a0ac )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff88002f92ce0, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003301100
    GetUlongFromAddress: unable to read from fffff800033011c0
     ffffffffffffffff 
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    +0
    fffff880`02f92ce0 083cf9          or      byte ptr [rcx+rdi*8],bh
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    BUGCHECK_STR:  0x1E_c0000005_R
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  sppsvc.exe
    
    CURRENT_IRQL:  2
    
    TAG_NOT_DEFINED_c000000f:  FFFFF88002F94FB0
    
    LAST_CONTROL_TRANSFER:  from fffff8800165b5a7 to fffff8800163f4df
    
    CONTEXT:  fffff88002f93460 -- (.cxr 0xfffff88002f93460)
    rax=fffff8800168a280 rbx=0000000000000000 rcx=fffffa8007bfff00
    rdx=07d2000000000000 rsi=fffffa8007bfff00 rdi=0000000000000011
    rip=fffff8800163f4df rsp=fffff88002f93e40 rbp=fffffa8007bffe10
     r8=0000000000000101  r9=0000000000000000 r10=0000000000000010
    r11=fffff88002f93ff8 r12=07d2000000000000 r13=0000000000000000
    r14=fffffa8007bf8b00 r15=fffff8800176e9a0
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    tcpip!RawReceiveDatagrams+0x1f:
    fffff880`0163f4df 48837a4800      cmp     qword ptr [rdx+48h],0 ds:002b:07d20000`00000048=????????????????
    Resetting default scope
    
    STACK_TEXT:  
    fffff880`02f93e40 fffff880`0165b5a7 : 00000000`00000000 fffffa80`084631a0 fffffa80`07bffe10 fffffa80`07bfff00 : tcpip!RawReceiveDatagrams+0x1f
    fffff880`02f93f40 fffff880`0165b0ba : 00000000`00000000 fffff880`0176e9a0 fffff880`02f940f0 fffffa80`11397c15 : tcpip!IppDeliverListToProtocol+0xf7
    fffff880`02f94000 fffff880`0165a8b4 : fffff880`0176e9a0 fffffa80`08783b10 00000000`00000011 00000000`00000000 : tcpip!IppProcessDeliverList+0x5a
    fffff880`02f940a0 fffff880`0165835f : fffff880`02f942b0 fffffa80`07d20000 fffff880`0176e9a0 00000000`089fb001 : tcpip!IppReceiveHeaderBatch+0x435
    fffff880`02f94180 fffff880`01657952 : fffffa80`084f9630 00000000`00000000 fffffa80`089fb001 00000000`00000001 : tcpip!IpFlcReceivePackets+0x64f
    fffff880`02f94380 fffff880`01656dea : fffffa80`089fb010 fffff880`02f944b0 fffffa80`089fb010 fffff880`00db0000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
    fffff880`02f94460 fffff800`030d4968 : fffffa80`087839e0 00000000`00004800 fffffa80`0746b060 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
    fffff880`02f944b0 fffff880`016574b2 : fffff880`01656d10 fffffa80`06dd5910 00000000`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`02f94590 fffff880`015300eb : fffffa80`089fb8d0 00000000`00000000 fffffa80`084631a0 fffffa80`084631a0 : tcpip!FlReceiveNetBufferListChain+0xb2
    fffff880`02f94600 fffff880`014f9ad6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
    fffff880`02f94670 fffff880`01472cc1 : fffffa80`084631a0 00000000`00000002 00000000`00000001 00000000`00000001 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
    fffff880`02f94af0 fffff880`03ad50ac : fffffa80`08598000 00000000`00000000 00000000`00000000 fffffa80`087839e0 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1
    fffff880`02f94b40 fffffa80`08598000 : 00000000`00000000 00000000`00000000 fffffa80`087839e0 00000000`00000001 : Rt64win7+0x1a0ac
    fffff880`02f94b48 00000000`00000000 : 00000000`00000000 fffffa80`087839e0 00000000`00000001 fffffa80`09d7d410 : 0xfffffa80`08598000
    
    
    FOLLOWUP_IP: 
    Rt64win7+1a0ac
    fffff880`03ad50ac ??              ???
    
    SYMBOL_STACK_INDEX:  c
    
    SYMBOL_NAME:  Rt64win7+1a0ac
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Rt64win7
    
    IMAGE_NAME:  Rt64win7.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  50db313e
    
    STACK_COMMAND:  .cxr 0xfffff88002f93460 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_Rt64win7+1a0ac
    
    BUCKET_ID:  X64_0x1E_c0000005_R_Rt64win7+1a0ac
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm Rt64win7
    start             end                 module name
    fffff880`03abb000 fffff880`03b82000   Rt64win7 T (no symbols)           
        Loaded symbol image file: Rt64win7.sys
        Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
        Image name: Rt64win7.sys
        Timestamp:        Wed Dec 26 22:47:50 2012 (50DB313E)
        CheckSum:         000CDEEE
        ImageSize:        000C7000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    It is blaming the network driver, which is a recent one ..... so there may be something blocking the network.
    Try SFC /SCANNOW : Run in Command Prompt at Boot

    upload your MSINFO32.nfo file.

    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


  5. Posts : 28
    Windows 7 Home Premium x64
    Thread Starter
       #25

    Here you go. Thank you again for the help.
      My Computer


  6. Posts : 28
    Windows 7 Home Premium x64
    Thread Starter
       #26

    GPU test came back, Temp Held steady at 63C. Going to run processor test now.
      My Computer


  7. Posts : 28
    Windows 7 Home Premium x64
    Thread Starter
       #27

    Dump files from blue screen after GPU test, and soon after.
      My Computer


  8. Posts : 1,314
    Windows 7 64-bit
       #28

    Late coming in, but I am curious about a couple of your crashdumps, notably one of your most recent, showing the crash occurred because of a single bit flip (bit of data inadvertently zeroed). There is a possibility this could be caused by a driver bug, but more likely I've found it's from hardware issues, typically from the dread Trio of Trouble - PSU, CPU or motherboard.

    Pardon if I'm just repeating other people's recommendations here, but if you haven't already, you'll want to do a BIOS update, and then reset your BIOS all to factory safe defaults. Some mobos have preset 'normal' settings that are actually overclocked, so set to a safe preset to ensure we're not dealing with something like bad RAM timing/voltage issues.

    Also, I think it's time now to look at that CPU. Run Prime95 for a few hours on Torture Test on Blend settings. Make sure you are aware your CPU cooling is up to the task because Prime95 runs CPU real hot. After that test, regardless of the results, finish up with another lengthy run but on Large FFT settings instead. Report to us the results of each. Send us crashdumps for any crashes that may occur during tests.
      My Computer


  9. Posts : 28
    Windows 7 Home Premium x64
    Thread Starter
       #29

    Bios is latest version out. Not overclocking anything, stock BIOS settings. Voltages all with in manufactures recommendations. Running the Prime95 now.
      My Computer


  10. Posts : 1,314
    Windows 7 64-bit
       #30

    Did you check to make sure the stock settings are actually on a 'safe settings' and not 'normal', if available? Anyways, we'll see how Prime95 goes.
      My Computer


 
Page 3 of 5 FirstFirst 12345 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 07:11.
Find Us