Windows 8 and 8.1 Forums


Frequent BSOD in and out of games, errors vary

  1. #1


    Posts : 5
    Windows 10 (Build 9926)

    Frequent BSOD in and out of games, errors vary


    Hello all!

    One of my PCs is having pretty frequent BSODs (a few times a day), can happen with just the desktop and no programs open or whilst playing games.

    I originally thought this was a memory issue so did a memtest, got 9 passes so stopped it after that. HDD appears to be fine too (this is also all new hardware, purchased in november '14).
    The most common errors it pops up with are Kernel security check failure and IRQ_not_less_or_equal.

    The OS is Windows 10, however this also happened on 8.1 initially (I don't expect 10 to be stable, I'm happy to deal with it if something just isn't compatible - but would like to check if there's something I can do first!
    ). My other 2 PCs run W10 like a dream but they're all different hardware.

    Here are the logs:
    Attachment 58676


    Thank you!

      My System SpecsSystem Spec

  2. #2


    Posts : 2,480
    Windows 10 Pro x64


    Test your RAM: RAM - Test with Memtest86+ - Windows 7 Help Forums
    one stick at a time eight passes per stick.
      My System SpecsSystem Spec

  3. #3


    Posts : 5
    Windows 10 (Build 9926)


    Thank you softwaremaniac! I have already tested both sticks individually, both for 9 passes. Any other suggestions?
      My System SpecsSystem Spec

  4. #4


    Posts : 2,480
    Windows 10 Pro x64


    It could be the issue within W10 if using different software than on the two other machines. What AV are you using?
      My System SpecsSystem Spec

  5. #5


    Posts : 5
    Windows 10 (Build 9926)


    No AV (for testing purposes). This also happened on 8.1
    Could this be a driver issue? I would normally use whocrashed to see what driver it could be but it doesn't work on W10 yet :/
      My System SpecsSystem Spec

  6. #6


    Posts : 2,480
    Windows 10 Pro x64


    That's my point. It is most likely a driver issue as I can see a bunch o things that cannot be started. W10 is not yet safe to use because it has problems.
      My System SpecsSystem Spec

  7. #7


    Posts : 5
    Windows 10 (Build 9926)


    Yes I realise 10 is not stable yet, but these exact bsods were happening on with 8.1 (same machine). So its not necessarily a W10 issue as a whole anyway. Any idea what drivers I could try updating/changing specifically?
    Thank you for taking the time to help
      My System SpecsSystem Spec

  8. #8


    Posts : 2,480
    Windows 10 Pro x64


    Well, if it happened on W8.1 too then it might not be a driver issue. I'd go ahead and start HW diag: Hardware Diagnostics
    Uninstall software related to drivers in red.
    Code:
    wdcsam64.sys Wed Apr 16 10:39:08 2008  (4805BB2C) 
    
    wdcsam64.sys - this driver hasn't been added to the DRT as  of this run. Please search Google/Bing for the driver if additional information  is needed. 
    
    CAM_Client.sys Sat Jul 26 15:29:37  2008 (488B26C1) 
    Most likely a product that belongs to the  WinRing0 libraries (?from OpenLibSys.org?) - which are known to cause BSOD's in  some Windows systems. I suggest uninstalling this program. 
    http://www.carrona.org/drivers/driver.php?id=CAM_Client.sys 
    
    SiLib.sys  Fri Jul 16 00:08:26 2010 (4C3F86DA) 
    USBXpress Development Kit  
    http://www.carrona.org/drivers/driver.php?id=SiLib.sys 
    
    SiUSBXp.sys Fri  Jul 16 00:27:13 2010 (4C3F8B41) 
    Silicone Labs USBXpress  Development Kit 
    http://www.carrona.org/drivers/driver.php?id=SiUSBXp.sys 
    
    ISCTD64.sys Tue Nov 27 20:52:34  2012 (50B51A02) 
    Intel Smart Connect Technology Driver 
    http://www.carrona.org/drivers/driver.php?id=ISCTD64.sys 
    
    nvhda64v.sys Mon Jul 21 16:17:53  2014 (53CD2111) 
    nVidia HDMI Audio Device (nForce chipset driver) 
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys 
    
    TeeDriverx64.sys Tue Sep 23  22:01:14 2014 (5421D18A) 
    Intel Management Engine Interface driver 
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys 
    
    cpuz138_x64.sys Tue Oct 21  16:36:10 2014 (54466F5A) 
    CPUID CPU-Z Driver 
    http://www.carrona.org/drivers/driver.php?id=cpuz138_x64.sys 
    
    e1i63x64.sys Mon Nov 17  18:41:22 2014 (546A3342) 
    Intel(R) Gigabit Adapter 
    http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys 
    
    nvvad64v.sys Thu Nov 20 16:33:54  2014 (546E09E2) 
    NVIDIA Virtual Audio Driver 
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys 
    
    NvStreamKms.sys Mon Jan 12 18:56:42 2015 (54B40ADA)  
    nVidia Streaming Kernel service - may cause BSOD in  Win8.1 systems (found in May 2014). Date/TimeStamp: Tue Apr 29 20:59:44 2014  (53604B00) MAY NOT BE A PROBLEM, this is a tenative posting - Appears that  April 29 driver is a problem, July 2014 drivers seem OK 
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys 
    
    intelppm.sys Tue Jan 20  05:07:14 2015 (54BDD472) 
    Intel Processor driver 
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys 
    
    nvlddmkm.sys Thu Feb 5 19:01:37  2015 (54D3B001) 
    nVidia Video drivers 
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys 
    
    RTKVHD64.sys Fri Feb 6 10:47:44  2015 (54D48DC0) 
    Realtek High Definition Audio Function Driver 
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys 
    
    
    
    Debug session time: Mon  Mar 2 07:31:33.187 2015 (UTC + 1:00) 
    Loading Dump File  [C:\Users\Mihael\SysnativeBSODApps\030215-11484-01.dmp] 
    Built by:  9926.0.amd64fre.fbl_awesome1501.150119-1648 
    System Uptime: 0 days  2:00:03.835 
    Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )  
    BugCheck 139, {e, ffffd00021c38fe0, ffffd00021c38f38, 0} 
    BugCheck Info:  KERNEL_SECURITY_CHECK_FAILURE  (139) 
    Bugcheck code 00000139 
    Arguments: 
    Arg1: 000000000000000e,  Type of memory safety violation 
    Arg2: ffffd00021c38fe0, Address of the trap  frame for the exception that caused the bugcheck 
    Arg3: ffffd00021c38f38,  Address of the exception record for the exception that caused the bugcheck  
    Arg4: 0000000000000000, Reserved 
    BUGCHECK_STR: 0x139  
    DEFAULT_BUCKET_ID: INVALID_REFERENCE_COUNT 
    PROCESS_NAME: searchui.exe  
    FAILURE_BUCKET_ID: 0x139_e_nt!KiFastFailDispatch 
    MaxSpeed: 3400  
    CurrentSpeed: 3399 
    BiosVersion = P1.90 
    BiosReleaseDate = 12/06/2013  
    SystemManufacturer = To Be Filled By O.E.M. 
    SystemProductName = To Be  Filled By O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Mon Mar 2 05:31:06.716 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030215-11859-01.dmp] 
    Built by:  9926.0.amd64fre.fbl_awesome1501.150119-1648 
    System Uptime: 0 days  4:30:44.364 
    Probably caused by : memory_corruption 
    BugCheck 109,  {a3a01f59a6d227b0, b3b72bdff951632a, fffff8019f61b90c, 1} 
    BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION  (109) 
    Bugcheck code 00000109 
    Arguments: 
    Arg1: a3a01f59a6d227b0,  Reserved 
    Arg2: b3b72bdff951632a, Reserved 
    Arg3: fffff8019f61b90c,  Failure type dependent information 
    Arg4: 0000000000000001, Type of corrupted  region, can be 
    0 : A generic data region 
    1 : Modification of a function  or .pdata 
    2 : A processor IDT 
    3 : A processor GDT 
    4 : Type 1 process  list corruption 
    5 : Type 2 process list corruption 
    6 : Debug routine  modification 
    7 : Critical MSR modification 
    BUGCHECK_STR: 0x109  
    DEFAULT_BUCKET_ID: CODE_CORRUPTION 
    PROCESS_NAME: csrss.exe  
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT 
    MaxSpeed: 3400  
    CurrentSpeed: 3399 
    BiosVersion = P1.90 
    BiosReleaseDate = 12/06/2013  
    SystemManufacturer = To Be Filled By O.E.M. 
    SystemProductName = To Be  Filled By O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Mon Mar 2 01:00:01.883 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030215-11718-01.dmp] 
    Built by:  9926.0.amd64fre.fbl_awesome1501.150119-1648 
    System Uptime: 0 days  1:24:00.531 
    *** WARNING: Unable to verify timestamp for win32k.sys 
    ***  ERROR: Module load completed but symbols could not be loaded for win32k.sys  
    Probably caused by : memory_corruption 
    BugCheck 109, {a3a01f5921a8bb91,  b3b72bdf74265563, fffff8002b696b41, 1} 
    BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION  (109) 
    Bugcheck code 00000109 
    Arguments: 
    Arg1: a3a01f5921a8bb91,  Reserved 
    Arg2: b3b72bdf74265563, Reserved 
    Arg3: fffff8002b696b41,  Failure type dependent information 
    Arg4: 0000000000000001, Type of corrupted  region, can be 
    0 : A generic data region 
    1 : Modification of a function  or .pdata 
    2 : A processor IDT 
    3 : A processor GDT 
    4 : Type 1 process  list corruption 
    5 : Type 2 process list corruption 
    6 : Debug routine  modification 
    7 : Critical MSR modification 
    BUGCHECK_STR: 0x109  
    DEFAULT_BUCKET_ID: CODE_CORRUPTION 
    PROCESS_NAME: System  
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT 
    MaxSpeed: 3400  
    CurrentSpeed: 3399 
    BiosVersion = P1.90 
    BiosReleaseDate = 12/06/2013  
    SystemManufacturer = To Be Filled By O.E.M. 
    SystemProductName = To Be  Filled By O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Sun Mar 1 13:21:58.052 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030115-11687-01.dmp] 
    Built by:  9926.0.amd64fre.fbl_awesome1501.150119-1648 
    System Uptime: 0 days  0:46:35.700 
    Probably caused by : memory_corruption 
    BugCheck 50,  {fffffffffffffffa, 2, fffff8010c61ebd3, 0} 
    BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA  (50) 
    Bugcheck code 00000050 
    Arguments: 
    Arg1: fffffffffffffffa,  memory referenced. 
    Arg2: 0000000000000002, value 0 = read operation, 1 =  write operation. 
    Arg3: fffff8010c61ebd3, If non-zero, the instruction  address which referenced the bad memory 
    address. 
    Arg4: 0000000000000000,  (reserved) 
    BUGCHECK_STR: AV 
    DEFAULT_BUCKET_ID: CODE_CORRUPTION  
    PROCESS_NAME: CAM_Client.exe 
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT 
    MaxSpeed: 3400 
    CurrentSpeed: 3399  
    BiosVersion = P1.90 
    BiosReleaseDate = 12/06/2013 
    SystemManufacturer  = To Be Filled By O.E.M. 
    SystemProductName = To Be Filled By O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Sun Mar 1 10:51:17.703 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030115-11875-01.dmp] 
    Built by:  9926.0.amd64fre.fbl_awesome1501.150119-1648 
    System Uptime: 0 days  5:05:48.352 
    Probably caused by : ntkrnlmp.exe ( nt! ??  ::FNODOBFM::`string'+19688 ) 
    BugCheck 1A, {41201, fffff6800001de08,  ce700009b81f1825, ffffe001b1443f20} 
    BugCheck Info: MEMORY_MANAGEMENT (1a)  
    Bugcheck code 0000001A 
    Arguments: 
    Arg1: 0000000000041201, The  subtype of the bugcheck. 
    Arg2: fffff6800001de08 
    Arg3: ce700009b81f1825  
    Arg4: ffffe001b1443f20 
    BUGCHECK_STR: 0x1a_41201 
    PROCESS_NAME:  CAM_Client.exe 
    FAILURE_BUCKET_ID: 0x1a_41201_nt!_??_::FNODOBFM::_string_  
    MaxSpeed: 3400 
    CurrentSpeed: 3399 
    BiosVersion = P1.90  
    BiosReleaseDate = 12/06/2013 
    SystemManufacturer = To Be Filled By O.E.M.  
    SystemProductName = To Be Filled By O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Sun Mar 1 05:45:07.821 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030115-11484-01.dmp] 
    Built by:  9926.0.amd64fre.fbl_awesome1501.150119-1648 
    System Uptime: 0 days  0:45:09.468 
    *** WARNING: Unable to verify timestamp for win32k.sys 
    ***  ERROR: Module load completed but symbols could not be loaded for win32k.sys  
    Probably caused by : memory_corruption 
    BugCheck 109, {a3a01f59cea6a8c0,  b3b72be0212442a2, fffff80084a1e19e, 1} 
    BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION  (109) 
    Bugcheck code 00000109 
    Arguments: 
    Arg1: a3a01f59cea6a8c0,  Reserved 
    Arg2: b3b72be0212442a2, Reserved 
    Arg3: fffff80084a1e19e,  Failure type dependent information 
    Arg4: 0000000000000001, Type of corrupted  region, can be 
    0 : A generic data region 
    1 : Modification of a function  or .pdata 
    2 : A processor IDT 
    3 : A processor GDT 
    4 : Type 1 process  list corruption 
    5 : Type 2 process list corruption 
    6 : Debug routine  modification 
    7 : Critical MSR modification 
    BUGCHECK_STR: 0x109  
    DEFAULT_BUCKET_ID: CODE_CORRUPTION 
    PROCESS_NAME: System  
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT 
    MaxSpeed: 3400  
    CurrentSpeed: 3399 
    BiosVersion = P1.90 
    BiosReleaseDate = 12/06/2013  
    SystemManufacturer = To Be Filled By O.E.M. 
    SystemProductName = To Be  Filled By O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Sun Mar 1 04:59:29.735 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030115-11546-01.dmp] 
    Built by:  9926.0.amd64fre.fbl_awesome1501.150119-1648 
    System Uptime: 0 days  0:54:15.383 
    Probably caused by : memory_corruption 
    BugCheck 109,  {a3a01f595c76f9c8, b3b72bdfaef493aa, fffff8008c8969cc, 1} 
    BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION  (109) 
    Bugcheck code 00000109 
    Arguments: 
    Arg1: a3a01f595c76f9c8,  Reserved 
    Arg2: b3b72bdfaef493aa, Reserved 
    Arg3: fffff8008c8969cc,  Failure type dependent information 
    Arg4: 0000000000000001, Type of corrupted  region, can be 
    0 : A generic data region 
    1 : Modification of a function  or .pdata 
    2 : A processor IDT 
    3 : A processor GDT 
    4 : Type 1 process  list corruption 
    5 : Type 2 process list corruption 
    6 : Debug routine  modification 
    7 : Critical MSR modification 
    BUGCHECK_STR: 0x109  
    DEFAULT_BUCKET_ID: CODE_CORRUPTION 
    PROCESS_NAME: csrss.exe  
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT 
    MaxSpeed: 3400  
    CurrentSpeed: 3399 
    BiosVersion = P1.90 
    BiosReleaseDate = 12/06/2013  
    SystemManufacturer = To Be Filled By O.E.M. 
    SystemProductName = To Be  Filled By O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Sun Mar 1 04:04:51.034 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030115-11515-01.dmp] 
    Built by:  9926.0.amd64fre.fbl_awesome1501.150119-1648 
    System Uptime: 0 days  2:00:10.684 
    Probably caused by : hardware ( nt!PopQueueTargetDpc+7e )  
    BugCheck A, {752dd, 2, 0, fffff8000c498c8e} 
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL  (a) 
    Bugcheck code 0000000A 
    Arguments: 
    Arg1: 00000000000752dd,  memory referenced 
    Arg2: 0000000000000002, IRQL 
    Arg3: 0000000000000000,  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: fffff8000c498c8e, address which  referenced memory 
    BUGCHECK_STR: AV 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: NF2_CLIENT_Rel 
    FAILURE_BUCKET_ID: IP_MISALIGNED  
    MaxSpeed: 3400 
    CurrentSpeed: 3399 
    BiosVersion = P1.90  
    BiosReleaseDate = 12/06/2013 
    SystemManufacturer = To Be Filled By O.E.M.  
    SystemProductName = To Be Filled By O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Sun Mar 1 02:04:18.327 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030115-11796-01.dmp] 
    Built by:  9926.0.amd64fre.fbl_awesome1501.150119-1648 
    System Uptime: 0 days  2:52:00.193 
    Probably caused by : memory_corruption 
    BugCheck 109,  {a3a01f5944fb7592, b3b72bdf97790f64, fffff803d8696929, 1} 
    BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION  (109) 
    Bugcheck code 00000109 
    Arguments: 
    Arg1: a3a01f5944fb7592,  Reserved 
    Arg2: b3b72bdf97790f64, Reserved 
    Arg3: fffff803d8696929,  Failure type dependent information 
    Arg4: 0000000000000001, Type of corrupted  region, can be 
    0 : A generic data region 
    1 : Modification of a function  or .pdata 
    2 : A processor IDT 
    3 : A processor GDT 
    4 : Type 1 process  list corruption 
    5 : Type 2 process list corruption 
    6 : Debug routine  modification 
    7 : Critical MSR modification 
    BUGCHECK_STR: 0x109  
    DEFAULT_BUCKET_ID: CODE_CORRUPTION 
    PROCESS_NAME: csrss.exe  
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT 
    MaxSpeed: 3400  
    CurrentSpeed: 3399 
    BiosVersion = P1.90 
    BiosReleaseDate = 12/06/2013  
    SystemManufacturer = To Be Filled By O.E.M. 
    SystemProductName = To Be  Filled By O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Sat Feb 28 23:12:01.959 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030115-12375-01.dmp] 
    Built by:  9926.0.amd64fre.fbl_awesome1501.150119-1648 
    System Uptime: 2 days  1:54:45.607 
    Probably caused by : memory_corruption ( ONE_BIT ) 
    BugCheck  1A, {41792, fffff68000108a40, 400000, 0} 
    BugCheck Info: MEMORY_MANAGEMENT (1a)  
    Bugcheck code 0000001A 
    Arguments: 
    Arg1: 0000000000041792, A corrupt  PTE has been detected. Parameter 2 contains the address of 
    the PTE.  Parameters 3/4 contain the low/high parts of the PTE. 
    Arg2: fffff68000108a40  
    Arg3: 0000000000400000 
    Arg4: 0000000000000000 
    BUGCHECK_STR:  0x1a_41792 
    PROCESS_NAME: NF2_CLIENT_Rel 
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT 
    MaxSpeed: 3400 
    CurrentSpeed: 3399  
    BiosVersion = P1.90 
    BiosReleaseDate = 12/06/2013 
    SystemManufacturer  = To Be Filled By O.E.M. 
    SystemProductName = To Be Filled By O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Thu Feb 26 21:16:55.690 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\022715-11703-01.dmp] 
    Built by:  9926.0.amd64fre.fbl_awesome1501.150119-1648 
    System Uptime: 0 days  0:00:38.338 
    *** WARNING: Unable to verify timestamp for cpuz138_x64.sys  
    *** ERROR: Module load completed but symbols could not be loaded for  cpuz138_x64.sys 
    Probably caused by : cpuz138_x64.sys ( cpuz138_x64+2462 )  
    BugCheck 50, {ffffe00000080019, 0, fffff802008c2462, 2} 
    BugCheck Info:  PAGE_FAULT_IN_NONPAGED_AREA  (50) 
    Bugcheck code 00000050 
    Arguments: 
    Arg1: ffffe00000080019,  memory referenced. 
    Arg2: 0000000000000000, value 0 = read operation, 1 =  write operation. 
    Arg3: fffff802008c2462, If non-zero, the instruction  address which referenced the bad memory 
    address. 
    Arg4: 0000000000000002,  (reserved) 
    BUGCHECK_STR: AV 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: CAM_Client.exe 
    FAILURE_BUCKET_ID: AV_cpuz138_x64+2462  
    MaxSpeed: 3400 
    CurrentSpeed: 3399 
    BiosVersion = P1.90  
    BiosReleaseDate = 12/06/2013 
    SystemManufacturer = To Be Filled By O.E.M.  
    SystemProductName = To Be Filled By O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Mon Feb 23 14:47:51.505 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\022415-11921-01.dmp] 
    Built by:  9926.0.amd64fre.fbl_awesome1501.150119-1648 
    System Uptime: 0 days  10:10:00.154 
    *** WARNING: Unable to verify timestamp for win32k.sys 
    ***  ERROR: Module load completed but symbols could not be loaded for win32k.sys  
    Probably caused by : memory_corruption 
    BugCheck 109, {a3a00f58b44b7617,  b3b71bdf06c90fe9, fffff8013d87a710, 1} 
    BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION  (109) 
    Bugcheck code 00000109 
    Arguments: 
    Arg1: a3a00f58b44b7617,  Reserved 
    Arg2: b3b71bdf06c90fe9, Reserved 
    Arg3: fffff8013d87a710,  Failure type dependent information 
    Arg4: 0000000000000001, Type of corrupted  region, can be 
    0 : A generic data region 
    1 : Modification of a function  or .pdata 
    2 : A processor IDT 
    3 : A processor GDT 
    4 : Type 1 process  list corruption 
    5 : Type 2 process list corruption 
    6 : Debug routine  modification 
    7 : Critical MSR modification 
    BUGCHECK_STR: 0x109  
    DEFAULT_BUCKET_ID: CODE_CORRUPTION 
    PROCESS_NAME: csrss.exe  
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT 
    MaxSpeed: 3400  
    CurrentSpeed: 3399 
    BiosVersion = P1.90 
    BiosReleaseDate = 12/06/2013  
    SystemManufacturer = To Be Filled By O.E.M. 
    SystemProductName = To Be  Filled By O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Mon Feb 23 04:37:30.310 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\022315-11453-01.dmp] 
    Built by:  9926.0.amd64fre.fbl_awesome1501.150119-1648 
    System Uptime: 0 days  0:05:03.958 
    *** WARNING: Unable to verify timestamp for cpuz138_x64.sys  
    *** ERROR: Module load completed but symbols could not be loaded for  cpuz138_x64.sys 
    Probably caused by : cpuz138_x64.sys ( cpuz138_x64+2480 )  
    BugCheck 50, {ffffea01c601d307, 0, fffff8004ed12480, 2} 
    BugCheck Info:  PAGE_FAULT_IN_NONPAGED_AREA  (50) 
    Bugcheck code 00000050 
    Arguments: 
    Arg1: ffffea01c601d307,  memory referenced. 
    Arg2: 0000000000000000, value 0 = read operation, 1 =  write operation. 
    Arg3: fffff8004ed12480, If non-zero, the instruction  address which referenced the bad memory 
    address. 
    Arg4: 0000000000000002,  (reserved) 
    BUGCHECK_STR: AV 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: CAM_Client.exe 
    FAILURE_BUCKET_ID: AV_cpuz138_x64+2480  
    MaxSpeed: 3400 
    CurrentSpeed: 3399 
    BiosVersion = P1.90  
    BiosReleaseDate = 12/06/2013 
    SystemManufacturer = To Be Filled By O.E.M.  
    SystemProductName = To Be Filled By O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Mon Feb 23 04:32:05.430 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\022315-11812-01.dmp] 
    Built by:  9926.0.amd64fre.fbl_awesome1501.150119-1648 
    System Uptime: 0 days  17:23:27.932 
    *** WARNING: Unable to verify timestamp for win32k.sys 
    ***  ERROR: Module load completed but symbols could not be loaded for win32k.sys  
    Probably caused by : memory_corruption 
    BugCheck 109, {a3a01f58f49fe6a1,  b3b72bdf471d8073, fffff8018174a8f0, 1} 
    BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION  (109) 
    Bugcheck code 00000109 
    Arguments: 
    Arg1: a3a01f58f49fe6a1,  Reserved 
    Arg2: b3b72bdf471d8073, Reserved 
    Arg3: fffff8018174a8f0,  Failure type dependent information 
    Arg4: 0000000000000001, Type of corrupted  region, can be 
    0 : A generic data region 
    1 : Modification of a function  or .pdata 
    2 : A processor IDT 
    3 : A processor GDT 
    4 : Type 1 process  list corruption 
    5 : Type 2 process list corruption 
    6 : Debug routine  modification 
    7 : Critical MSR modification 
    BUGCHECK_STR: 0x109  
    DEFAULT_BUCKET_ID: CODE_CORRUPTION 
    PROCESS_NAME: System  
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT 
    MaxSpeed: 3400  
    CurrentSpeed: 3399 
    BiosVersion = P1.90 
    BiosReleaseDate = 12/06/2013  
    SystemManufacturer = To Be Filled By O.E.M. 
    SystemProductName = To Be  Filled By O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Sun Feb 22 05:58:36.653 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\022215-12015-01.dmp] 
    Built by:  9926.0.amd64fre.fbl_awesome1501.150119-1648 
    System Uptime: 2 days  3:00:32.301 
    *** WARNING: Unable to verify timestamp for cpuz138_x64.sys  
    *** ERROR: Module load completed but symbols could not be loaded for  cpuz138_x64.sys 
    Probably caused by : cpuz138_x64.sys ( cpuz138_x64+2462 )  
    BugCheck 50, {fffff80000000018, 0, fffff801d14e2462, 2} 
    BugCheck Info:  PAGE_FAULT_IN_NONPAGED_AREA  (50) 
    Bugcheck code 00000050 
    Arguments: 
    Arg1: fffff80000000018,  memory referenced. 
    Arg2: 0000000000000000, value 0 = read operation, 1 =  write operation. 
    Arg3: fffff801d14e2462, If non-zero, the instruction  address which referenced the bad memory 
    address. 
    Arg4: 0000000000000002,  (reserved) 
    BUGCHECK_STR: AV 
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT  
    PROCESS_NAME: CAM_Client.exe 
    FAILURE_BUCKET_ID: AV_cpuz138_x64+2462  
    MaxSpeed: 3400 
    CurrentSpeed: 3399 
    BiosVersion = P1.90  
    BiosReleaseDate = 12/06/2013 
    SystemManufacturer = To Be Filled By O.E.M.  
    SystemProductName = To Be Filled By O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    
    
    
    
    --- E O J --- 2015 Mar 02 21:49:31 PM _88-dbug Copyright  2012 Sysnative Forums 
    --- E O J --- 2015 Mar 02 21:49:31 PM _88-dbug  Copyright 2012 Sysnative Forums 
    --- E O J --- 2015 Mar 02 21:49:31 PM  _88-dbug Copyright 2012 Sysnative Forums
      My System SpecsSystem Spec

  9. #9


    Posts : 5
    Windows 10 (Build 9926)


    Thank you so much Softwaremaniac! I will try these after work today and report back thank you again for your time, I appreciate it!
      My System SpecsSystem Spec

Frequent BSOD in and out of games, errors vary
Related Threads
Hi everyone! Built a new PC a couple of weeks ago and its been a nightmare ever since. I have: Intel i5 4440 CPU ASUS H81M-L motherboard NVIDIA GTX 760 8 gigs of memory, single Kingston stick Corsair VS550 550w PSU
My daughter plays on Friv, a website with hundreds of games, most of them are FLASH based. It frequently creates BSOD on my Win 8.1 desktop computer I'm tried to use Google Chrome and the result is the same. When I look with BlueScreenViewer, I can see it is always the exact same error. ...
BSOD very frequent... please help!!! in BSOD Crashes and Debugging
Hi All: This problem is really frustrating, I executed the updates, check the disk and drivers and it seems to be everything OK. Is if possible somebody check my files, I executed the SF Diagnostic Tools, and I have the results in the .zip I will try to attach. Best Regards and thank you...
frequent BSOD in BSOD Crashes and Debugging
Hi Guys, In the last 24 hours or so I have had maybe 15 BSODs. Most of them seem to be when the cpu is under some sort of load. I downloaded the Intel Processor Diagnostic Tool and this BSODed 3 times out of 5 while running. I did a system restore back to the earliest I could go, before I was...
Frequent BSOD in BSOD Crashes and Debugging
Hi everyone, I experience regular BSOD, in particular just after launching StarCraft 2. It's my new PC (1 month) that i maked myself. I have this problem since the beginning but it's recurrent with SC2. The "message error" of the BSOD is 'DRIVER_IRQL_LESS_OR_EQUAL e22w8x64.sys'. I get...
Hello, windows 8 community. I recently purchased a windows 8 PC, and it has worked well enough so far. however, as of late, I have encountered many error messages citing a shortage of memory, and after a short investigation, I determined that almost half of my RAM is shown as "Modified" in the task...
Solved Frequent BSOD - Various Causes in BSOD Crashes and Debugging
I've been encountering BSODs on a semi-regular basis. It started with my new machine some time last year w/ Win7x64. About 2mo ago I upgraded to Win8 and if anything, they've gotten more frequent. I've run memtest w/ no errors and various video card stress tests w/ no errors, and I'm not...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook