Jump to content
AIDA64 Discussion Forum

mathusel

Members
  • Content Count

    1
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mathusel

  • Rank
    Newbie
  1. Hi, I wanted to start AIDA64, but everytime I try, the system chrashes. I don't have the possibility to run the programm normally. I've tried the latest version and also the beta. My system: Microsoft Windows 10 Pro Version 10.0.18363 Build 18363 CPU Intel Core i7-9700K BIOS-Version American Megatrends Inc. A.60, 08.08.2019 BIOS-Modus UEFI BaseBoard-Product MPG Z390 GAMING EDGE AC (MS-7B17) BaseBoard-Version 2.0 RAM 16,0 GB GPU Geforce RTX 2080 MSI Aero Dump: (I have several of them) On Sat 18.04.2020 22:00:22 your computer crashed or a problem was reported crash dump file: C:\Windows\MEMORY.DMP This was probably caused by the following module: storport.sys (storport!memset+0x8280) Bugcheck code: 0xC2 (0x62, 0x0, 0x0, 0x0) Error: BAD_POOL_CALLER file path: C:\Windows\system32\drivers\storport.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Microsoft Storage Port Driver Bug check description: This indicates that the current thread is making a bad pool request. 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 a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK. On Sat 18.04.2020 20:08:20 your computer crashed or a problem was reported crash dump file: C:\Windows\Minidump\041820-8328-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390) Bugcheck code: 0xC2 (0x62, 0x0, 0x0, 0x0) Error: BAD_POOL_CALLER 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 the current thread is making a bad pool request. 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. Does someone know the cause of this problem? Thank you very much.
×
×
  • Create New...