BSOD while playing, ntoskrnl.exe

Page 6 of 10 FirstFirst ... 45678 ... LastLast
  1.    #51

    I just posted just in case anyone else, posts later in this thread, and leave the voltages for now. Use your system as you normally would and then report back the results.
      My Computer


  2. Posts : 60
    Win7 Professional x64
    Thread Starter
       #52

    Two in a row, while computer was booted up and idle. I was not at the computer at the time being.. This might relate to settings on the BIOS. I see that the referenced address was the same in both crashes.. Should i increase vccio and vccsa?
      My Computer

  3.    #53

    Code:
    BugCheck 3B, {c0000005, fffff80002d5c30e, fffff88008d185e0, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1de )
    Code:
    Usual causes:  System service, Device driver, graphics driver, memory
    Update to the latest graphics driver, even if these drivers are beta, then increase the voltages to the recommend values in my last post.
      My Computer


  4. Posts : 60
    Win7 Professional x64
    Thread Starter
       #54

    I switched to running OS off of another SSD aswell, will get the newest drivers aswell.
      My Computer


  5. Posts : 60
    Win7 Professional x64
    Thread Starter
       #55

    Crashed today too, while computer was idle. It's weird, it never happens when I'm using it..


    Will reset BIOS and memory, also downclock DRAM to 1333mhz for now
      My Computer

  6.    #56

    Code:
    BugCheck 50, {fffff6d8b00001c0, 0, fffff80002aa2501, 5}
    
    Could not read faulting driver name
    Probably caused by : memory_corruption ( nt!MiDispatchFault+d1 )
    Code:
    Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
    Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

    Additional Help - Using Driver Verifier to identify issues with Drivers

    Run the Intel CPU test:

    Check for any file system errors and bad sectors using Option #2 of:

    Use this command with Disk Check:

    Code:
    chkdsk C: /f /r
      My Computer


  7. Posts : 60
    Win7 Professional x64
    Thread Starter
       #57

    Hey Blue. Another bluescreen while I was away and computer was idle.. The computer had gone into a bootloop of sorts and BIOS had put a hold on it. I came home and computer was off thinking it had crashed and shut itself down, but weird part is, it shouldn't turn itself off. It should just boot into windows again right?

    So I tried pushing the power button and it wouldn't start! I had to shut it off for a couple seconds, then try again and it booted into bios saying something like "boot failed several times" and then some basic info about drives..

    So, it might be something with power options? The bluescreen is reported as the same time I managed to get the computer running, or just a minute before.. This is weird..

    All bios settings are normal and latest Geforce drivers... Please Advise!
      My Computer

  8.    #58

    Code:
    BugCheck 3B, {c000001d, fffff880016318ad, fffff88003fd0c50, 0}
    
    Probably caused by : memory_corruption
    Code:
    0: kd> !error c000001d
    Error code: (NTSTATUS) 0xc000001d (3221225501) - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.
    What are the results of the above tests?
      My Computer


  9. Posts : 60
    Win7 Professional x64
    Thread Starter
       #59

    ChkDisk came back fine, bluescreened today again while away. Computer won't start the first time i push the power button.. It will start up but peripherals won't get any power, screen is black, mouse and keyboard are both black too.

    Verifier was on while this happened, so hopefully something..
    I am currently setting up Intel Burntest. Will reply
      My Computer

  10.    #60

    Code:
    BugCheck 1A, {888a, fffff9802d126f80, fffff6fcc02f8ec1, fffffa800af1ce50}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+37f50 )
    Code:
    Usual causes:  Device driver, memory, kernel
    Have which used the System File Checker (sfc /scannow)?

    This bugcheck is usually hardware related, but can be caused by drivers and insufficient hard-drive and RAM space to load the operating system.
      My Computer


 
Page 6 of 10 FirstFirst ... 45678 ... 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:47.
Find Us