Windows 10: Varying BSOD's...

Discus and support Varying BSOD's... in Windows 10 BSOD Crashes and Debugging to solve the problem; done. By chance could you tell me if the SMBUS driver is present apparently....."SMBus Driver Version 5.12.0.0031 Release Notes Contents 1... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by 1337comet, May 27, 2016.

  1. 1337comet Win User

    Varying BSOD's...


    done. By chance could you tell me if the SMBUS driver is present apparently....."SMBus Driver
    Version 5.12.0.0031 Release Notes

    Contents

    1 Overview
    2 Required Files
    3 Installation/Uninstallation
    4 Troubleshooting

    1 Overview

    Windows thinks SMBUS as a device and require a driver for it. Therefore, we provide a null driver package, a .inf file without .sys file, to satisfy OS requirements.

    This driver supports Win7 x86/64, Win8.1x64 & Win10 x86/64"....
     
    1337comet, May 29, 2016
    #16
  2. axe0 New Member

    I'm not aware of a driver called smbus, I've never seen a driver with that name...
    There are some drivers with smbus description though.

    Could you clarify where this question comes from?
     
  3. 1337comet Win User
    Third party "driver verifier" I've never heard of one either but I am no computer savant.
     
    1337comet, May 29, 2016
    #18
  4. 1337comet Win User

    Varying BSOD's...

    As well using two different "monitor" programs for systems temps and running mhz and im getting discrepancies between the 2 and windows monitor... will this reflect in the .dmp files? Secifically with my memory...I have 2 differnt brands, PNY (4 sticks total, 2 are 4 gig same make/model, other are PNY (currently one stick in use) 8 gigx2 again same make and model, and i just got my new test memory in the mail x2 4 gig komputer bay (sry if i said kingston earlier) (99925***) others mount with default stats of 99927 (this memory is being detected but does not work on their own for some reason.... (have all these to test the mem modules on the board as well as the memory sticks.)
     
    1337comet, May 29, 2016
    #19
  5. axe0 New Member
    What exactly do you mean with 'will this reflect in the dumps'?

    Make sure that you run 1 brand at a time.
     
  6. 1337comet Win User
    the the dump files show the running freq of the mem and CPU? and yea i know to run same type same size, got a few differnt types for testing purposes
     
    1337comet, May 29, 2016
    #21
  7. axe0 New Member
    Yes
     
  8. 1337comet Win User

    Varying BSOD's...

    Ok I've looked (with sight beyond sight +2 to my noob powa! Varying BSOD's... :p) in a few bsod.dmp's and i cant find it.
     
    1337comet, May 29, 2016
    #23
  9. axe0 New Member
    Enter this command and it'll show, unless mssmbios.sys isn't loaded.
    Code: !sysinfo smbios[/quote] Here is my output from 1 of your dumps with a few commands standard loaded.
    Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffff727c08a3fc8, 2, 1, fffff80312028430} Probably caused by : ntkrnlmp.exe ( nt!RemoveListHeadPte+a0 ) Followup: MachineOwner --------- Processing initial command '!analyze -v;!sysinfo smbios; !sysinfo machineid; !sysinfo cpuspeed; !thread; .bugcheck; .time' 2: kd> !analyze -v;!sysinfo smbios; !sysinfo machineid; !sysinfo cpuspeed; !thread; .bugcheck; .time ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) 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. Arguments: Arg1: fffff727c08a3fc8, 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: fffff80312028430, address which referenced memory Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400 BUILD_VERSION_STRING: 10586.306.amd64fre.th2_release_sec.160422-1850 SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd. SYSTEM_PRODUCT_NAME: To be filled by O.E.M. SYSTEM_SKU: To be filled by O.E.M. SYSTEM_VERSION: To be filled by O.E.M. BIOS_VENDOR: American Megatrends Inc. BIOS_VERSION: F6f BIOS_DATE: 12/10/2014 BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd. BASEBOARD_PRODUCT: 970A-D3P BASEBOARD_VERSION: To be filled by O.E.M. DUMP_TYPE: 2 BUGCHECK_P1: fffff727c08a3fc8 BUGCHECK_P2: 2 BUGCHECK_P3: 1 BUGCHECK_P4: fffff80312028430 WRITE_ADDRESS: fffff8031238f520: Unable to get MiVisibleState fffff727c08a3fc8 CURRENT_IRQL: 2 FAULTING_IP: nt!RemoveListHeadPte+a0 fffff803`12028430 4a8944d308 mov qword ptr [rbx+r10*8+8],rax CPU_COUNT: 6 CPU_MHZ: dbc CPU_VENDOR: AuthenticAMD CPU_FAMILY: 15 CPU_MODEL: 2 CPU_STEPPING: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: AV PROCESS_NAME: WmiPrvSE.exe ANALYSIS_SESSION_HOST: DESKTOP-T4TODAV ANALYSIS_SESSION_TIME: 05-30-2016 21:53:09.0622 ANALYSIS_VERSION: 10.0.10586.567 amd64fre TRAP_FRAME: ffffd0002698e250 -- (.trap 0xffffd0002698e250) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=78031230d0000000 rbx=0000000000000000 rcx=cf81147f80000000 rdx=0000098000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80312028430 rsp=ffffd0002698e3e0 rbp=fffff8031230d600 r8=fffff6e7c078f210 r9=000000000fffffff r10=0000000cf81147f8 r11=fffff8031230d620 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac po nc nt!RemoveListHeadPte+0xa0: fffff803`12028430 4a8944d308 mov qword ptr [rbx+r10*8+8],rax ds:00000067`c08a3fc8=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8031215e2e9 to fffff80312153780 STACK_TEXT: ffffd000`2698e108 fffff803`1215e2e9 : 00000000`0000000a fffff727`c08a3fc8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx ffffd000`2698e110 fffff803`1215cac7 : 00000000`00000000 fffff803`126d1db9 00000000`00000500 fffff803`126c70b1 : nt!KiBugCheckDispatch+0x69 ffffd000`2698e250 fffff803`12028430 : 00000000`000002c0 00000000`00000000 00000000`00000500 00000000`00000000 : nt!KiPageFault+0x247 ffffd000`2698e3e0 fffff803`121e6e33 : 8000ffff`fffff963 00000000`00000000 8000ffff`fffff963 fffff803`00000001 : nt!RemoveListHeadPte+0xa0 ffffd000`2698e420 fffff803`12182aa7 : 00000000`000002c0 00000000`63694d46 ffffe001`00000004 fffff803`00000000 : nt!MmAllocateSpecialPool+0x297 ffffd000`2698e4c0 fffff803`126c6101 : 00000000`00000500 00000000`00000028 ffffe001`49d46b20 ffffd000`2698e570 : nt! ?? ::FNODOBFM::`string'+0x209a7 ffffd000`2698e550 fffff800`456a9592 : 00000000`00000280 00000000`000004f8 00000000`63694d46 00000000`63694d46 : nt!VeAllocatePoolWithTagPriority+0x1e9 ffffd000`2698e5c0 fffff803`126c64f3 : 00000000`63694d46 00000000`000004f8 00000000`00000280 00000000`00000000 : VerifierExt!ExAllocatePoolWithTagPriority_internal_wrapper+0x82 ffffd000`2698e600 fffff800`45558a32 : 00000000`00000000 ffffcf80`d7248880 00000000`00000000 00000000`00000000 : nt!VerifierExAllocatePoolEx+0x4f ffffd000`2698e640 fffff800`45558792 : ffffcf80`d7270c80 ffffe001`4cc2c450 00000000`00000000 ffffd000`2698e720 : FLTMGR!FltpAllocateIrpCtrlInternal+0x292 ffffd000`2698e6a0 fffff800`45585aa1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : FLTMGR!FltpAllocateIrpCtrl+0x12 ffffd000`2698e6e0 fffff803`123cd123 : ffffe001`4d224d70 fffff803`1209c476 ffffe001`4cd80080 ffffffff`00000000 : FLTMGR!FltpFastIoQueryStandardInfo+0xb1 ffffd000`2698e770 fffff803`1240325f : 00000000`00000002 ffffe001`4d224d70 00000000`00000006 00000000`00000000 : nt!FsRtlGetFileSize+0x77 ffffd000`2698e820 fffff803`12402ab9 : ffffd000`2698ea60 00000000`00000000 00000000`00000000 ffffd000`2698ea58 : nt!MiCreateSection+0x68f ffffd000`2698e9f0 fffff803`1215dfa3 : ffffe001`4cd80080 00000042`9e97b748 ffffd000`2698eaa8 00000000`00000000 : nt!NtCreateSection+0x1c9 ffffd000`2698ea90 00007ffb`e3885a24 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000042`9e97b728 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`e3885a24 STACK_COMMAND: kb THREAD_SHA1_HASH_MOD_FUNC: 67d6d97238794a62b4610e990aa97fb6beb9fa20 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 7cc0631e6a4886f48e8db9877a8a78851aaa191d THREAD_SHA1_HASH_MOD: f622fd576a6db9b0a93956f54a32fcdfb727d678 FOLLOWUP_IP: nt!RemoveListHeadPte+a0 fffff803`12028430 4a8944d308 mov qword ptr [rbx+r10*8+8],rax FAULT_INSTR_CODE: d344894a SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!RemoveListHeadPte+a0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 571af445 IMAGE_VERSION: 10.0.10586.306 BUCKET_ID_FUNC_OFFSET: a0 FAILURE_BUCKET_ID: AV_VRF_nt!RemoveListHeadPte BUCKET_ID: AV_VRF_nt!RemoveListHeadPte PRIMARY_PROBLEM_CLASS: AV_VRF_nt!RemoveListHeadPte TARGET_TIME: 2016-05-28T16:25:39.000Z OSBUILD: 10586 OSSERVICEPACK: 0 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 272 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2016-04-23 06:04:21 BUILDDATESTAMP_STR: 160422-1850 BUILDLAB_STR: th2_release_sec BUILDOSVER_STR: 10.0.10586.306.amd64fre.th2_release_sec.160422-1850 ANALYSIS_SESSION_ELAPSED_TIME: 98f ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:av_vrf_nt!removelistheadpte FAILURE_ID_HASH: {6529624b-b675-4796-37f4-1715bea08ec5} Followup: MachineOwner --------- [SMBIOS Data Tables v2.7] [DMI Version - 0] [2.0 Calling Convention - No] [Table Size - 2559 bytes] [BIOS Information (Type 0) - Length 24 - Handle 0000h] Vendor American Megatrends Inc. BIOS Version F6f BIOS Starting Address Segment f000 BIOS Release Date 12/10/2014 BIOS ROM Size 400000 BIOS Characteristics 07: - PCI Supported 11: - Upgradeable FLASH BIOS 12: - BIOS Shadowing Supported 15: - CD-Boot Supported 16: - Selectable Boot Supported 17: - BIOS ROM Socketed 19: - EDD Supported 23: - 1.2MB Floppy Supported 24: - 720KB Floppy Supported 25: - 2.88MB Floppy Supported 26: - Print Screen Device Supported 27: - Keyboard Services Supported 28: - Serial Services Supported 29: - Printer Services Supported 32: - BIOS Vendor Reserved BIOS Characteristic Extensions 00: - ACPI Supported 01: - USB Legacy Supported 08: - BIOS Boot Specification Supported 10: - Specification Reserved 11: - Specification Reserved BIOS Major Revision 4 BIOS Minor Revision 6 EC Firmware Major Revision 255 EC Firmware Minor Revision 255 [System Information (Type 1) - Length 27 - Handle 0001h] Manufacturer Gigabyte Technology Co., Ltd. Product Name To be filled by O.E.M. Version To be filled by O.E.M. Serial Number To be filled by O.E.M. UUID 00000000-0000-0000-0000-000000000000 Wakeup Type Power Switch SKUNumber To be filled by O.E.M. Family To be filled by O.E.M. [BaseBoard Information (Type 2) - Length 15 - Handle 0002h] Manufacturer Gigabyte Technology Co., Ltd. Product 970A-D3P Version To be filled by O.E.M. Serial Number To be filled by O.E.M. Asset Tag Feature Flags 09h -1154334064: - (null) -1154334016: - (null) Location To be filled by O.E.M. Chassis Handle 0003h Board Type 0ah - Processor/Memory Module Number of Child Handles 0 [System Enclosure (Type 3) - Length 22 - Handle 0003h] Manufacturer Gigabyte Technology Co., Ltd. Chassis Type Desktop Version To Be Filled By O.E.M. Serial Number Asset Tag Number Bootup State Safe Power Supply State Safe Thermal State Safe Security Status None OEM Defined 0 Height 0U Number of Power Cords 1 Number of Contained Elements 0 Contained Element Size 0 [Processor Information (Type 4) - Length 42 - Handle 0004h] Socket Designation CPU 1 Processor Type Central Processor Processor Family 3fh - Specification Reserved Processor Manufacturer AMD Processor ID 200f6000fffb8b17 Processor Version AMD FX(tm)-6300 Six-Core Processor Processor Voltage 8ch - 1.2V External Clock 200MHz Max Speed 3500MHz Current Speed 3500MHz Status Enabled Populated Processor Upgrade Specification Reserved L1 Cache Handle 0005h L2 Cache Handle 0006h L3 Cache Handle 0007h Serial Number Asset Tag Number Part Number To Be Filled By O.E.M. [Cache Information (Type 7) - Length 19 - Handle 0005h] Socket Designation L1-Cache Cache Configuration 0180h - WB Enabled Int NonSocketed L1 Maximum Cache Size 0120h - 288K Installed Size 0120h - 288K Supported SRAM Type 0010h - Pipeline-Burst Current SRAM Type 0010h - Pipeline-Burst Cache Speed 1ns Error Correction Type Specification Reserved System Cache Type Unified Associativity 2-way Set-Associative [Cache Information (Type 7) - Length 19 - Handle 0006h] Socket Designation L2-Cache Cache Configuration 0181h - WB Enabled Int NonSocketed L2 Maximum Cache Size 1800h - 6144K Installed Size 1800h - 6144K Supported SRAM Type 0010h - Pipeline-Burst Current SRAM Type 0010h - Pipeline-Burst Cache Speed 1ns Error Correction Type Specification Reserved System Cache Type Unified Associativity 16-way Set-Associative [Cache Information (Type 7) - Length 19 - Handle 0007h] Socket Designation L3-Cache Cache Configuration 0182h - WB Enabled Int NonSocketed L3 Maximum Cache Size 2000h - 8192K Installed Size 2000h - 8192K Supported SRAM Type 0010h - Pipeline-Burst Current SRAM Type 0010h - Pipeline-Burst Cache Speed 1ns Error Correction Type Specification Reserved System Cache Type Unified Associativity Specification Reserved [Memory Controller Information (Type 5) - Length 24 - Handle 0008h] Error Detecting Method 06h - 64-bit ECC Error Correcting Capability 04h - None Supported Interleave 03h - One Way Interleave Current Interleave 03h - One Way Interleave Maximum Memory Module Size 0bh - 2048MB Supported Speeds 000ch - 70ns 60ns Supported Memory Types 0500h - DIMM SDRAM Memory Module Voltage 3.3V Number of Memory Slots 4 Memory Slot Handle 0009h Memory Slot Handle 000ah Memory Slot Handle 000bh Memory Slot Handle 000ch Enabled Err Correcting Caps 04h - None [Memory Module Information (Type 6) - Length 12 - Handle 0009h] Socket Designation DIMM0 Bank Connections 01h - 1 0 Current Speed 1ns Current Memory Type 0500h - DIMM SDRAM Installed Size 1dh - 536870912 [single bank] Enabled Size 1dh - 536870912 [single bank] Error Status 00h - [No Errors] [Memory Module Information (Type 6) - Length 12 - Handle 000ah] Socket Designation DIMM1 Bank Connections 23h - 3 2 Current Speed 35ns Current Memory Type 0500h - DIMM SDRAM Installed Size 1dh - 536870912 [single bank] Enabled Size 1dh - 536870912 [single bank] Error Status 00h - [No Errors] [Memory Module Information (Type 6) - Length 12 - Handle 000bh] Socket Designation DIMM2 Bank Connections 45h - 5 4 Current Speed 69ns Current Memory Type 0500h - DIMM SDRAM Installed Size 1dh - 536870912 [single bank] Enabled Size 1dh - 536870912 [single bank] Error Status 00h - [No Errors] [Memory Module Information (Type 6) - Length 12 - Handle 000ch] Socket Designation DIMM3 Bank Connections 67h - 7 6 Current Speed 103ns Current Memory Type 0500h - DIMM SDRAM Installed Size 1dh - 536870912 [single bank] Enabled Size 1dh - 536870912 [single bank] Error Status 00h - [No Errors] [Onboard Devices Information (Type 10) - Length 6 - Handle 0029h] Number of Devices 1 01: Type Video [enabled] 01: Description To Be Filled By O.E.M. [OEM Strings (Type 11) - Length 5 - Handle 002ah] Number of Strings 5 1 To Be Filled By O.E.M. 2 To Be Filled By O.E.M. 3 To Be Filled By O.E.M. 4 To Be Filled By O.E.M. 5 To Be Filled By O.E.M. [System Configuration Options (Type 12) - Length 5 - Handle 002bh] [Physical Memory Array (Type 16) - Length 23 - Handle 002ch] Location 03h - SystemBoard/Motherboard Use 03h - System Memory Memory Error Correction 03h - None Maximum Capacity 33554432KB Memory Error Inf Handle [Not Provided] Number of Memory Devices 4 [Memory Array Mapped Address (Type 19) - Length 31 - Handle 002dh] Starting Address 00000000h Ending Address 007fffffh Memory Array Handle 002ch Partition Width 255 [Memory Device (Type 17) - Length 34 - Handle 002eh] Physical Memory Array Handle 002ch Memory Error Info Handle [Not Provided] Total Width 0 bits Data Width 64 bits Size [Not Populated] Form Factor 09h - DIMM Device Set [None] Device Locator Node0_Dimm0 Bank Locator Node0_Bank0 Memory Type 02h - Unknown Type Detail 0080h - Synchronous Speed 0MHz Manufacturer Dimm0_Manufacturer Serial Number Asset Tag Number Part Number Dimm0_PartNum [Memory Device (Type 17) - Length 34 - Handle 0030h] Physical Memory Array Handle 002ch Memory Error Info Handle [Not Provided] Total Width 0 bits Data Width 64 bits Size [Not Populated] Form Factor 09h - DIMM Device Set [None] Device Locator Node0_Dimm1 Bank Locator Node0_Bank0 Memory Type 02h - Unknown Type Detail 0080h - Synchronous Speed 0MHz Manufacturer Dimm1_Manufacturer Serial Number Asset Tag Number Part Number Dimm1_PartNum [Memory Device (Type 17) - Length 34 - Handle 0032h] Physical Memory Array Handle 002ch Memory Error Info Handle [Not Provided] Total Width 0 bits Data Width 64 bits Size [Not Populated] Form Factor 09h - DIMM Device Set [None] Device Locator Node0_Dimm2 Bank Locator Node0_Bank0 Memory Type 02h - Unknown Type Detail 0080h - Synchronous Speed 0MHz Manufacturer Dimm2_Manufacturer Serial Number Asset Tag Number Part Number Dimm2_PartNum [Memory Device (Type 17) - Length 34 - Handle 0034h] Physical Memory Array Handle 002ch Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 8192MB Form Factor 09h - DIMM Device Set [None] Device Locator Node0_Dimm3 Bank Locator Node0_Bank0 Memory Type 18h - Specification Reserved Type Detail 4080h - Synchronous Speed 800MHz Manufacturer Undefined Serial Number Asset Tag Number Part Number 8GBH2X04E9992 [Memory Device Mapped Address (Type 20) - Length 35 - Handle 0035h] Starting Address 00000000h Ending Address 007fffffh Memory Device Handle 0034h Mem Array Mapped Adr Handle 002dh Partition Row Position [Unknown] Interleave Position [Unknown] Interleave Data Depth [Unknown] Machine ID Information [From Smbios 2.7, DMIVersion 0, Size=2559] BiosMajorRelease = 4 BiosMinorRelease = 6 BiosVendor = American Megatrends Inc. BiosVersion = F6f BiosReleaseDate = 12/10/2014 SystemManufacturer = Gigabyte Technology Co., Ltd. SystemProductName = To be filled by O.E.M. SystemFamily = To be filled by O.E.M. SystemVersion = To be filled by O.E.M. SystemSKU = To be filled by O.E.M. BaseBoardManufacturer = Gigabyte Technology Co., Ltd. BaseBoardProduct = 970A-D3P BaseBoardVersion = To be filled by O.E.M. sysinfo: unknown error 80004005 GetPointerFromAddress: unable to read from fffff80312390200 THREAD ffffe0014cd80080 Cid 0c78.0e48 Teb: 000000429e164000 Win32Thread: 0000000000000000 RUNNING on processor 2 Impersonation token: ffffc00140f09060 (Level Impersonation) GetUlongFromAddress: unable to read from fffff803122dffa8 Owning Process ffffe0014c7cc840 Image: WmiPrvSE.exe Attached Process N/A Image: N/A fffff78000000000: Unable to get shared data Wait Start TickCount 10679 Context Switch Count 1946 IdealProcessor: 1 ReadMemory error: Cannot get nt!KeMaximumIncrement value. UserTime 00:00:00.000 KernelTime 00:00:00.000 Win32 Start Address 0x00007ffbe380b350 Stack Init ffffd0002698ec90 Current ffffd0002698e3f0 Base ffffd0002698f000 Limit ffffd00026989000 Call 0 Priority 8 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5 Child-SP RetAddr : Args to Child : Call Site ffffd000`2698e108 fffff803`1215e2e9 : 00000000`0000000a fffff727`c08a3fc8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx ffffd000`2698e110 fffff803`1215cac7 : 00000000`00000000 fffff803`126d1db9 00000000`00000500 fffff803`126c70b1 : nt!KiBugCheckDispatch+0x69 ffffd000`2698e250 fffff803`12028430 : 00000000`000002c0 00000000`00000000 00000000`00000500 00000000`00000000 : nt!KiPageFault+0x247 (TrapFrame @ ffffd000`2698e250) ffffd000`2698e3e0 fffff803`121e6e33 : 8000ffff`fffff963 00000000`00000000 8000ffff`fffff963 fffff803`00000001 : nt!RemoveListHeadPte+0xa0 ffffd000`2698e420 fffff803`12182aa7 : 00000000`000002c0 00000000`63694d46 ffffe001`00000004 fffff803`00000000 : nt!MmAllocateSpecialPool+0x297 ffffd000`2698e4c0 fffff803`126c6101 : 00000000`00000500 00000000`00000028 ffffe001`49d46b20 ffffd000`2698e570 : nt! ?? ::FNODOBFM::`string'+0x209a7 ffffd000`2698e550 fffff800`456a9592 : 00000000`00000280 00000000`000004f8 00000000`63694d46 00000000`63694d46 : nt!VeAllocatePoolWithTagPriority+0x1e9 ffffd000`2698e5c0 fffff803`126c64f3 : 00000000`63694d46 00000000`000004f8 00000000`00000280 00000000`00000000 : VerifierExt!ExAllocatePoolWithTagPriority_internal_wrapper+0x82 ffffd000`2698e600 fffff800`45558a32 : 00000000`00000000 ffffcf80`d7248880 00000000`00000000 00000000`00000000 : nt!VerifierExAllocatePoolEx+0x4f ffffd000`2698e640 fffff800`45558792 : ffffcf80`d7270c80 ffffe001`4cc2c450 00000000`00000000 ffffd000`2698e720 : FLTMGR!FltpAllocateIrpCtrlInternal+0x292 ffffd000`2698e6a0 fffff800`45585aa1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : FLTMGR!FltpAllocateIrpCtrl+0x12 ffffd000`2698e6e0 fffff803`123cd123 : ffffe001`4d224d70 fffff803`1209c476 ffffe001`4cd80080 ffffffff`00000000 : FLTMGR!FltpFastIoQueryStandardInfo+0xb1 ffffd000`2698e770 fffff803`1240325f : 00000000`00000002 ffffe001`4d224d70 00000000`00000006 00000000`00000000 : nt!FsRtlGetFileSize+0x77 ffffd000`2698e820 fffff803`12402ab9 : ffffd000`2698ea60 00000000`00000000 00000000`00000000 ffffd000`2698ea58 : nt!MiCreateSection+0x68f ffffd000`2698e9f0 fffff803`1215dfa3 : ffffe001`4cd80080 00000042`9e97b748 ffffd000`2698eaa8 00000000`00000000 : nt!NtCreateSection+0x1c9 ffffd000`2698ea90 00007ffb`e3885a24 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ ffffd000`2698eb00) 00000042`9e97b728 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`e3885a24 Bugcheck code 0000000A Arguments fffff727`c08a3fc8 00000000`00000002 00000000`00000001 fffff803`12028430 Debug session time: Sat May 28 18:25:39.070 2016 (UTC + 2:00) System Uptime: 0 days 0:02:46.861[/quote]
     
  10. 1337comet Win User
    Is this it by chance? Attachment 82451 Its showing that its duel channel but its not running in dual channel mode :S? prob nothing.

    For the most part since yesterdays BSOD while running driver verifier the system has been stable with one ram slot filled...I cant game and I'm still getting random screen freezing....

    Kerbal space program, fry cry 4, LoL all run and sometimes for a good bit but will crash, I have crash reports from KSP (apparently for dev. they request these) would these be helpful at all?
     
    1337comet, May 29, 2016
    #25
  11. axe0 New Member
    Only system dumps do I analyse, others are different.

    So to be clear you've got new BSODs since enabling driver verifier?
     
  12. 1337comet Win User
    Yes, 24hrs into scanning I got a BSOD while gaming, rebooted deactivated verifier, rebooted, and hrs later had another while gaming/school work.
     
    1337comet, May 29, 2016
    #27
  13. axe0 New Member

    Varying BSOD's...

  14. 1337comet Win User
    I am prepping my system for an install of Adobe PS CS6 M.C. Should I wait? I kinda need it for work but I have .......2 other Macbook pros I can work on *Smile
     
    1337comet, May 29, 2016
    #29
  15. axe0 New Member
    Only 1 of the dumps from yesterday was caused by driver verifier but did not flag any driver again.
    This means that the problem is something else than drivers, in most cases it is hardware and in some cases it is something with Windows.





    Varying BSOD's... [​IMG]
    Diagnostic Test
    Varying BSOD's... [​IMG]
    RAM TEST

    Varying BSOD's... [​IMG]
    Run MemTest86+ - Test RAM - Windows 10 Forums


    Varying BSOD's... [​IMG]
    Note
    Varying BSOD's... [​IMG]


    MemTest86+ needs to be run for at least 8 complete 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.

    Make a photo of the result and post it.

    Addition:
    If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
    If errors show up and you see them a lot later, no problem, the errors don't affect the test.
     
Thema:

Varying BSOD's...

Loading...
  1. Varying BSOD's... - Similar Threads - Varying BSOD's

  2. I keep getting frequent and varied BSOD's, How can I fix this?

    in Windows 10 Gaming
    I keep getting frequent and varied BSOD's, How can I fix this?: I am getting BSOD's every now and then up to 1 to 3 times per session.I am getting errors such as: "DPC_WATCHDOG_VIOLATION", "CRITICAL_PROCES_DIED", "ATTEMPTED_WRITE_TO_READONLY_MEMORY", "DRIVER_IRQL_NOT_LESS_OR_EQUAL" and "KMODE_EXCEPTION_NOT_HANDLED".I have tried numerous...
  3. I keep getting frequent and varied BSOD's, How can I fix this?

    in Windows 10 Software and Apps
    I keep getting frequent and varied BSOD's, How can I fix this?: I am getting BSOD's every now and then up to 1 to 3 times per session.I am getting errors such as: "DPC_WATCHDOG_VIOLATION", "CRITICAL_PROCES_DIED", "ATTEMPTED_WRITE_TO_READONLY_MEMORY", "DRIVER_IRQL_NOT_LESS_OR_EQUAL" and "KMODE_EXCEPTION_NOT_HANDLED".I have tried numerous...
  4. I keep getting frequent and varied BSOD's, How can I fix this?

    in Windows 10 BSOD Crashes and Debugging
    I keep getting frequent and varied BSOD's, How can I fix this?: I am getting BSOD's every now and then up to 1 to 3 times per session.I am getting errors such as: "DPC_WATCHDOG_VIOLATION", "CRITICAL_PROCES_DIED", "ATTEMPTED_WRITE_TO_READONLY_MEMORY", "DRIVER_IRQL_NOT_LESS_OR_EQUAL" and "KMODE_EXCEPTION_NOT_HANDLED".I have tried numerous...
  5. BSOD crashes with varying reasons still occuring after replacing RAM

    in Windows 10 BSOD Crashes and Debugging
    BSOD crashes with varying reasons still occuring after replacing RAM: Hi, I've been having this issue for a while where I keep getting blue screens with a variety of different stopcodes, I first did a fresh install of windows on a brand new M.2 drive, but they continued so I thought it might be faulty RAM , so I replaced that but am still...
  6. BSOD crashes with varying reasons still occuring after replacing RAM

    in Windows 10 Gaming
    BSOD crashes with varying reasons still occuring after replacing RAM: Hi, I've been having this issue for a while where I keep getting blue screens with a variety of different stopcodes, I first did a fresh install of windows on a brand new M.2 drive, but they continued so I thought it might be faulty RAM , so I replaced that but am still...
  7. BSOD crashes with varying reasons still occuring after replacing RAM

    in Windows 10 Software and Apps
    BSOD crashes with varying reasons still occuring after replacing RAM: Hi, I've been having this issue for a while where I keep getting blue screens with a variety of different stopcodes, I first did a fresh install of windows on a brand new M.2 drive, but they continued so I thought it might be faulty RAM , so I replaced that but am still...
  8. Frequent BSODs, varying error codes.

    in Windows 10 Gaming
    Frequent BSODs, varying error codes.: Hi,I've been having a lot of BSODs recently, and the error codes have been varying.I've updated all my relevant drivers, windows and BIOS but I can't seem to figure out what's causing them.MinidumpLet me know if there's any more information I need to provide, and thank you in...
  9. Frequent BSODs, varying error codes.

    in Windows 10 Software and Apps
    Frequent BSODs, varying error codes.: Hi,I've been having a lot of BSODs recently, and the error codes have been varying.I've updated all my relevant drivers, windows and BIOS but I can't seem to figure out what's causing them.MinidumpLet me know if there's any more information I need to provide, and thank you in...
  10. BSOD Frequently, Varying Causes. ntkrnlmp.exe, vgk.sys

    in Windows 10 Gaming
    BSOD Frequently, Varying Causes. ntkrnlmp.exe, vgk.sys: I have been freqently bluescreening while gaming over the past couple of days. The reasons have been varying. vgk.sys is Vanguard, the riot client, but this is happening even when vanguard is not installed. Hence ntkrnlmp.exe. I have uploaded a few crash dumps here so...