Unkown BSOD problem


  1. Posts : 2
    Windows 7
       #1

    Unkown BSOD problem


    I built my computer around 1-2 month ago and have been getting some BSOD errors at random times. I found one of them to indicate a memory problem, so i did do a memtest for around 1 day or so and no errors showed up. One problem that I see in all of them using bluescreenview is that ntoskrnl.exe is showing up in almost every error.

    Attached is the .dmp files.
      My Computer


  2. Posts : 13,354
    Windows 7 Professional x64
       #2

    Looks like a hardware problem. Please read this article on your bugcheck 124: https://www.sevenforums.com/crash-loc...-what-try.html

    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

    Try this free stress test: Free Software - GIMPS
    Prime95 Setup:
    - extract the contents of the zip file to a location of your choice
    - double click on the executable file
    - select "Just stress testing"
    - select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
    - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
    The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
    Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
    The Test selection box and the stress.txt file describes what components that the program stresses.
    Please post back with results.

    ...Summary of the Dumps:
    Code:
    
    BugCheck 50, {fffff8a00284b4e0, 0, fffff80003004ee0, 2}
    Probably caused by : fileinfo.sys ( fileinfo!FIStreamLog+89 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck E3, {fffff88000cf5c10, fffffa8003cf1040, 0, 2}
    Probably caused by : CI.dll ( CI!I_FindFileOrHeaderHashInCatalogs+cb )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck 6B, {ffffffffc0000428, 3, 0, 0}
    Probably caused by : ntkrnlmp.exe ( nt!PspLocateSystemDll+13e )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck 1A, {41790, fffffa80034041c0, ffff, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    BugCheck 124, {0, fffffa8004f1f028, be000000, 800400}
    Probably caused by : hardware
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    
      My Computer


  3. Posts : 2
    Windows 7
    Thread Starter
       #3

    I will try out the bugs, but as i have stated in my first post, I did use memtest. All of my memory was fine after 1 whole day of testing.
      My Computer


 

  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:46.
Find Us