Several different BSODs the past week, completely random.

[MnemonicSyntax]

Hey guys,

So lately I've had several BSODs the past week. I updated my video drivers and everything seemed to be okay, but then I got a new error code (located in dmp file) and then today I received a completely different code, 0x01E.

This occurs randomly, I can't recreate it. Sometimes it happens when playing video games, sometimes it happens while browsing the internet or watching YouTube videos.

I've read the instructions and I believe I have everything in order, apologies in advance if I missed something, please let me know otherwise.

I greatly appreciate anyone's help on this matter, as well as your time.

 

[Arc]

There are multiple different bugcheck codes blaming multiple different things, and one of the dumps is totally uncommon in nature. In this situation it would be better to determine the stability of the RAM at first.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result. A camera snap of the memtest86+ window before closing the program would be nice.

 

[MnemonicSyntax]

Alright, I'll get started on this right away. In the meantime, can you tell me what's being blamed?

I'd surely appreciate it! Thanks!

 

[Arc]

Alright, I'll get started on this right away. In the meantime, can you tell me what's being blamed?

I'd surely appreciate it! Thanks!

Memory Corruption, mostly; and ntkrnlmp (which means the dump recording mechanism failed to get the crasher rightly, and wrongly blamed the karnel itself on which the crash took place).

 

[MnemonicSyntax]

Alright, I ran it all day while at work, came home and checked it, then went to bed, woke up and it had 11 passes with zero errors. Here's the photo you requested as well Arc.

 

[Arc]

Nice!

Then let us check other possibilities .... if there is a failing driver that is passing bad information to the memory, that may result in memory corruption, too. So let us enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[MnemonicSyntax]

You got it, thanks for the help so far! Greatly appreciated!

Getting to work on Pt. 2 now.

 

[MnemonicSyntax]

Well, it's already BSOD'd again. Included is the new dump. :/

Also, I forgot to mention I was running Driver Verifier! Thanks!

 

[MnemonicSyntax]

And another. I was about to click on a YouTube video this time. Using the latest updated Chrome while still running Driver Verifier.

 

[Arc]

None of the last two crash dumps are verifier enabled.

3: kd> !verifier
fffff80003093b80: Unable to get verifier list.

If verifier is enabled, it would have displayed the verifier settings. And, the default bucket ID would also display it, which it does not.

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

Anyway, one is still blaming memory, and the other is IRST. For the IRST issue, you need to get rid of intel rapid/matrix storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

 

[MnemonicSyntax]

When I did Verifier, I selected all drivers except Microsoft ones per the instructions. Could that be why it's not verifier enabled?

As for the Intel thing, uninstalling now.

Thank you so much for your patience with me!

EDIT: It seems my computer restarts now after uninstalling the Intel program, but when I log into Windows it says "Your computer needs to restarted...." and then asks me if I want to restart now or restart later. I selected now, and when I got back into Windows it did it again.

And in Device Manager it looks like it reinstalled the Intel program/driver.

Intel(R) 8 Series/C220 Series SATA AHCI Controller - 8C02

 

[Arc]

The restart configures the new driver.

If you want to verify the new driver, you can do it. In Device manager, right click on the device name, that is "Intel(R) 8 Series/C220 Series SATA AHCI Controller - 8C02" and click on "properties" on the context menu. It will open the properties dialog with the "General" tag selected. Click on the "Driver" tab, and the "Driver details" button. It should show msahci.sys now.

 

[MnemonicSyntax]

Yep, it does.

The restart isn't the problem, it's that it keeps wanting me to restart even after restarting. "You must restart your computer to apply these changes" and "Before restarting, save any open files and close all programs." Then I've got two options, Restart Now and Restart Later. I chose Restart Now and when I logged back in, it gave me the same option again, like the changes didn't actually take. On the second time, I chose Restart Later.

I'll reboot now and see what happens and get back to you.

EDIT: Well, everything seems to be working in the way of the restarting request. Should I run Driver Verifier again?

 

[Arc]

Not right now. First let us see how it works with msahci. If the necessity arises, we will opt for verifier again.

 

[MnemonicSyntax]

Alright, been a while but got a new one. Was browsing the internet today and it BSOD'd while watching videos again on YouTube.

