BSOD 0x3B and 0x1E

Page 6 of 7 FirstFirst ... 4567 LastLast

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

    I am not shocked. As there was a continuous series of Ntfs corruption, you should not have installed Acronis at the first place.
    Code:
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 24, {1904fb, fffff880090e2c98, fffff880090e24f0, fffff88001248f37}
    
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    -------------------------------------------------------------------------------
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
        fffff88001248f2f - Ntfs!NtfsSnapshotScbInternal+12f
        [ 83:c3 ]
    1 error : !Ntfs (fffff88001248f2f)
    Uninstall Acronis right now.

    Display driver is failing.
    Code:
    fffff880`090e1f38  fffff880`0f232c7eUnable to load image nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
     nvlddmkm+0x1abc7e
    Follow Post #18 for it once again.

    Network driver is failing, too. You know, I told about it in the earlier post.
    Code:
    fffff880`090e2168  fffff880`0f05cf12Unable to load image Rt64win7.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
     Rt64win7+0x16f12
    Get it from Realtek. Download the first one from the list: Win7 and WinServer 2008 R2 Driver. Install it by following: Driver Install - Device Manager .

    If the Ntfs BSODs continue to occur even after uninstalling Acronis, change the SATA cables. Then apply it in another SATA port on the motherboard.

    And, dont do anything else other than the suggestions. We need to concentrate on one thing only, that is to find out the root cause behind the Ntfs errors; and nothing else.
      My Computer


  2. Posts : 37
    Windows 7 Home Premium 64bit SP1
    Thread Starter
       #52

    I uninstalled Acronis as soon as you said it was not a good idea to use it. I installed the 314.22 Nvidia driver first off after all the updates and got a Nvidia crash that Driver Verifier caught, so I updated it. Is there a chance the Nvidia card could be going bad? I mean it has memory on it and I don't seem to have problems until I install the drivers for it. With 4 Win 7 re-installs, it is probably a good chance it is hardware failure, right? I do have a new Sata cord but that will have to wait until I get it back.

    I got tired of fooling with it and I know you are frustrated with trying to help me. I sure would be, as this thread is now 6 pages. I'm either doing something COMPLETELY wrong or I need a professional to take a look at it. My spring semester starts on Jan 16, so I need the computer stable. I am currently on my husbands computer so I could let you know what's going on with it. I dropped the computer off with the Geek Squad around 4 this afternoon. I told them all the info I had including symptoms, BSOD errors, steps we took to try to fix it and gave them the link to this thread. They said it will be ready by the 9th but maybe sooner and they would call me if they ran into any serious issues. I have a 1 year plan with them, so I figured it was worth a shot.
      My Computer


  3. Posts : 37
    Windows 7 Home Premium 64bit SP1
    Thread Starter
       #53

    Hello!

    I picked up my computer today. The computer was supposed to be repaired by 1/9/14 but he had not found the problem and called me several times. He finally called me today and said one of my ram sticks was bad (he tested them individually after testing them in pairs and coming up with nothing as I did) and he said he corrected some type of error from not connecting to service. Said it had not BSOD for 12 hours after that and to come get it. He did mention that if I continued having problems that he suspect I had corrupted BIOS even though mine is updated to latest or motherboard is having issues. ( I am not sure, but I "think" my motherboard has dual bios..)

    I came home and set everything up. Not really expecting the problem to be fixed I started the comp up, ran my FFXIV ARR game and just let it sit while I did some chores. I came back to find it on the log in screen and a error message came up in Whocrashed after windows booted up.

    I have uninstalled, cleaned up, and installed Nvidia drivers as mentioned in post #18. I have installed the Realtek network driver as instructed. I am going to shut down the computer and change out the SATA cord then wait and see if it BSOD again.

    UPDATE: I have switched out the SATA cord and changed to another port. This is current SF, Speccy and Screenshot after all the changes. Starting my game back up again to see if it BSOD again.

    Last edited by SekitaLuna; 12 Jan 2014 at 00:20.
      My Computer


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

    A bad RAM may cause those issues, undoubtedly. But I am not 100% sure that replacing RAM will do. Noted that you applied SATA cable to another port. It is definitely a good step.

    Let us know how things go. Best of luck.
      My Computer


  5. Posts : 37
    Windows 7 Home Premium 64bit SP1
    Thread Starter
       #55

    Arc said:
    A bad RAM may cause those issues, undoubtedly. But I am not 100% sure that replacing RAM will do. Noted that you applied SATA cable to another port. It is definitely a good step.

    Let us know how things go. Best of luck.
    I haven't replaced the RAM as of yet, just removed the bad stick +1 good one. Thanks for the well wishes. I have also updated my System Specs.
      My Computer


  6. Posts : 37
    Windows 7 Home Premium 64bit SP1
    Thread Starter
       #56

    Well no BSOD's per say, but the monitor will turn off and the keyboard will lose power but the tower is on. No warning. It has happened twice. No messages on "Who Crashed". All lights will be on within the case on the motherboard (green and red). None are on atm.
      My Computer


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

    Sleep or hibernate :)

    You can easily disable it. Hibernate - Enable or Disable
      My Computer


  8. Posts : 37
    Windows 7 Home Premium 64bit SP1
    Thread Starter
       #58

    Hmm I thought that didn't kick in until you were idle. Turned both to "Never"
      My Computer


  9. Posts : 37
    Windows 7 Home Premium 64bit SP1
    Thread Starter
       #59

    It just did it again, after turning off hibernate earlier, but this time there was a crash log.

    UPDATE: Ran a Admin cmd Chkdsk /f /r and it completed but then didn't want to finish booting. Ran startup recovery and it BSOD with "Referencer by Pointer" 0x18 error but wiped the crash dump with system restore.


    On Sun 1/12/2014 9:44:06 PM GMT your computer crashed

    crash dump file: C:\Windows\Minidump\011214-10764-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0x50 (0xFFFFF0800ABB61A8, 0x0, 0xFFFFF80002A5221B, 0x7)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    Last edited by SekitaLuna; 12 Jan 2014 at 17:17.
      My Computer


  10. Posts : 37
    Windows 7 Home Premium 64bit SP1
    Thread Starter
       #60

    Should I just go ahead and buy a Motherboard + CPU combo?

    On Sun 1/12/2014 11:40:03 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011214-14071-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFFA800792D000)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Mon 1/13/2014 10:05:11 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011314-17175-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0x109 (0xA3A039D898482588, 0xB3B7465EEAC4F4DE, 0xFFFFF80002E31F80, 0x1)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    Last edited by SekitaLuna; 13 Jan 2014 at 07:17.
      My Computer


 
Page 6 of 7 FirstFirst ... 4567 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 12:08.
Find Us