APC index mismatch windows 8.1

O

omegaluke

Member
Messages
39
The other day, I uninstalled a program (Firestorm viewer for Second life chat program 64bit version)
install went well (or so i thought). When I opened the program, it crashed and went to a blue screen saying your pc encountered an error and needs to be restarted. see error apc_index_mismatch.

After a restart, I tried the program again and same result....uninstalled and reinstalled with same
result (even tried a slightly older version....not knowing if it was a glitch in the new version or not). That didnt help anything either.

Any help would be soo greatly appreciated.
 

Attachments

  • WEE_BEASTIE-Thu_04_04_2019_101556_65.zip
    1.4 MB · Views: 160

My Computer

System One

  • OS
    8.1
Hi omegaluke,

If this only happens with that particular program, you might want to contact their support. Looking at the dumps I notice I do not have access to the resources to debug this as the resources are private to the vendor of the program.
 

My Computer

System One

  • OS
    Windows 10 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom build
    CPU
    i5-6500 @3.20GHz
    Motherboard
    Gigabyte B150-HD3P-CF
    Memory
    16GB DDR4 2133 Crucial Ballistix Sport LT
    Graphics Card(s)
    MSI GeForce GTX 1060 GAMING X 6G
    Sound Card
    Built-in
    Monitor(s) Displays
    Liyama ProLite XB2483HSU-B2
    Screen Resolution
    1920 x 1080
    Hard Drives
    Crucial MX200 500GB & Toshiba DT01ACA300 3TB
    PSU
    Corsair RM550x
    Case
    Fractal Design Define S
    Cooling
    Cooler Master TX3 i
    Keyboard
    Func KB-460 (MX Red)
    Mouse
    Corsair Gaming M65 RGB
    Browser
    Google Chrome
    Antivirus
    Bitdefender Total Security 2017 + MBAM Pro + MBAE Pro
    Other Info
    Creative Sound Blaster Tactic3D Rage V2 headset
Possibly yes, I imagine you could create a ticket or something and they would just ask you to supply what they need.
 

My Computer

System One

  • OS
    Windows 10 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom build
    CPU
    i5-6500 @3.20GHz
    Motherboard
    Gigabyte B150-HD3P-CF
    Memory
    16GB DDR4 2133 Crucial Ballistix Sport LT
    Graphics Card(s)
    MSI GeForce GTX 1060 GAMING X 6G
    Sound Card
    Built-in
    Monitor(s) Displays
    Liyama ProLite XB2483HSU-B2
    Screen Resolution
    1920 x 1080
    Hard Drives
    Crucial MX200 500GB & Toshiba DT01ACA300 3TB
    PSU
    Corsair RM550x
    Case
    Fractal Design Define S
    Cooling
    Cooler Master TX3 i
    Keyboard
    Func KB-460 (MX Red)
    Mouse
    Corsair Gaming M65 RGB
    Browser
    Google Chrome
    Antivirus
    Bitdefender Total Security 2017 + MBAM Pro + MBAE Pro
    Other Info
    Creative Sound Blaster Tactic3D Rage V2 headset
Ok seems it is now crashing even without the program running....all the logs seem to show this in red. (this is a copy of the most recent dmp as viewed from a program called bluescreenview).