0x19 Bad Pool Header

 

[ICIT2LOL]

Mate the dumps are coming up as hardware ones for me and I am wondering if it is a peripheral that is causing an issue.

Now specifically ( and I have had problems myself with it) have you got a Microsoft keyboard and mouse and if so do they use the Microsoft Intelli Media software - for which there are a few see this listing https://www.microsoft.com/hardware/en-us/downloads

Personally I have had to can the keyboards and mice at times and use another brand.

 

[MnemonicSyntax]

I have a Logitech Keyboard and Mouse. G510s and the Proteus Core to be exact.

 

[ICIT2LOL]

Yep well I was going on the failure bucket for that search and now am looking at the audiodg.exe and it is part of the Windows system so if you haven't already run these - I have not gone back through the thread yet

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

http://www.sevenforums.com/tutorials/433-disk-check.html< if necessary include the /f and /r in the command line as per Option2
Do those in safe mode

There are other things to look through though as for example what is in the pic for msinfo.

PS on searching it is something hooked up via USB but what??

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000021, the data following the pool block being freed is corrupt.  Typically this means the consumer (call stack ) has overrun the block.
Arg2: fffffa800e43b000, The pool pointer being freed.
Arg3: 0000000000001c10, The number of bytes allocated for the pool block.
Arg4: 0012001500121c25, The corrupted value found following the pool block.
Debugging Details:
------------------
Unknown module 'Unknown_Module_fffff880_06a04000' found on stack, using vad to reload module.
!vad_reload -1 0xfffff88006a04000
Unable to get LeftChild of nt!_MMVAD_SHORT at fffffa8012003010
BUGCHECK_STR:  0x19_21
POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c2100
GetUlongFromAddress: unable to read from fffff800030c21c0
 fffffa800e43b000 Nonpaged pool
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  [COLOR=red]audiodg.exe[/COLOR]
CURRENT_IRQL:  2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER:  from fffff80002fbb9c2 to fffff80002e858c0
STACK_TEXT:  
fffff880`0da5d588 fffff800`02fbb9c2 : 00000000`00000019 00000000`00000021 fffffa80`0e43b000 00000000`00001c10 : nt!KeBugCheckEx
fffff880`0da5d590 fffff880`06a24198 : 00000000`00000000 00000000`00000000 fffffa80`42434541 fffffa80`00000000 : nt!ExAllocatePoolWithTag+0x16fa
fffff880`0da5d640 00000000`00000000 : 00000000`00000000 fffffa80`42434541 fffffa80`00000000 fffff6fc`40032518 : Unknown_Module_fffff880_06a04000+0x20198
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
Unknown_Module_fffff880_06a04000+20198
fffff880`06a24198 ??              ???
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  Unknown_Module_fffff880_06a04000+20198
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Unknown_Module_fffff880_06a04000
IMAGE_NAME:  Unknown_Module_fffff880_06a04000
DEBUG_FLR_IMAGE_TIMESTAMP:  5252be31
FAILURE_BUCKET_ID:  [COLOR=red]X64_0x19_21_Unknown_Module_fffff880_06a04000+20198[/COLOR]
BUCKET_ID:  X64_0x19_21_Unknown_Module_fffff880_06a04000+20198
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x19_21_unknown_module_fffff880_06a04000+20198
FAILURE_ID_HASH:  {af464161-e09a-dda0-3dec-45d5ef50427d}
Followup: MachineOwner

 

[ICIT2LOL]

This did come up at length USB\VID_0000&PID_0000\5&CC7037B&0&8 - Microsoft Community

 

[MnemonicSyntax]

Alright, so an update.

I reformatted my computer. After getting back into Windows, the USB failure popped up. I unplugged everything except a mouse, restarted, still had the issue. Switched USB ports, still had the issue.

Fed up, I Google my motherboard (Asus Maximus Extreme VI) and the USB issue, and a few others had the same thing happen but it's not very widespread. Clearing the CMOS fixed their issue and so I thought I would try it.

It worked.

So I don't have the USB Unknown Device in Device Manager. My question is though, could that be related to my BSODs? Clearing the CMOS battery?

Thanks for your awesome help guys, this forum is nothing but class acts