Please ensure Javascript is enabled for purposes of website accessibility Jump to content

jozinzbazin

Members
  • Posts

    5
  • Joined

  • Last visited

Profile Information

  • Registered Products
    2

Recent Profile Visitors

427 profile views

jozinzbazin's Achievements

Rookie

Rookie (2/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. Hello guys, I have hd500x and some problem. After installing the latest drivers I cant change the default buffer size and bit depth from its defaults (1024 and 32 bit) respectively. The onliest param I able to change is buffse suze in the lowest row of UI. Here goes the question - hiw I can overcome this problem btw I have audio from my disply in parallel with line6. Also there is some bluescreens after the pod was plugged in (in the first two minutes). Appreciate any possible help. Thank in advance please help
  2. if you have amd, it's HIGHLY LIKELY you have overclocked the memory. So to overcome your problem you have at least 2 options: 1) reset all your ram settings in bios (speed, voltage, etc) to recommended ones 2) set LLC parameter (load line calibration to more agressive values, eq from 3 to 2). Something like that
  3. First of all thanks for your replies. It seems the problem was caused by page file faults. So first I've checked the operating system pagefiles location (this could be weird assuming I have enough memory to do all the things in the same time). So I've enabled the pagefile on both of my disks manually. The problem has disappered at the moment but who knows...
  4. Not at all, only pod asio drivers Similar problem had been appeared on my friends pod hd pro x. But that time we just thinked it's due to very old hardware of their PC. But in my case I have AMD ryzen system with 32GB memory onboard Here is some exception info derived from memory dump by windbg BASEBOARD_VERSION: DUMP_TYPE: 1 BUGCHECK_P1: 3 BUGCHECK_P2: ffffe10611155e00 BUGCHECK_P3: ffffe10611155d58 BUGCHECK_P4: 0 TRAP_FRAME: ffffe10611155e00 -- (.trap 0xffffe10611155e00) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffbd8c48cf5cb0 rbx=0000000000000000 rcx=0000000000000003 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8023312736c rsp=ffffe10611155f90 rbp=ffffe10611156029 r8=ffff800000000000 r9=ffffad81b7ec1180 r10=0000000000000001 r11=0000000000000002 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po cy nt!ExAllocatePoolWithTag+0x161c: fffff802`3312736c cd29 int 29h Resetting default scope EXCEPTION_RECORD: ffffe10611155d58 -- (.exr 0xffffe10611155d58) ExceptionAddress: fffff8023312736c (nt!ExAllocatePoolWithTag+0x000000000000161c) ExceptionCode: c0000409 (Security check failure or stack buffer overrun) ExceptionFlags: 00000001 NumberParameters: 1 Parameter[0]: 0000000000000003 Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY CPU_COUNT: 10 CPU_MHZ: bb8 CPU_VENDOR: AuthenticAMD CPU_FAMILY: 17 CPU_MODEL: 1 CPU_STEPPING: 1 BUGCHECK_STR: 0x139 PROCESS_NAME: POD HD500X Edit.exe CURRENT_IRQL: 2 DEFAULT_BUCKET_ID: FAIL_FAST_CORRUPT_LIST_ENTRY ERROR_CODE: (NTSTATUS) 0xc0000409 - <Unable to get error code text> EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - <Unable to get error code text> EXCEPTION_CODE_STR: c0000409 EXCEPTION_PARAMETER1: 0000000000000003 ANALYSIS_SESSION_HOST: UZZER-PC ANALYSIS_SESSION_TIME: 08-17-2018 12:27:27.0704 ANALYSIS_VERSION: 10.0.17134.12 amd64fre LAST_CONTROL_TRANSFER: from fffff80232fee9e9 to fffff80232fe30e0 STACK_TEXT: ffffe106`11155ad8 fffff802`32fee9e9 : 00000000`00000139 00000000`00000003 ffffe106`11155e00 ffffe106`11155d58 : nt!KeBugCheckEx ffffe106`11155ae0 fffff802`32feed50 : 00000002`29678000 00000013`00000000 00000000`00000001 00000009`031ff31b : nt!KiBugCheckDispatch+0x69 ffffe106`11155c20 fffff802`32fedd37 : ffffbd8c`53a13c98 00000000`07737800 ffffbd8c`53a13c98 ffffd08e`000000b8 : nt!KiFastFailDispatch+0xd0 ffffe106`11155e00 fffff802`3312736c : ffffffff`ffffff00 00000000`0000e310 0a000004`612f2921 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0xf7 ffffe106`11155f90 fffff802`32f957ff : ffffbd8c`00000000 00000000`00001000 00000000`00000041 00000000`00000000 : nt!ExAllocatePoolWithTag+0x161c ffffe106`11156090 fffff802`8b919508 : 00000000`00000000 00000000`00000000 ffffbd8c`53353b00 ffffbd8c`49748800 : nt!ExAllocatePool+0xf ffffe106`111560c0 fffff802`8b92079d : ffffbd8c`4c58e000 00000000`00001050 ffffbd8c`4c58e000 ffffffff`fe363c80 : L6PODHD5SE64+0x79508 ffffe106`11156140 fffff802`8b91ff5f : ffffbd8c`507b5c40 ffffbd8c`4bdd6630 ffffbd8c`4bac8778 00000000`80000005 : L6PODHD5SE64+0x8079d ffffe106`11156170 fffff802`8b8bbd10 : 00000000`00000000 ffffbd8c`4bdd6630 ffffbd8c`4bac8778 00000000`00000000 : L6PODHD5SE64+0x7ff5f ffffe106`111561a0 fffff802`8b8bb0e4 : 00000000`00000000 ffffbd8c`49748000 ffffbd8c`49748848 ffffe106`11156340 : L6PODHD5SE64+0x1bd10 ffffe106`11156210 fffff802`8b8ba833 : ffffbd8c`4bac8778 00000000`c0000001 00000000`00000824 00000000`00000000 : L6PODHD5SE64+0x1b0e4 ffffe106`11156270 fffff802`8b8a93bf : 00000000`00000000 00000000`00000008 ffffbd8c`49748000 ffff8ff1`43820410 : L6PODHD5SE64+0x1a833 ffffe106`111562d0 fffff802`8b8b6700 : ffff8fc7`ef631238 ffff8fc7`e3f7b188 ffffbd8c`4bac8670 fffff802`32eb92a7 : L6PODHD5SE64+0x93bf ffffe106`11156350 fffff802`8b8a3f76 : ffffbd8c`48e2c5e0 fffff802`8b9672b0 ffffbd8c`49748000 00000000`000001a0 : L6PODHD5SE64+0x16700 ffffe106`11156380 fffff802`8b961e7b : ffffbd8c`48e2c5e0 fffff802`8b96e115 ffffbd8c`48e2c5e0 00000000`00000000 : L6PODHD5SE64+0x3f76 ffffe106`111563b0 fffff802`8b96e5b7 : ffffbd8c`48e2c5e0 ffffbd8c`4bac81a0 00000000`00000105 00000000`00000000 : STREAM!SCIssueRequestToDevice+0x153 ffffe106`11156400 fffff802`8b96ea93 : ffffbd8c`53353ba0 ffffbd8c`53353ba0 ffffbd8c`00000000 00000000`000002aa : STREAM!SCSubmitRequest+0x12f ffffe106`11156470 fffff802`8b9730b7 : 00000000`ffffffff 00000000`00001001 ffffbd8c`4bac8050 ffffbd8c`54d3e010 : STREAM!SCMinidriverDevicePropertyHandler+0xef ffffe106`11156500 fffff802`8cf53e05 : ffffe106`00000005 00000000`00000000 ffffbd8c`4ec9d700 ffffbd8c`4ec9d700 : STREAM!StreamClassMinidriverDeviceGetProperty+0x17 ffffe106`11156530 fffff802`8cf53a0b : 00000000`00000824 fffff802`0000000e ffffbd8c`4f7d01e0 ffffbd8c`53a13d78 : ks!KspPropertyHandler+0x3e5 ffffe106`111565a0 fffff802`8b973250 : ffffbd8c`53a13d78 00000000`008fd824 00000000`00000001 00000000`00001860 : ks!KsPropertyHandler+0x1b ffffe106`111565f0 fffff802`8cf53fe5 : ffffbd8c`54d3e488 ffffbd8c`54d3e010 ffffbd8c`4953f470 00000000`00000000 : STREAM!FilterDispatchIoControl+0xf0 ffffe106`11156630 fffff802`8b962d93 : ffffbd8c`4c6673f0 fffff802`8b082549 00000000`00000000 ffffbd8c`53a13e68 : ks!KsDispatchIrp+0x55 ffffe106`111566f0 fffff802`32eb78d9 : ffffbd8c`54d3e010 ffffe106`111567c0 ffffbd8c`54d3e4d0 ffffbd8c`4c6673e0 : STREAM!StreamClassPassThroughIrp+0x123 ffffe106`11156730 fffff802`8b081529 : ffffbd8c`54d3e010 ffffe106`111567c0 ffffbd8c`54d3e4d0 ffffbd8c`4c6673e0 : nt!IofCallDriver+0x59 ffffe106`11156770 fffff802`8b081023 : ffffbd8c`54d3e010 00000000`00000001 00000000`00000000 ffffbd8c`514d1080 : ksthunk!CKernelFilterDevice::DispatchIrp+0xf9 ffffe106`111567d0 fffff802`32eb78d9 : 00000000`008fd824 fffff802`33385020 00000000`00000000 ffffbd8c`4ba9bc00 : ksthunk!CKernelFilterDevice::DispatchIrpBridge+0x13 ffffe106`11156800 fffff802`3334c55e : ffffbd8c`54d3e010 ffffe106`11156b80 00000000`00000001 00000000`00001000 : nt!IofCallDriver+0x59 ffffe106`11156840 fffff802`3334bd9c : ffffbd8c`00000000 ffffbd8c`514d10d0 00000000`00000000 ffffe106`11156b80 : nt!IopSynchronousServiceTail+0x19e ffffe106`111568f0 fffff802`3334b716 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x66c ffffe106`11156a20 fffff802`32fee553 : 00000000`746c6644 ffffe106`11156b00 00000000`00000000 ffffd08e`a1393480 : nt!NtDeviceIoControlFile+0x56 ffffe106`11156a90 00000000`696c1e5c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`005eeba8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x696c1e5c THREAD_SHA1_HASH_MOD_FUNC: 0890717ebb833bea38bd6ab332f6fe2dfbf535fc THREAD_SHA1_HASH_MOD_FUNC_OFFSET: b317d5f668fd59b3edbfcded6685102a4b090324 THREAD_SHA1_HASH_MOD: 6174dc8a4bb89cc33379cb957eb8bd69f5130297 FOLLOWUP_IP: nt!ExAllocatePool+f fffff802`32f957ff 4883c428 add rsp,28h FAULT_INSTR_CODE: 28c48348 SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: nt!ExAllocatePool+f FOLLOWUP_NAME: Pool_corruption IMAGE_NAME: Pool_Corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: Pool_Corruption STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: f FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_nt!ExAllocatePool BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_nt!ExAllocatePool PRIMARY_PROBLEM_CLASS: 0x139_3_CORRUPT_LIST_ENTRY_nt!ExAllocatePool TARGET_TIME: 2018-08-17T00:27:32.000Z OSBUILD: 16299 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: 2017-10-25 06:06:03 BUILDDATESTAMP_STR: 170928-1534 BUILDLAB_STR: rs3_release BUILDOSVER_STR: 10.0.16299.15.amd64fre.rs3_release.170928-1534 ANALYSIS_SESSION_ELAPSED_TIME: f688 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x139_3_corrupt_list_entry_nt!exallocatepool FAILURE_ID_HASH: {8494215d-b8f8-700d-7fe5-d5e588093d7b} Followup: Pool_corruption ---------
  5. Recently the system has been started to constantly crash with no known reason. The bug is ended in ntoskrnl.exe, but whoscrashed and windbg has suggested the error in the L6PODHD5SE64.sys. The pod is plugged to PC via the usb cable. In most cases the system sound was trough the line6 and there was some daw opened with hd500x asio driver as main sound device. The pod has the latest driver version installed (4.2.7.6) similar to other apps have. The error is 0x00000139 00000000`00000003 ffffe106`11155e00 ffffe106`11155d58 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+1640e0 x64 ntoskrnl.exe+1640e0 Now to the question: how to solve this issue, may be some drivers are available at moment? Any help is appreciated.
×
×
  • Create New...