Windows 8 and 8.1 Forums

BSOD random, Different Errors

  1. #1

    Posts : 11
    windows embedded 8.1 industry pro

    BSOD random, Different Errors

    I built my computer about a month ago. Initially, i was only having my computer crash once a week randomly, but these past few days it was more like 2-3 times per day that went to dump which i no longer have and several that created no dump file at all. I caved in did a complete OS restore, but crashes came more often. It has happened about 4 times since I installed the clean OS, one crash did not log a dump file. Once after I had initially installed it, before I was even able to set up the OS.
    So far i have
    - ran memtest86 to 7 passes with no errors
    - chkdisk with no errors
    - HWmonitor does not indicate overheating
    - updated all drivers
    currentlly, i am trying to install the windows 8.1 update files but my PC crashes before they finish downloading.

    Attachment 65983

    Also, i have been getting many display driver has crashed errors that don't crash my PC but they do make my screen go black for a bit while it resets.

    edit: had another BSOD with a different error. Also, disabled XMP and some OC genie button when it was about to start up agian.Attachment 65984
    Last edited by mooretom32; 16 Oct 2015 at 23:51.

      My System SpecsSystem Spec

  2. #2

    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro

    Hi mooretom32,

    Welcome to the 8forums.

    warning   Warning
    Programs that claim to update your drivers install either the wrong or corrupted drivers.
    If you have installed any driver with Driver Booster 3, please remove them as it may cause trouble.

    A 0x1A(MEMORY_MANAGEMENT) is a memory related crash, usually caused by drivers or memory problems (not properly seated, dust and faulty memory)
    In the 0x1A there is a lot of NTFS activity what could point to a failing hard drive
    NTFS = file system
    ffffd000`29deb698 fffff801`bc214461 : 00000000`0000001a 00000000`00005003 fffff799`40000000 00000000`0000c123 : nt!KeBugCheckEx
    ffffd000`29deb6a0 fffff801`bc135ba7 : 00000000`00000001 ffffe002`0024d880 00000000`00000000 00000580`00000000 : nt! ?? ::FNODOBFM::`string'+0x2cfb1
    ffffd000`29deb700 fffff801`bc103f1d : 00000000`00000000 00000000`00000000 ffffd000`29deb9a0 fffff6d8`00f05ac0 : nt!MiMakeSystemCacheRangeValid+0x117
    ffffd000`29deb8a0 fffff801`bc0b02f1 : ffffe002`037c9300 00000007`00000001 00000000`00000028 00000000`00040000 : nt!MmCheckCachedPageStates+0x54d
    ffffd000`29deba40 fffff801`bc41dedf : ffffe002`037c9300 ffffe002`0024d880 ffffc001`0000000e ffffc001`1275ebb0 : nt!CcMapDataForOverwrite+0xf9
    ffffd000`29debac0 fffff801`23104404 : 00000000`00000000 00000000`00040000 00000000`00000008 00000001`00520000 : nt!CcPreparePinWrite+0x73
    ffffd000`29debb80 fffff801`230f8893 : ffffd000`29debf80 ffffc001`02c8a830 00000000`00000088 00000000`00000048 : Ntfs!LfsAllocateLbcb+0x138
    ffffd000`29debbf0 fffff801`230f809e : 00000000`00000000 00000000`00000058 ffffc001`02c8a7a0 00000000`00000058 : Ntfs!LfsPrepareLfcbForLogRecord+0x9b
    ffffd000`29debc20 fffff801`2310cb5f : 00000000`00000000 ffffc001`02baa260 ffffc001`02baa200 00000000`00001000 : Ntfs!LfsWriteLogRecordIntoLogPage+0x33e
    ffffd000`29debcd0 fffff801`231002a2 : ffffd000`29dec502 ffffb002`123cf484 ffffd000`29dec5b0 ffffd000`0226c100 : Ntfs!LfsWrite+0x12f
    ffffd000`29debda0 fffff801`2310d22f : 00000000`00000048 00000000`00000000 00000000`0858f400 00000000`0858f400 : Ntfs!NtfsWriteLog+0xae4
    ffffd000`29debfe0 fffff801`23103515 : ffffc001`1690d010 ffffd000`29dec820 00000000`00000000 ffffd000`29dec378 : Ntfs!NtfsChangeAttributeValue+0x323
    ffffd000`29dec1e0 fffff801`230d5d16 : ffffd000`29dec5b0 ffffc001`1690d010 ffffc001`1690d010 00000000`00000000 : Ntfs!NtfsUpdateStandardInformation+0x2d3
    ffffd000`29dec320 fffff801`230d419e : fffff801`23110e70 ffffc001`1ae79c60 ffffc001`1690d010 ffffd000`29dec5b0 : Ntfs!NtfsModifySecurity+0x276
    ffffd000`29dec460 fffff801`2311fb41 : ffffd000`29dec5b0 ffffe002`046213c0 ffffc001`1690d010 00000000`00000000 : Ntfs!NtfsCommonSetSecurityInfo+0x1d2
    ffffd000`29dec510 fffff801`23121707 : ffffd000`29dec5b0 ffffe002`046213c0 ffffe002`046213c0 00000000`00000000 : Ntfs!NtfsFsdDispatchSwitch+0x131
    ffffd000`29dec590 fffff801`22802cf8 : 00000000`00000000 00000000`00000015 ffffe001`fb7112c0 ffffe002`046213c0 : Ntfs!NtfsFsdDispatch+0x58
    ffffd000`29dec7e0 fffff801`228010b6 : ffffe001`ff0372f0 ffffe002`06049980 ffffe002`046213c0 00000000`00000204 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x258
    ffffd000`29dec880 fffff801`bc44a1b3 : 00000000`00000000 ffffd000`29deca99 ffffe002`06049980 00000000`0000000c : fltmgr!FltpDispatch+0xb6
    ffffd000`29dec8e0 fffff801`bc4a963e : 000000ad`00000201 00000000`9000001f 00000000`01000000 00000000`00000004 : nt!IopGetSetSecurityObject+0x19b
    ffffd000`29dec990 fffff801`bc4a9405 : 00000000`00000014 00000000`9000001f 00000000`9000001f 00000000`00000b60 : nt!ObSetSecurityObjectByPointer+0x5e
    ffffd000`29dec9f0 fffff801`bc1e27b3 : 00000000`00000fe0 ffffe002`0024d880 00000000`00000000 00000000`00000001 : nt!NtSetSecurityObject+0x14d
    ffffd000`29decb00 00007fff`5f7dc3ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    000000ad`9b65e6f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`5f7dc3ca
    The 0xA(IRQL_NOT_LESS_OR_EQUAL) states of memory corruption, but as there was a write activity to the memory this is more likely being caused by a driver.
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arg1: fffffa802adabe08, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff800ba53bd35, address which referenced memory
    FOLLOWUP_NAME:  MachineOwner
    IMAGE_VERSION:  6.3.9600.17031
    IMAGE_NAME:  memory_corruption
    The 0x50(PAGE_FAULT_IN_NON_PAGED_AREA) points to a graphical problem.
    ffffd001`1e65efb8 fffff803`04da20e7 : 00000000`00000050 fffff901`400bfcf0 00000000`00000001 ffffd001`1e65f1a0 : nt!KeBugCheckEx
    ffffd001`1e65efc0 fffff803`04c849c9 : 00000000`00000001 ffffe001`27d7f880 ffffd001`1e65f1a0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x20c37
    ffffd001`1e65f060 fffff803`04d7b22f : 00000000`00000001 00000000`00000000 00000000`00000000 ffffd001`1e65f1a0 : nt!MmAccessFault+0x7a9
    ffffd001`1e65f1a0 fffff960`00842c7c : ffffe001`27096b20 ffffd001`08000000 ffffd001`1a942500 fffff803`04eb16da : nt!KiPageFault+0x12f
    ffffd001`1e65f330 ffffe001`27096b20 : ffffd001`08000000 ffffd001`1a942500 fffff803`04eb16da 00000000`00000000 : cdd+0xdc7c
    ffffd001`1e65f338 ffffd001`08000000 : ffffd001`1a942500 fffff803`04eb16da 00000000`00000000 00000000`00000000 : 0xffffe001`27096b20
    ffffd001`1e65f340 ffffd001`1a942500 : fffff803`04eb16da 00000000`00000000 00000000`00000000 ffffd001`1e65f8ec : 0xffffd001`08000000
    ffffd001`1e65f348 fffff803`04eb16da : 00000000`00000000 00000000`00000000 ffffd001`1e65f8ec ffffc2fb`7f5ef93b : 0xffffd001`1a942500
    ffffd001`1e65f350 fffff800`a6245ab9 : ffffd001`00000174 ffffc000`b67b6128 fffff901`400be020 0000cccc`0000000a : nt!ExAllocatePoolWithTag+0x21a
    ffffd001`1e65f420 fffff800`a6246d61 : ffffe001`26c87000 ffffc000`b67b6010 ffffd001`1a942320 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::OpenLocalAllocation+0x219
    ffffd001`1e65f4c0 fffff800`a62451e3 : ffffc000`b255bb60 ffffc000`b108e9e0 00000000`00000001 fffff803`04c85066 : dxgmms1!VIDMM_GLOBAL::OpenOneAllocation+0x181
    ffffd001`1e65f5b0 fffff800`a60ed73b : ffffc000`b928e2d0 fffff803`04eb259e ffffe001`26bdd560 00000000`4b677844 : dxgmms1!VIDMM_GLOBAL::OpenAllocation+0xb7
    ffffd001`1e65f610 fffff800`a60ecf9c : ffffc000`b6842000 00000000`00000000 ffffc000`b139b1b0 00000000`4b677844 : dxgkrnl!DXGDEVICE::CreateVidMmAllocations<_DXGK_ALLOCATIONINFO>+0x2fb
    ffffd001`1e65f6f0 0000011d`00000400 : ffffe001`27d7f880 ffffe001`27dd8480 ffffc000`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE::CreateAllocation+0x96c
    ffffd001`1e65fe00 ffffe001`27d7f880 : ffffe001`27dd8480 ffffc000`00000000 00000000`00000000 00000000`00000000 : 0x0000011d`00000400
    ffffd001`1e65fe08 ffffe001`27dd8480 : ffffc000`00000000 00000000`00000000 00000000`00000000 0000011d`00000400 : 0xffffe001`27d7f880
    ffffd001`1e65fe10 ffffc000`00000000 : 00000000`00000000 00000000`00000000 0000011d`00000400 fffff901`400bd070 : 0xffffe001`27dd8480
    ffffd001`1e65fe18 00000000`00000000 : 00000000`00000000 0000011d`00000400 fffff901`400bd070 00000000`00000000 : 0xffffc000`00000000
    Please follow instructions below carefully.

    Please uninstall everything of AMD using Display Driver Uninstaller and install new drivers from AMD

    BSOD random, Different Errors Diagnostic Test BSOD random, Different Errors

    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note

    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

    BSOD random, Different Errors Diagnostics Test BSOD random, Different Errors

    Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums

    Note   Note
    Do not run SeaTools on an SSD as the results will be invalid.

    Run chkdsk Disk Check - Windows 7 Help Forums
      My System SpecsSystem Spec

  3. #3

    Posts : 11
    windows embedded 8.1 industry pro

    I ran seatools and passed the smart, short, and long tests.
    Same for WD hardr drive diagnostics tool.
    check disk was also clear
    I had installed amd drivers on my own but i will reinstall.
    Currently uninstalling drivers installed by Driver Booster, although, i was having errors before installing it on my previous OS install. I will run memtest86 to 8 passes, one stick at a time, while I sleep tonight and all day tomorrow for the second stick, if i can.
    Surprisingly, my PC has not crashed while i was running the Hard Drive diagnostics tools.

    edit: finished uninstalling Driver Booster drivers and manually installed needed drivers.

    edit: Ran memtest, No errors after 10 passes. PC has not crashed for about 1 day, will reply again in 1 week to mark as solved if no crashes occur.
    Last edited by mooretom32; 18 Oct 2015 at 10:55.
      My System SpecsSystem Spec

  4. #4

    Posts : 11
    windows embedded 8.1 industry pro

    No BSOD

    My computer crashed again.
    I know it is definitely not a Ram or Hard drive problem because both passed various tests with flying colors.
    No BSOD
    sudden crash while doing Java Hw in Eclipse editor
    last sound i heard was an audio loop
    temps were all well within normal limits. probably. my cpu rarely goes above 42 c during low use and GPU stays at around
    60 c depending on ambient temps
      My System SpecsSystem Spec

  5. #5

    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro

    Hi mooretom32,

    Please DO NOT edit posts after a few hours due to the fact that nobody will get notified when a post is edited.
    As you didn't get a BSOD, please create a new thread at the Performance and Maintenance section
      My System SpecsSystem Spec

  6. #6

    Posts : 11
    windows embedded 8.1 industry pro

    Ok, thanks for your help earlier.
      My System SpecsSystem Spec

BSOD random, Different Errors
Related Threads
New Build: Random Bsod, Multiple errors. in BSOD Crashes and Debugging
65769 Here are the Dmp Files Bsod can happen a couple minutes after startup, it can happen when using Chrome, it can happen when starting up a game. I cannot isolate what exactly triggers them. I have swapped ram around, ran with one, I have used memtest and it found no issues, all drivers...
Over the past month I have been getting both DPC Watchdog Violation BSODs and Bad Pool Header BSODs. I think they are related in some way but I have no idea how. Both seem to happen at relatively random times, but I've notice that they happen more often when I'm playing Hearthstone or browsing...
59725 I've been targeting this problem months on end. Trying various things, i'm about ready to give up and just scrap this computer and buy a new one. I don't want to beg or bother anyone, but I really need help,I spent over a thousand dollars on this PC from newegg. Below are the specs, if...
Random BSoD errors in BSOD Crashes and Debugging
Recently when I was just browsing on my laptop I got a BSoD stating DRIVER_POWER_STATE_FAILURE and the pc restarted and after a few days while waking up my pc i received another BSoD with the message SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.Well I am now baffled and don't know what to do since it my...
Solved Random BSOD errors several times a day. in BSOD Crashes and Debugging
So I got myself a new computer not long ago, and I had some issues with the windows install that gave me 5-6 bsod a day atleast. Managed to fix that issue eventually, but lately it started to pop up with the same thing again, everything from MEMORY_MANAGEMENT to KERNEL_ERROR. Latest one was...
Solved BSOD's at random, multiple errors in BSOD Crashes and Debugging
I've been having fairly frequent, seemingly random BSOD's lately, only major hardware change I've made recently was upgrade my videocard to my current Nvidia GTX 750 Ti. Errors are multiple, including Kernel_Security_Check_Failure, PFN_List_Corrupt, and System_Service_Exception. Ran memory...
random memory errors causing bsod in BSOD Crashes and Debugging
my new machine is bsod at least twice a day, often with the error memory management attached are the zipped files from the diagnostic toll
Eight Forums Android App Eight Forums IOS App Follow us on Facebook