Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Constant BSOD - AMD Ryzen 1600x


  • Please log in to reply
5 replies to this topic

#1 JasonBourne2

JasonBourne2

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:11:17 AM

Posted 26 November 2017 - 12:23 PM

Hello,

I recently built this new rig and I've been getting a lot of BSOD. My windows install is fresh and I have updated all of my drivers that i know of.  I uploaded SysnativeFileCollectionApp.zip to: http://www.filedropper.com/sysnativefilecollectionapp


Speccy: http://speccy.piriform.com/results/YF0w0Cl0IHguqvDp8kQr3Nx

 

I also ran a memory test, with both memory stick in and had no errors, though it didnt finish running. I had no idea how long it takes and when it would stop, but i saw the progression bar reach the end andit had 0 errors.

Your help is appreciated.


Edited by JasonBourne2, 26 November 2017 - 02:15 PM.


BC AdBot (Login to Remove)

 


#2 JasonBourne2

JasonBourne2
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:11:17 AM

Posted 26 November 2017 - 01:31 PM

I also recieved this:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 16299 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff803`14c09000 PsLoadedModuleList = 0xfffff803`14f6afb0
Debug session time: Sun Nov 26 13:22:24.520 2017 (UTC - 5:00)
System Uptime: 0 days 0:01:44.258
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8031e70641f, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff8031e70641f, address which referenced memory

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
fffff8031e70641f

CURRENT_IRQL: 2

FAULTING_IP:
IUFileFilter+641f
fffff803`1e70641f 48c744244000000000 mov qword ptr [rsp+40h],0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR: AV

PROCESS_NAME: UninstallMonit

TRAP_FRAME: ffff9989c7db7c40 -- (.trap 0xffff9989c7db7c40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=c624c184913b0000
rdx=00000000003fb743 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8031e70641f rsp=ffff9989c7db7dd0 rbp=0000000000000000
r8=000000000000692f r9=0000000000d26000 r10=0000000000d25e00
r11=ffffffffffffffff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
IUFileFilter+0x641f:
fffff803`1e70641f 48c744244000000000 mov qword ptr [rsp+40h],0 ss:0018:ffff9989`c7db7e10=ffffc28d25fba010
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80314d789e9 to fffff80314d6d0e0

FAILED_INSTRUCTION_ADDRESS:
IUFileFilter+641f
fffff803`1e70641f 48c744244000000000 mov qword ptr [rsp+40h],0

STACK_TEXT:
ffff9989`c7db7af8 fffff803`14d789e9 : 00000000`0000000a fffff803`1e70641f 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
ffff9989`c7db7b00 fffff803`14d76d7d : ffffede1`4692fdd0 00000000`00000021 ffffedf6`f0a34978 ffffedf6`fb7851a0 : nt!KiBugCheckDispatch+0x69
ffff9989`c7db7c40 fffff803`1e70641f : fffff803`1e706210 00000000`00000000 00000000`0000049b 00000000`00697566 : nt!KiPageFault+0x23d
ffff9989`c7db7dd0 fffff803`1e706210 : 00000000`00000000 00000000`0000049b 00000000`00697566 ffffe800`0087f000 : IUFileFilter+0x641f
ffff9989`c7db7dd8 00000000`00000000 : 00000000`0000049b 00000000`00697566 ffffe800`0087f000 00000000`0974f714 : IUFileFilter+0x6210


STACK_COMMAND: kb

FOLLOWUP_IP:
IUFileFilter+641f
fffff803`1e70641f 48c744244000000000 mov qword ptr [rsp+40h],0

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: IUFileFilter+641f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: IUFileFilter

IMAGE_NAME: IUFileFilter.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 593632e9

FAILURE_BUCKET_ID: X64_AV_VRF_CODE_AV_BAD_IP_IUFileFilter+641f

BUCKET_ID: X64_AV_VRF_CODE_AV_BAD_IP_IUFileFilter+641f



#3 JasonBourne2

JasonBourne2
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:11:17 AM

Posted 26 November 2017 - 04:39 PM

Update: I used the driver verifier method & found out the rzdaendpt.sys,rzpmgrk.sys & rzpnk.sys drivers crash my system right on boot(only when verifier is on). The problem is, these are for my razer mouse, if I delete these files my mouse stops working. If I try to reinstall the drivers, it still crashes. I also received a new error recently:

 

Error: crash dump file: C:\Windows\Minidump\112617-6578-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0xD1 (0xFFFFF843EF373FD6, 0x2, 0x8, 0xFFFFF843EF373FD6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,953 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:12:17 PM

Posted 26 November 2017 - 05:45 PM

Please re-run the Sysnative File Collection App (to collect the latest dumps) and attach them directly HERE in your next reply. To do so, please click Reply to this topic on the top right-side of your topic page. Next, on the bottom, under Attach Files, click Browse..., then click Open, and finally Attach This File. To finalize and post your post, click Add Reply.

 

Thanks.

 

regards,

bwv848

 


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#5 JasonBourne2

JasonBourne2
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:11:17 AM

Posted 01 December 2017 - 03:06 PM

I believe the issue was caused by AMD software clashing with my Nvidia drives. Some how the AMD software app that installs AMD related drivers was installed. Since uninstalling, I haven't had a BSOD. I will upload the file if i receive another one.


Edited by JasonBourne2, 01 December 2017 - 03:07 PM.


#6 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,953 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:12:17 PM

Posted 01 December 2017 - 03:47 PM

Glad to hear that! Let us know whether we can be of further help...


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users