==================================================
Dump File : 041119-67343-01.dmp
Crash Time : 4/11/2019 4:11:36 PM
Bug Check String : APC_INDEX_MISMATCH
Bug Check Code : 0x00000001
Parameter 1 : 00007ffd`c40d07ca
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`0000ffff
Parameter 4 : ffffd000`24aaecc0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1402a0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.19304 (winblue_ltsb_escrow.190305-1818)
Processor : x64
Crash Address : ntoskrnl.exe+1402a0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041119-67343-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 9600
Dump File Size : 294,504
Dump File Time : 4/11/2019 4:14:00 PM
==================================================
 

My Computer

System One

  • OS
    8.1
Whenever you would like to upload information about a crash, please run the DM Log Collector and upload the zip it provides.

Information from programs like Bluescreen viewer and WhoCrashed aren't as much help as actual dumps are, and the zip created by the DM Log Collector provides more information on top of the dumps.
 

My Computer

System One

  • OS
    Windows 10 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom build
    CPU
    i5-6500 @3.20GHz
    Motherboard
    Gigabyte B150-HD3P-CF
    Memory
    16GB DDR4 2133 Crucial Ballistix Sport LT
    Graphics Card(s)
    MSI GeForce GTX 1060 GAMING X 6G
    Sound Card
    Built-in
    Monitor(s) Displays
    Liyama ProLite XB2483HSU-B2
    Screen Resolution
    1920 x 1080
    Hard Drives
    Crucial MX200 500GB & Toshiba DT01ACA300 3TB
    PSU
    Corsair RM550x
    Case
    Fractal Design Define S
    Cooling
    Cooler Master TX3 i
    Keyboard
    Func KB-460 (MX Red)
    Mouse
    Corsair Gaming M65 RGB
    Browser
    Google Chrome
    Antivirus
    Bitdefender Total Security 2017 + MBAM Pro + MBAE Pro
    Other Info
    Creative Sound Blaster Tactic3D Rage V2 headset
axe0 said:
Whenever you would like to upload information about a crash, please run the DM Log Collector and upload the zip it provides.

Information from programs like Bluescreen viewer and WhoCrashed aren't as much help as actual dumps are, and the zip created by the DM Log Collector provides more information on top of the dumps.
Click to expand...

Appologies, when I tried using the dm log collector yesterday it only created an empty zip file, so figured that was the best way to get the log up here. Seems to be working fine now though.
 

Attachments

  • WEE_BEASTIE-Fri_04_12_2019__70605_31.zip
    1.4 MB · Views: 177

My Computer

System One

  • OS
    8.1
Something I noticed in the eventlogs, although they're a few months old, are/were you aware of these?
Code: 
2019-01-06T10:52:03.615		The device, \Device\CdRom1, has a bad block.
2019-01-06T10:52:01.377		The device, \Device\CdRom1, has a bad block.
2019-01-06T10:51:59.117		The device, \Device\CdRom1, has a bad block.
2019-01-06T10:51:56.904		The device, \Device\CdRom1, has a bad block.
2019-01-06T10:51:53.557		The device, \Device\CdRom1, has a bad block.
2019-01-06T10:51:50.426		The device, \Device\CdRom1, has a bad block.
2019-01-06T10:51:48.436		The device, \Device\CdRom1, has a bad block.
2019-01-06T10:51:45.216		The device, \Device\CdRom1, has a bad block.
2019-01-06T10:51:43.187		The device, \Device\CdRom1, has a bad block.
2019-01-06T10:51:39.907		The device, \Device\CdRom1, has a bad block.
2019-01-06T10:51:36.911		The device, \Device\CdRom1, has a bad block.
2019-01-06T10:51:34.954		The device, \Device\CdRom1, has a bad block.
2019-01-06T10:51:32.737		The device, \Device\CdRom1, has a bad block.
2019-01-06T10:51:29.323		The device, \Device\CdRom1, has a bad block.
2019-01-06T10:51:27.041		The device, \Device\CdRom1, has a bad block.
2019-01-06T10:51:24.772		The device, \Device\CdRom1, has a bad block.
2019-01-06T10:51:21.366		The device, \Device\CdRom1, has a bad block.
2019-01-06T10:49:32.450		The device, \Device\CdRom0, has a bad block.
2019-01-06T10:49:30.491		The device, \Device\CdRom0, has a bad block.
2019-01-06T10:49:28.554		The device, \Device\CdRom0, has a bad block.
2019-01-06T10:49:26.572		The device, \Device\CdRom0, has a bad block.
2019-01-06T10:49:24.589		The device, \Device\CdRom0, has a bad block.
2019-01-06T10:49:21.224		The device, \Device\CdRom0, has a bad block.
2019-01-06T10:49:17.989		The device, \Device\CdRom0, has a bad block.
2019-01-06T10:49:15.850		The device, \Device\CdRom0, has a bad block.
2019-01-06T10:49:12.325		The device, \Device\CdRom0, has a bad block.
2019-01-06T10:49:10.111		The device, \Device\CdRom0, has a bad block.
2019-01-06T10:49:06.854		The device, \Device\CdRom0, has a bad block.
2019-01-06T10:49:03.580		The device, \Device\CdRom0, has a bad block.
2019-01-06T10:49:01.415		The device, \Device\CdRom0, has a bad block.
2019-01-06T10:48:59.152		The device, \Device\CdRom0, has a bad block.
2019-01-06T10:48:55.898		The device, \Device\CdRom0, has a bad block.
2019-01-06T10:48:53.884		The device, \Device\CdRom0, has a bad block.
2019-01-06T10:48:51.667		The device, \Device\CdRom0, has a bad block.
2019-01-06T10:48:48.495		The device, \Device\CdRom0, has a bad block.
2019-01-04T12:07:53.788		The device, \Device\Harddisk3\DR5, has a bad block.
2019-01-04T12:07:53.773		The device, \Device\Harddisk3\DR5, has a bad block.
2019-01-04T12:07:53.773		The device, \Device\Harddisk3\DR5, has a bad block.
2018-09-13T23:10:37.268		The device, \Device\Harddisk2\DR36, has a bad block.
2018-09-13T23:10:34.310		The device, \Device\Harddisk2\DR36, has a bad block.
2018-09-13T23:10:30.092		The device, \Device\Harddisk2\DR36, has a bad block.
2018-09-13T23:10:27.185		The device, \Device\Harddisk2\DR36, has a bad block.
2018-09-13T23:10:24.041		The device, \Device\Harddisk2\DR36, has a bad block.
2018-09-13T23:03:40.324		The device, \Device\Harddisk2\DR35, has a bad block.
2018-09-13T23:03:37.366		The device, \Device\Harddisk2\DR35, has a bad block.
2018-09-13T23:03:34.274		The device, \Device\Harddisk2\DR35, has a bad block.
2018-09-13T23:03:31.382		The device, \Device\Harddisk2\DR35, has a bad block.
2018-09-13T23:03:28.218		The device, \Device\Harddisk2\DR35, has a bad block.
2018-09-13T23:03:25.090		The device, \Device\Harddisk2\DR35, has a bad block.
2018-09-13T11:05:57.901		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T11:05:57.535		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T11:05:57.076		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T11:05:56.684		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T11:05:56.061		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T11:02:26.469		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T11:02:20.473		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T11:02:17.498		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T11:02:14.292		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T11:02:11.324		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T10:30:24.360		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T10:30:23.977		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T10:30:23.568		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T10:30:23.119		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T10:30:22.620		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T10:29:56.117		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T10:29:53.189		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T10:29:50.296		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T10:29:47.154		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T10:29:44.221		The device, \Device\Harddisk1\DR33, has a bad block.
2018-09-13T10:24:39.736		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:24:36.851		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:24:33.685		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:24:28.916		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:24:19.129		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:24:16.133		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:24:13.248		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:24:10.062		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:24:07.092		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:23:58.436		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:23:55.481		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:23:52.595		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:23:49.351		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:23:46.453		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:23:40.342		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:23:37.400		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:23:34.208		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:23:31.316		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:23:26.026		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:23:23.015		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:23:18.698		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:23:15.766		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:23:12.564		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:23:09.649		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:21:18.500		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:21:15.603		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:21:12.718		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:21:09.585		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T10:21:06.601		The device, \Device\Harddisk2\DR31, has a bad block.
2018-09-13T09:55:06.519		The device, \Device\Harddisk2\DR30, has a bad block.
2018-09-13T09:55:03.052		The device, \Device\Harddisk2\DR30, has a bad block.
2018-09-13T09:54:57.136		The device, \Device\Harddisk2\DR30, has a bad block.
2018-09-13T09:54:53.985		The device, \Device\Harddisk2\DR30, has a bad block.
2018-09-13T09:54:47.742		The device, \Device\Harddisk2\DR30, has a bad block.
2018-09-13T09:54:44.749		The device, \Device\Harddisk2\DR30, has a bad block.
2018-09-13T09:54:38.741		The device, \Device\Harddisk2\DR30, has a bad block.
2018-08-11T21:31:42.239		The device, \Device\CdRom0, has a bad block.
2018-08-11T21:31:34.379		The device, \Device\CdRom0, has a bad block.
2018-08-11T21:31:27.302		The device, \Device\CdRom0, has a bad block.
2018-08-11T21:31:20.304		The device, \Device\CdRom0, has a bad block.
2018-08-11T21:31:13.643		The device, \Device\CdRom0, has a bad block.
2018-08-11T21:31:06.867		The device, \Device\CdRom0, has a bad block.
2018-08-11T21:31:00.088		The device, \Device\CdRom0, has a bad block.
2018-08-11T21:30:53.225		The device, \Device\CdRom0, has a bad block.
2018-08-11T21:30:46.129		The device, \Device\CdRom0, has a bad block.
2018-08-11T21:30:39.345		The device, \Device\CdRom0, has a bad block.
2018-08-11T21:30:32.532		The device, \Device\CdRom0, has a bad block.
2018-08-11T21:30:25.559		The device, \Device\CdRom0, has a bad block.



I notice the dumps are very consistent, everytime before a crash a call is made to the function nt!IopAllocateIrpPrivate.
As this function is a private function I assume it provides a driver with resources to communicate with other drivers and that it returns the memory address to the resources for the driver to use, based on what I know of the public version.
Luckily, one of the dumps shows which driver the resources are going to, a driver from Avast.
Please remove Avast using their uninstall program :arrow: Avast Uninstall Utility | Download aswClear for Avast Removal
Code: 
0: kd> lmvm aswbidsdriver
Browse full module list
start             end                 module name
fffff801`2a04e000 fffff801`2a08c000   aswbidsdriver T (no symbols)           
    Loaded symbol image file: aswbidsdriver.sys
    Image path: \SystemRoot\system32\drivers\aswbidsdriver.sys
    Image name: aswbidsdriver.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Feb 25 04:49:39 2019 (5C73E463)
    CheckSum:         0003F3BB
    ImageSize:        0003E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
 
Last edited:

My Computer

System One

  • OS
    Windows 10 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom build
    CPU
    i5-6500 @3.20GHz
    Motherboard
    Gigabyte B150-HD3P-CF
    Memory
    16GB DDR4 2133 Crucial Ballistix Sport LT
    Graphics Card(s)
    MSI GeForce GTX 1060 GAMING X 6G
    Sound Card
    Built-in
    Monitor(s) Displays
    Liyama ProLite XB2483HSU-B2
    Screen Resolution
    1920 x 1080
    Hard Drives
    Crucial MX200 500GB & Toshiba DT01ACA300 3TB
    PSU
    Corsair RM550x
    Case
    Fractal Design Define S
    Cooling
    Cooler Master TX3 i
    Keyboard
    Func KB-460 (MX Red)
    Mouse
    Corsair Gaming M65 RGB
    Browser
    Google Chrome
    Antivirus
    Bitdefender Total Security 2017 + MBAM Pro + MBAE Pro
    Other Info
    Creative Sound Blaster Tactic3D Rage V2 headset
Hmmm no, I was not aware of those issues....I dont have a cd rom built in, but instead use an external and also have been known to hook up hard drives via an external enclosure or pin drive use (could that be the hard drive issues they are refering to?) Ok avast has been uninstalled via the avast clear software.
 

My Computer

System One

  • OS
    8.1
Alright, let me know how it goes.
 

My Computer

System One

  • OS
    Windows 10 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom build
    CPU
    i5-6500 @3.20GHz
    Motherboard
    Gigabyte B150-HD3P-CF
    Memory
    16GB DDR4 2133 Crucial Ballistix Sport LT
    Graphics Card(s)
    MSI GeForce GTX 1060 GAMING X 6G
    Sound Card
    Built-in
    Monitor(s) Displays
    Liyama ProLite XB2483HSU-B2
    Screen Resolution
    1920 x 1080
    Hard Drives
    Crucial MX200 500GB & Toshiba DT01ACA300 3TB
    PSU
    Corsair RM550x
    Case
    Fractal Design Define S
    Cooling
    Cooler Master TX3 i
    Keyboard
    Func KB-460 (MX Red)
    Mouse
    Corsair Gaming M65 RGB
    Browser
    Google Chrome
    Antivirus
    Bitdefender Total Security 2017 + MBAM Pro + MBAE Pro
    Other Info
    Creative Sound Blaster Tactic3D Rage V2 headset
seems its still doing it, even with avast removed...what else could be causing it?

also, can i reinstall avast?
 
Last edited:

My Computer

System One

  • OS
    8.1
Without a dump it's nearly impossible to say what could be causing it, could you upload the dump C:\Windows\MEMORY.dmp to onedrive, google drive or dropbox and post a share link in your next post. Please note that you will first have to copy it as accessing the file in its original location can cause some problems, I would recommend to copy using powershell or command prompt (command: copy C:\Windows\MEMORY.dmp "<path to directory you want to copy to>").
 

My Computer

System One

  • OS
    Windows 10 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom build
    CPU
    i5-6500 @3.20GHz
    Motherboard
    Gigabyte B150-HD3P-CF
    Memory
    16GB DDR4 2133 Crucial Ballistix Sport LT
    Graphics Card(s)
    MSI GeForce GTX 1060 GAMING X 6G
    Sound Card
    Built-in
    Monitor(s) Displays
    Liyama ProLite XB2483HSU-B2
    Screen Resolution
    1920 x 1080
    Hard Drives
    Crucial MX200 500GB & Toshiba DT01ACA300 3TB
    PSU
    Corsair RM550x
    Case
    Fractal Design Define S
    Cooling
    Cooler Master TX3 i
    Keyboard
    Func KB-460 (MX Red)
    Mouse
    Corsair Gaming M65 RGB
    Browser
    Google Chrome
    Antivirus
    Bitdefender Total Security 2017 + MBAM Pro + MBAE Pro
    Other Info
    Creative Sound Blaster Tactic3D Rage V2 headset
ok i may be totally dense.......but did command prompt but couldnt locate file......can you please break the steps down simpler for me? sorry to be a pain. thanks
 

My Computer

System One

  • OS
    8.1
Could you check if in the Windows partition, in the Windows folder, there is a file named memory.dmp.
 

My Computer

System One

  • OS
    Windows 10 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom build
    CPU
    i5-6500 @3.20GHz
    Motherboard
    Gigabyte B150-HD3P-CF
    Memory
    16GB DDR4 2133 Crucial Ballistix Sport LT
    Graphics Card(s)
    MSI GeForce GTX 1060 GAMING X 6G
    Sound Card
    Built-in
    Monitor(s) Displays
    Liyama ProLite XB2483HSU-B2
    Screen Resolution
    1920 x 1080
    Hard Drives
    Crucial MX200 500GB & Toshiba DT01ACA300 3TB
    PSU
    Corsair RM550x
    Case
    Fractal Design Define S
    Cooling
    Cooler Master TX3 i
    Keyboard
    Func KB-460 (MX Red)
    Mouse
    Corsair Gaming M65 RGB
    Browser
    Google Chrome
    Antivirus
    Bitdefender Total Security 2017 + MBAM Pro + MBAE Pro
    Other Info
    Creative Sound Blaster Tactic3D Rage V2 headset
Sorry for the delay in response, I've been away for the weekend and only now have found some time.

Please check Dump Files - Configure Windows to Create on BSOD - Windows 7 Help Forums and verify your system settings are configured properly, preferably configured for kernel memory dumps which are memory dumps that contain a large portion of what's available in the memory and are often several hundreds of megabytes up to a few gigabytes in size. It also allows Windows to create mini kernel dumps (often referred to as minidump) which contain the very minimum of what's needed to troubleshoot which often is enough for me. Kernel memory dump is preferred in case it's needed to look more into what happened as minidumps are not always sufficient in finding the cause.
If, for some reason, you can't configure the system to create kernel memory dumps, for example due to limited space available, or because you can't select it, then select mini kernel dumps (small memory dump).
 

My Computer

System One

  • OS
    Windows 10 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom build
    CPU
    i5-6500 @3.20GHz
    Motherboard
    Gigabyte B150-HD3P-CF
    Memory
    16GB DDR4 2133 Crucial Ballistix Sport LT
    Graphics Card(s)
    MSI GeForce GTX 1060 GAMING X 6G
    Sound Card
    Built-in
    Monitor(s) Displays
    Liyama ProLite XB2483HSU-B2
    Screen Resolution
    1920 x 1080
    Hard Drives
    Crucial MX200 500GB & Toshiba DT01ACA300 3TB
    PSU
    Corsair RM550x
    Case
    Fractal Design Define S
    Cooling
    Cooler Master TX3 i
    Keyboard
    Func KB-460 (MX Red)
    Mouse
    Corsair Gaming M65 RGB
    Browser
    Google Chrome
    Antivirus
    Bitdefender Total Security 2017 + MBAM Pro + MBAE Pro
    Other Info
    Creative Sound Blaster Tactic3D Rage V2 headset
ok i tried doing the dump setup, and nothing. I did however on curiosity leave my pc running and observing it.....the random restarts (the ones not caused by running the originally mentioned firestorm viewer) are not going blue screen crash just everything just randomly restarts....could that explain why the dumps arent being created? The issue with the firestorm viewer is still happening whenever that program loads though.
 

My Computer

System One

  • OS
    8.1
Yes, that explains it. Although there are 3 types of crashes (random restarts/shutdown, freezes and BSOD) many confuse them and think every one of them creates dumps while in fact only a BSOD can create a dump file.
 

My Computer

System One

  • OS
    Windows 10 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom build
    CPU
    i5-6500 @3.20GHz
    Motherboard
    Gigabyte B150-HD3P-CF
    Memory
    16GB DDR4 2133 Crucial Ballistix Sport LT
    Graphics Card(s)
    MSI GeForce GTX 1060 GAMING X 6G
    Sound Card
    Built-in
    Monitor(s) Displays
    Liyama ProLite XB2483HSU-B2
    Screen Resolution
    1920 x 1080
    Hard Drives
    Crucial MX200 500GB & Toshiba DT01ACA300 3TB
    PSU
    Corsair RM550x
    Case
    Fractal Design Define S
    Cooling
    Cooler Master TX3 i
    Keyboard
    Func KB-460 (MX Red)
    Mouse
    Corsair Gaming M65 RGB
    Browser
    Google Chrome
    Antivirus
    Bitdefender Total Security 2017 + MBAM Pro + MBAE Pro
    Other Info
    Creative Sound Blaster Tactic3D Rage V2 headset
ok so with regards to the bsod I have been experiencing (will deal with the random restarts later). They only seem to occur when I run that particular program originally mentioned (the firstorm viewer for second life). Is there anything that can be done about that?
 

My Computer

System One

  • OS
    8.1
You must log in or register to reply here.
Back
Top