Jump to content

BSOD

NewbixCube
By NewbixCube
in Troubleshooting
 Share
Posted

BSOD is the worse experience a computer could ever have. When you encounter this kind of problem you could either use system restore or scan for malware. 

Nope. Go hang out the Sysnative forums, OSR, or BleepingComputer. Then come back. There are far worse issues than BSODs. Statistically, most BSODs are due to driver errors or misbehaving applications/services.

 

Malware only makes up a small % of causes; usually since most malware makes it so that it either secretly hides on the system, or making windows unbootable completely.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5889050
Share on other sites
Link to post
Share on other sites
Posted
  • Author

@ionbasa

 

Looks like we're back to it. BSODs and now it's starting to just reboot. Sometimes it straight reboots and sometimes all the monitors go off and the computer is still running but it won't boot so I have to use power button.It seems like they progressively get worse. We fix it for a short time then they just start up again...

 

All the crashed occurred with the following programs open usually: Google Chrome (4-8 tabs), Spotify, Teamspeak, and Skype at the very least.

I crashed while using google chrome or as of lately just playing hearthstone. Most BSODs are different or repeats.

I've ran DDU in safe mode two days ago and have the latest nvidia drivers. The next thing I guess I should do is run memtest when I sleep tonight?

 

Memorydmp, Minidumps, Event Viewer, and Perfmon: https://mega.nz/#!BttiDYhL!0gJQQybPSpd7HUaihYUV3M0iZYo0L20BCNAqli7L4_c

 

WhoCrashed (9 Crashes in total since the 29th.)

On Fri 9/4/2015 6:26:57 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090415-10078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8018CABD0C7, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
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.



On Fri 9/4/2015 6:26:57 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8018CABD0C7, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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.



On Fri 9/4/2015 6:22:23 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090415-11234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x1A (0x61941, 0x5E1D49F0, 0xD, 0xFFFFD00024555B00)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 9/4/2015 2:29:10 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090415-15218-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x3C3D)
Bugcheck code: 0x10E (0x2E, 0xFFFFC00177E6C7E0, 0xFFFFC0018CFCBAD0, 0xFFFFD00143EB1730)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 9/2/2015 8:14:10 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090215-11843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x19 (0x3, 0xFFFFE00194C0D220, 0xFFFFE00194C0D220, 0x6C894CCE8B495F45)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 9/2/2015 4:01:52 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090215-12812-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF8002B8E2B18)
Bugcheck code: 0xD1 (0xFFFFE00286C42130, 0x2, 0x0, 0xFFFFF8002B8E2B18)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 9/1/2015 8:56:47 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090115-13546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DD00)
Bugcheck code: 0x50 (0xFFFFD00023F6F598, 0x2, 0xFFFFF801A7E845DF, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.



On Mon 8/31/2015 1:45:18 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\083115-14375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DD00)
Bugcheck code: 0x7F (0x8, 0xFFFFF801D903AE70, 0x0, 0xFFFFF801D742FA6C)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 8/29/2015 5:06:47 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082915-15656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DD00)
Bugcheck code: 0xA (0xFFFFFFFFC2B60F06, 0x2, 0x1, 0xFFFFF8002F1237E3)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5950353
Share on other sites
Link to post
Share on other sites
Posted

@ionbasa

 

Looks like we're back to it. BSODs and now it's starting to just reboot. Sometimes it straight reboots and sometimes all the monitors go off and the computer is still running but it won't boot so I have to use power button.It seems like they progressively get worse. We fix it for a short time then they just start up again...

 

All the crashed occurred with the following programs open usually: Google Chrome (4-8 tabs), Spotify, Teamspeak, and Skype at the very least.

I crashed while using google chrome or as of lately just playing hearthstone. Most BSODs are different or repeats.

I've ran DDU in safe mode two days ago and have the latest nvidia drivers. The next thing I guess I should do is run memtest when I sleep tonight?

 

Memorydmp, Minidumps, Event Viewer, and Perfmon: https://mega.nz/#!BttiDYhL!0gJQQybPSpd7HUaihYUV3M0iZYo0L20BCNAqli7L4_c

 

WhoCrashed (9 Crashes in total since the 29th.)

On Fri 9/4/2015 6:26:57 PM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\090415-10078-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8018CABD0C7, 0x0, 0xFFFFFFFFFFFFFFFF)

Error: KMODE_EXCEPTION_NOT_HANDLED

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 program generated an exception which the error handler did not catch.

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.

On Fri 9/4/2015 6:26:57 PM GMT your computer crashed

crash dump file: C:\WINDOWS\memory.dmp

This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8018CABD0C7, 0x0, 0xFFFFFFFFFFFFFFFF)

Error: KMODE_EXCEPTION_NOT_HANDLED

Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.

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.

On Fri 9/4/2015 6:22:23 PM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\090415-11234-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)

Bugcheck code: 0x1A (0x61941, 0x5E1D49F0, 0xD, 0xFFFFD00024555B00)

Error: MEMORY_MANAGEMENT

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 severe memory management error occurred.

This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Fri 9/4/2015 2:29:10 PM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\090415-15218-01.dmp

This was probably caused by the following module: watchdog.sys (watchdog+0x3C3D)

Bugcheck code: 0x10E (0x2E, 0xFFFFC00177E6C7E0, 0xFFFFC0018CFCBAD0, 0xFFFFD00143EB1730)

Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL

file path: C:\WINDOWS\system32\drivers\watchdog.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Watchdog Driver

Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Wed 9/2/2015 8:14:10 PM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\090215-11843-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)

Bugcheck code: 0x19 (0x3, 0xFFFFE00194C0D220, 0xFFFFE00194C0D220, 0x6C894CCE8B495F45)

Error: BAD_POOL_HEADER

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 pool header is corrupt.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 9/2/2015 4:01:52 PM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\090215-12812-01.dmp

This was probably caused by the following module: netio.sys (0xFFFFF8002B8E2B18)

Bugcheck code: 0xD1 (0xFFFFE00286C42130, 0x2, 0x0, 0xFFFFF8002B8E2B18)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

file path: C:\WINDOWS\system32\drivers\netio.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Network I/O Subsystem

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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Tue 9/1/2015 8:56:47 PM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\090115-13546-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14DD00)

Bugcheck code: 0x50 (0xFFFFD00023F6F598, 0x2, 0xFFFFF801A7E845DF, 0x0)

Error: PAGE_FAULT_IN_NONPAGED_AREA

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 invalid system memory has been referenced.

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.

On Mon 8/31/2015 1:45:18 PM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\083115-14375-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14DD00)

Bugcheck code: 0x7F (0x8, 0xFFFFF801D903AE70, 0x0, 0xFFFFF801D742FA6C)

Error: UNEXPECTED_KERNEL_MODE_TRAP

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 8/29/2015 5:06:47 PM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\082915-15656-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14DD00)

Bugcheck code: 0xA (0xFFFFFFFFC2B60F06, 0x2, 0x1, 0xFFFFF8002F1237E3)

Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

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.

I probably won't take a look at these today since it's actually my B-day today and i'll be out for the most part. But I'll post back as soon as possible. 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5952270
Share on other sites
Link to post
Share on other sites
Posted
  • Author

I probably won't take a look at these today since it's actually my B-day today and i'll be out for the most part. But I'll post back as soon as possible. 

 

No worries. I'd only expect a response if you're available to do so.

Happy birthday, hope you have a good one :)

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5955382
Share on other sites
Link to post
Share on other sites
Posted
  • Author

@ionbasa

 

Didn't get a bsod all day yesterday but I just got one now whilst playing hearthstone, starting a large download, and using google chrome/spotify.

Here's the info: https://mega.nz/#!41VQQYYL!KFBWVPcqURW-1yHtAoXaeTPczwEOapRL8CplsupylBo

 

WhoCrashed

On Sun 9/6/2015 6:00:53 PM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\090615-11718-01.dmp
This was probably caused by the following module: ndu.sys (Ndu+0x1D64)
Bugcheck code: 0xD1 (0x36, 0x2, 0x1, 0xFFFFF80147501D64)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ndu.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows Network Data Usage Monitoring Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

Also have another question. So every night I go to bed I put the computer in sleep but lately whenever I wake up and turn the computer on it posts but no fans turn on. So I hold down the power button turn it off, flip the psu off and on. Then hit power and it works just fine, loading in all the things I had open when I put it in sleep. I was thinking maybe it's since it's so cold lately? Not sure if it had a similarity to my issues.

 

EDIT: Right after submitting this I was downloading a game + ethernet drivers to update and watching a youtube video. BSOD right away. Seems ot be a similar one as I just had previously about drivers.

 

On Sun 9/6/2015 6:13:37 PM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\090615-11093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0xA (0xFFFFE001F5C9B970, 0x2, 0x1, 0xFFFFF802BF0ACE5F)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.

 

Is it possible that this is a hardware issue with my GPU? I know it's been said that it was software but we've done a lot.

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5966377
Share on other sites
Link to post
Share on other sites
Posted

@ionbasa

 

Didn't get a bsod all day yesterday but I just got one now whilst playing hearthstone, starting a large download, and using google chrome/spotify.

Here's the info: https://mega.nz/#!41VQQYYL!KFBWVPcqURW-1yHtAoXaeTPczwEOapRL8CplsupylBo

 

WhoCrashed

On Sun 9/6/2015 6:00:53 PM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\090615-11718-01.dmp

This was probably caused by the following module: ndu.sys (Ndu+0x1D64)

Bugcheck code: 0xD1 (0x36, 0x2, 0x1, 0xFFFFF80147501D64)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

file path: C:\WINDOWS\system32\drivers\ndu.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Windows Network Data Usage Monitoring Driver

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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

Also have another question. So every night I go to bed I put the computer in sleep but lately whenever I wake up and turn the computer on it posts but no fans turn on. So I hold down the power button turn it off, flip the psu off and on. Then hit power and it works just fine, loading in all the things I had open when I put it in sleep. I was thinking maybe it's since it's so cold lately? Not sure if it had a similarity to my issues.

 

EDIT: Right after submitting this I was downloading a game + ethernet drivers to update and watching a youtube video. BSOD right away. Seems ot be a similar one as I just had previously about drivers.

 

On Sun 9/6/2015 6:13:37 PM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\090615-11093-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)

Bugcheck code: 0xA (0xFFFFE001F5C9B970, 0x2, 0x1, 0xFFFFF802BF0ACE5F)

Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

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.

 

Is it possible that this is a hardware issue with my GPU? I know it's been said that it was software but we've done a lot.

It might be a power issue, or a BIOS issue. Have you tried updating to the latest BIOS for your motherboard? Occasionally things like sleep states don't quite work correctly on older BIOSes. 

 

I'm downloading the dump files now and will take a look.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5967590
Share on other sites
Link to post
Share on other sites
Posted (edited)
  • Author

It might be a power issue, or a BIOS issue. Have you tried updating to the latest BIOS for your motherboard? Occasionally things like sleep states don't quite work correctly on older BIOSes. 

 

I'm downloading the dump files now and will take a look.

 

I have the latest update for my bios. I could try flashing my bios? I don't know if that does anything also here's another post not sure if it could be related to BSODs or not but you've mentioned it before.

 

http://linustechtips.com/main/topic/445253-nettcp-listener-adapter-stopped/

 

Edit: I plan to run memtest when I leave to go out today.

Edited by NewbixCube
Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5967685
Share on other sites
Link to post
Share on other sites
Posted

I have the latest update for my bios. I could try flashing my bios? I don't know if that does anything also here's another post not sure if it could be related to BSODs or not but you've mentioned it before.

 

http://linustechtips.com/main/topic/445253-nettcp-listener-adapter-stopped/

 

 

Okay, ran the dump files through WinDBG:

 

Okay. Do you have BlueStacks installed? One of the faulting processes was "hd-network" which belongs to Bluestacks (the android app emulator).

I'm also seeing "NDU.sys" crashed a few times.

 

Did you by chance have any memory leaks and followed instructions to change anything in the registry? I also saw the post about the net.tcp issue, which actually showed up in a few BSODs as well.

 

You're best bet would be to:

Uninstall Bluestacks.

Repair install Windows after uninstalling Bluestacks: http://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html

 

As for your power issues, did this happen recently, or is it something new? Did you install Windows in UEFI mode or legacy mode?

Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16463.amd64fre.th1.150819-1946Machine Name:Kernel base = 0xfffff803`be480000 PsLoadedModuleList = 0xfffff803`be7a5030Debug session time: Sun Sep  6 14:00:53.521 2015 (UTC - 4:00)System Uptime: 1 days 22:09:41.170********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high.  This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: 0000000000000036, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000001, value 0 = read operation, 1 = write operationArg4: fffff80147501d64, address which referenced memoryDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2WRITE_ADDRESS: unable to get nt!MmSpecialPoolStartunable to get nt!MmSpecialPoolEndunable to get nt!MmPagedPoolEndunable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes 0000000000000036 CURRENT_IRQL:  2FAULTING_IP: Ndu!NduOutboundMacClassifyProcessSingleNbl+d4fffff801`47501d64 4c8933          mov     qword ptr [rbx],r14CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  AVPROCESS_NAME:  SystemTRAP_FRAME:  ffffd001cafa8030 -- (.trap 0xffffd001cafa8030)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=ffffd001cafa8250rdx=ffffe000c041d710 rsi=0000000000000000 rdi=0000000000000000rip=fffff80147501d64 rsp=ffffd001cafa81c0 rbp=ffffd001cafa8240 r8=0000000000000000  r9=0000000000000000 r10=0000000000000051r11=0000000000000002 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei pl nz na po ncNdu!NduOutboundMacClassifyProcessSingleNbl+0xd4:fffff801`47501d64 4c8933          mov     qword ptr [rbx],r14 ds:00000000`00000000=0000000000000000Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff803be5d8ba9 to fffff803be5ce240STACK_TEXT:  ffffd001`cafa7ee8 fffff803`be5d8ba9 : 00000000`0000000a 00000000`00000036 00000000`00000002 00000000`00000001 : nt!KeBugCheckExffffd001`cafa7ef0 fffff803`be5d73c8 : 00000000`00000206 fffff803`be4c8639 ffffe000`c4127a40 ffffe000`c0595840 : nt!KiBugCheckDispatch+0x69ffffd001`cafa8030 fffff801`47501d64 : ffffe000`c54478e0 ffffd001`cafa8240 00000000`00000000 ffffe000`c41277c0 : nt!KiPageFault+0x248ffffd001`cafa81c0 fffff801`47501c62 : ffffe000`c41277c0 00060000`06000000 00000000`00000000 ffffe000`c41277c0 : Ndu!NduOutboundMacClassifyProcessSingleNbl+0xd4ffffd001`cafa8290 fffff801`44c3203d : ffffe000`b9540990 ffffd001`cafa8359 ffffe000`00000000 ffffe000`c41277c0 : Ndu!NduOutboundMacClassify+0x102ffffd001`cafa82f0 fffff801`44f3155b : ffffe000`b6d229a0 ffffd001`cafa8708 ffffe000`c41277c0 ffffe000`b82aa010 : NETIO!KfdClassify2+0x17dffffd001`cafa83c0 fffff801`44afc5fb : ffff50cd`ffbc1880 00000000`00000000 ffffe000`bca51010 00000000`000005ac : wfplwfs!LwfLowerSendNetBufferLists+0xdbffffd001`cafa8500 fffff801`44af191c : ffffd001`cafa85a0 ffffd001`00000000 00000004`00000008 ffffe000`bd985210 : ndis!ndisCallSendHandler+0x3bffffd001`cafa8550 fffff801`44d35cb8 : ffffe000`b82a6860 ffffe000`c41277c0 ffffe000`00000000 00000000`00000000 : ndis!NdisSendNetBufferLists+0x23cffffd001`cafa86d0 fffff801`44d30e45 : 00000000`0000003c ffffe000`ba941f00 ffffd001`cafa87c1 ffffe000`b82a6360 : tcpip!FlFastSendPackets+0xf8ffffd001`cafa8720 fffff801`44cdcbfe : 00000000`00000001 00000000`00000014 ffffe000`b82a9010 00000000`00000000 : tcpip!IpNlpFastContinueSendDatagram+0x335ffffd001`cafa8810 fffff801`44d309b3 : ffffd001`cafa8cf0 000005ac`00003e07 fffff801`44e89310 ffffe000`c877e360 : tcpip!IppSendDatagramsCommon+0x77effffd001`cafa8a80 fffff801`44d272a4 : 00000000`00000002 00000000`00000000 ffffe000`b9f9aa40 fffff801`44cf9c15 : tcpip!IpNlpFastSendDatagram+0x313ffffd001`cafa8b60 fffff801`44d266d1 : 00000000`00000002 00000000`00000000 ffffe000`b829f3b0 ffffe000`c3193350 : tcpip!TcpTcbHeaderSend+0x784ffffd001`cafa8e30 fffff801`44ce2bad : ffffe000`b7afd380 00000000`09e7ce97 ffffd001`cb719a22 00000182`ebb24473 : tcpip!TcpFlushDelay+0x131ffffd001`cafa8ec0 fffff801`44ce1b99 : ffffe000`b7af73c0 ffffd001`cafa9169 ffffd001`cafa9130 fffff801`00000000 : tcpip!TcpPreValidatedReceive+0x3adffffd001`cafa8fb0 fffff801`44ce1792 : 00000000`00000000 00001f80`0041026b 00000000`00000000 00000000`00000006 : tcpip!IppDeliverListToProtocol+0x59ffffd001`cafa9060 fffff801`44ce0be4 : 00000000`00000006 00000000`00000000 ffffd001`cafa9169 00000000`00000000 : tcpip!IppProcessDeliverList+0x62ffffd001`cafa90d0 fffff801`44ce1f28 : fffff801`44e89310 ffffe000`b7b13330 00000000`00000001 00000000`00000001 : tcpip!IppReceiveHeaderBatch+0x214ffffd001`cafa91d0 fffff801`44d4342f : ffffe000`b82a6360 ffffe000`b82a33b0 ffffd001`cafa9301 00000000`00000000 : tcpip!IppFlcReceivePacketsCore+0x338ffffd001`cafa92f0 fffff801`44d42a90 : 00000000`00000002 ffffd001`00000001 fffff801`44d338a0 00060000`00000001 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x25fffffd001`cafa93d0 fffff803`be4fc1f5 : 00000000`00000002 00000000`00000000 ffffe000`b79fb840 fffff801`44d429d0 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xc0ffffd001`cafa9500 fffff801`44d33cf6 : ffffe000`b7b10230 00000000`00000000 ffffe000`b7b101d0 ffffe000`b82a3300 : nt!KeExpandKernelStackAndCalloutInternal+0x85ffffd001`cafa9550 fffff801`44af95d3 : 00000000`00000000 ffffd001`cafa9650 ffffe000`00000001 fffff801`44afcf67 : tcpip!FlReceiveNetBufferListChain+0xb6ffffd001`cafa95d0 fffff801`44af930d : 00000000`00000001 ffffe000`b82a0000 00000000`00000000 fffff801`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0x133ffffd001`cafa9690 fffff801`44afcc33 : ffffe000`b812b1a0 00000000`00000000 fffff801`44af90e0 00000000`00000000 : ndis!ndisMTopReceiveNetBufferLists+0x22dffffd001`cafa9790 fffff801`44af2929 : ffffe000`b81f0402 ffffd001`cafa98e0 ffffd001`cafa9a78 fffff803`be5d2c76 : ndis!ndisCallReceiveHandler+0x43ffffd001`cafa97e0 fffff801`46a08ada : 00000000`00000000 ffffe000`b81ee000 ffffe000`b81eea30 ffffd001`cafa9a78 : ndis!NdisMIndicateReceiveNetBufferLists+0x479ffffd001`cafa9950 00000000`00000000 : ffffe000`b81ee000 ffffe000`b81eea30 ffffd001`cafa9a78 ffffe000`00000001 : e22w7x64+0x8adaSTACK_COMMAND:  kbFOLLOWUP_IP: Ndu!NduOutboundMacClassifyProcessSingleNbl+d4fffff801`47501d64 4c8933          mov     qword ptr [rbx],r14SYMBOL_STACK_INDEX:  3SYMBOL_NAME:  Ndu!NduOutboundMacClassifyProcessSingleNbl+d4FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: NduIMAGE_NAME:  Ndu.sysDEBUG_FLR_IMAGE_TIMESTAMP:  559f3a77FAILURE_BUCKET_ID:  X64_AV_Ndu!NduOutboundMacClassifyProcessSingleNbl+d4BUCKET_ID:  X64_AV_Ndu!NduOutboundMacClassifyProcessSingleNbl+d4Followup: MachineOwner 
Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16431.amd64fre.th1.150810-2333Machine Name:Kernel base = 0xfffff800`2f07f000 PsLoadedModuleList = 0xfffff800`2f3a4030Debug session time: Sat Aug 29 13:06:47.827 2015 (UTC - 4:00)System Uptime: 1 days 5:30:20.476********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************IRQL_NOT_LESS_OR_EQUAL (a)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high.  This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: ffffffffc2b60f06, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000001, bitfield :	bit 0 : value 0 = read operation, 1 = write operation	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)Arg4: fffff8002f1237e3, address which referenced memoryDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2WRITE_ADDRESS: unable to get nt!MmSpecialPoolStartunable to get nt!MmSpecialPoolEndunable to get nt!MmPagedPoolEndunable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes ffffffffc2b60f06 CURRENT_IRQL:  2FAULTING_IP: nt!KiIntSteerCalculateDistribution+93fffff800`2f1237e3 c1e106          shl     ecx,6CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  AVPROCESS_NAME:  SystemTRAP_FRAME:  fffff80030c36140 -- (.trap 0xfffff80030c36140)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000rip=fffff8002f1237e3 rsp=fffff80030c362d0 rbp=fffff80030c36300 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000r11=fffff80030c362f0 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei pl nz na po cynt!KiIntSteerCalculateDistribution+0x93:fffff800`2f1237e3 c1e106          shl     ecx,6Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff8002f1d76a9 to fffff8002f1ccd00STACK_TEXT:  fffff800`30c35ff8 fffff800`2f1d76a9 : 00000000`0000000a ffffffff`c2b60f06 00000000`00000002 00000000`00000001 : nt!KeBugCheckExfffff800`30c36000 fffff800`2f1d5ec8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69fffff800`30c36140 fffff800`2f1237e3 : ffffe001`ea403530 fffff800`2f1237ab ffffe001`e91d0ae0 00000000`00000000 : nt!KiPageFault+0x248fffff800`30c362d0 fffff800`2f123345 : fffff800`30c36460 fffff800`2f123cb8 00000000`00000001 00000000`00000000 : nt!KiIntSteerCalculateDistribution+0x93fffff800`30c36340 fffff800`2f122145 : 00000000`00000014 fffff800`30c36500 00000000`0cb08c62 fffff800`30c36500 : nt!KeIntSteerPeriodic+0x65fffff800`30c36400 fffff800`2f088308 : 00000000`0cb08c62 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PpmParkSteerInterrupts+0x575fffff800`30c36810 fffff800`2f0ce735 : ffffe001`ed0fe080 fffff800`2f3e4f00 fffff800`30c369c0 fffff800`30c36b30 : nt!PpmCheckStart+0x178fffff800`30c368c0 fffff800`2f0cde10 : ffffe001`fb44ca20 fffff800`30c36b20 fffff800`30c36b10 00000000`00000001 : nt!KiExecuteAllDpcs+0x275fffff800`30c36a10 fffff800`2f1cfa5a : fffff800`2f3e2180 fffff800`2f3e2180 fffff800`2f458740 ffffe001`eb7b7080 : nt!KiRetireDpcList+0xe0fffff800`30c36c60 00000000`00000000 : fffff800`30c37000 fffff800`30c31000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5aSTACK_COMMAND:  kbFOLLOWUP_IP: nt!KiIntSteerCalculateDistribution+93fffff800`2f1237e3 c1e106          shl     ecx,6SYMBOL_STACK_INDEX:  3SYMBOL_NAME:  nt!KiIntSteerCalculateDistribution+93FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP:  55c9bcb6FAILURE_BUCKET_ID:  X64_AV_nt!KiIntSteerCalculateDistribution+93BUCKET_ID:  X64_AV_nt!KiIntSteerCalculateDistribution+93Followup: MachineOwner 
Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16431.amd64fre.th1.150810-2333Machine Name:Kernel base = 0xfffff801`d7409000 PsLoadedModuleList = 0xfffff801`d772e030Debug session time: Mon Aug 31 09:45:18.336 2015 (UTC - 4:00)System Uptime: 1 days 20:37:51.984********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************UNEXPECTED_KERNEL_MODE_TRAP (7f)This means a trap occurred in kernel mode, and it's a trap of a kindthat the kernel isn't allowed to have/catch (bound trap) or thatis always instant death (double fault).  The first number in thebugcheck params is the number of the trap (8 = double fault, etc)Consult an Intel x86 family manual to learn more about what thesetraps are. Here is a *portion* of those codes:If kv shows a taskGate        use .tss on the part before the colon, then kv.Else if kv shows a trapframe        use .trap on that valueElse        .trap on the appropriate frame will show where the trap was taken        (on x86, this will be the ebp that goes with the procedure KiTrap)Endifkb will then show the corrected stack.Arguments:Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULTArg2: fffff801d903ae70Arg3: 0000000000000000Arg4: fffff801d742fa6cDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x7f_8CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  Origin.exeCURRENT_IRQL:  2LAST_CONTROL_TRANSFER:  from fffff801d75616a9 to fffff801d7556d00STACK_TEXT:  fffff801`d903ad28 fffff801`d75616a9 : 00000000`0000007f 00000000`00000008 fffff801`d903ae70 00000000`00000000 : nt!KeBugCheckExfffff801`d903ad30 fffff801`d755f774 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69fffff801`d903ae70 fffff801`d742fa6c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb400000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFlushTbList+0x2ccSTACK_COMMAND:  kbFOLLOWUP_IP: nt!KiDoubleFaultAbort+b4fffff801`d755f774 90              nopSYMBOL_STACK_INDEX:  2SYMBOL_NAME:  nt!KiDoubleFaultAbort+b4FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP:  55c9bcb6FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b4BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b4Followup: MachineOwner 
Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16431.amd64fre.th1.150810-2333Machine Name:Kernel base = 0xfffff801`a7a7a000 PsLoadedModuleList = 0xfffff801`a7d9f030Debug session time: Tue Sep  1 16:56:47.829 2015 (UTC - 4:00)System Uptime: 1 days 7:10:48.479********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************PAGE_FAULT_IN_NONPAGED_AREA (50)Invalid system memory was referenced.  This cannot be protected by try-except,it must be protected by a Probe.  Typically the address is just plain bad or itis pointing at freed memory.Arguments:Arg1: ffffd00023f6f598, memory referenced.Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.Arg3: fffff801a7e845df, If non-zero, the instruction address which referenced the bad memory	address.Arg4: 0000000000000000, (reserved)Debugging Details:------------------Could not read faulting driver nameTRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2WRITE_ADDRESS: unable to get nt!MmSpecialPoolStartunable to get nt!MmSpecialPoolEndunable to get nt!MmPagedPoolEndunable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes ffffd00023f6f598 FAULTING_IP: nt!MiInsertSharedCommitNode+37ffffff801`a7e845df c68424d800000000 mov     byte ptr [rsp+0D8h],0MM_INTERNAL_CODE:  0CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  AVPROCESS_NAME:  ts3client_win6CURRENT_IRQL:  2TRAP_FRAME:  ffffd00023f6d330 -- (.trap 0xffffd00023f6d330)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=ffffe000a6beb840rdx=ffffc00173f61840 rsi=0000000000000000 rdi=0000000000000000rip=fffff801a7e845df rsp=ffffd00023f6d4c0 rbp=0000000000000003 r8=ffffe000a6487ad0  r9=0000000000000001 r10=ffffc00165c70598r11=0000000000000000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei pl zr na po ncnt!MiInsertSharedCommitNode+0x37f:fffff801`a7e845df c68424d800000000 mov     byte ptr [rsp+0D8h],0 ss:0018:ffffd000`23f6d598=00Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff801a7c1804a to fffff801a7bc7d00STACK_TEXT:  ffffd000`23f6d0e8 fffff801`a7c1804a : 00000000`00000050 ffffd000`23f6f598 00000000`00000002 ffffd000`23f6d330 : nt!KeBugCheckExffffd000`23f6d0f0 fffff801`a7a99536 : 00000000`00000002 00000000`00000000 ffffd000`23f6d330 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4174affffd000`23f6d1e0 fffff801`a7bd0dbd : 00000002`0000000c 00000000`00000000 ffffc001`6a06fe20 ffffe000`a6aed290 : nt!MmAccessFault+0x696ffffd000`23f6d330 fffff801`a7e845df : 00000000`00000000 00000000`00000000 00000000`000007ff ffffd001`5608f000 : nt!KiPageFault+0x13dffffd000`23f6d4c0 fffff801`a7e845a3 : ffffc001`65310f00 ffffe000`a6beb840 00000000`00000000 00000000`00000000 : nt!MiInsertSharedCommitNode+0x37fffffd000`23f6d580 fffff801`a7e9d52c : ffffc001`6547add0 00000000`00000000 00000000`00000001 ffffe000`a6bebf01 : nt!MiInsertSharedCommitNode+0x343ffffd000`23f6d640 fffff801`a7e9b493 : ffffe000`a1d09f30 00000000`00000000 00000000`00000002 ffffc001`654177f0 : nt!ObpIncrementHandleCountEx+0x3acffffd000`23f6d730 fffff801`a7f004d7 : ffffe000`ad270010 00000000`00000000 ffffc001`64e6d1a8 ffffe000`a1d09f20 : nt!ObpCreateHandle+0x373ffffd000`23f6d970 fffff801`a7f8c0e7 : ffffe000`00000001 000000aa`7610f7a8 00007ff8`26302058 00000000`00000020 : nt!ObOpenObjectByName+0x337ffffd000`23f6daa0 fffff801`a7bd2363 : ffffe000`a6a2a080 00000000`ffffffff 00000000`00000000 ffffe000`a686bf00 : nt!NtOpenSection+0x67ffffd000`23f6db00 00007ff8`48ec386a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13000000aa`7610f6f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff8`48ec386aSTACK_COMMAND:  kbFOLLOWUP_IP: nt!MiInsertSharedCommitNode+37ffffff801`a7e845df c68424d800000000 mov     byte ptr [rsp+0D8h],0SYMBOL_STACK_INDEX:  4SYMBOL_NAME:  nt!MiInsertSharedCommitNode+37fFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP:  55c9bcb6IMAGE_NAME:  memory_corruptionFAILURE_BUCKET_ID:  X64_AV_nt!MiInsertSharedCommitNode+37fBUCKET_ID:  X64_AV_nt!MiInsertSharedCommitNode+37fFollowup: MachineOwner 
Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16463.amd64fre.th1.150819-1946Machine Name:Kernel base = 0xfffff800`c7816000 PsLoadedModuleList = 0xfffff800`c7b3b030Debug session time: Wed Sep  2 16:14:10.907 2015 (UTC - 4:00)System Uptime: 0 days 4:11:41.555********************************************************************************                                                                             **                        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 ofthe problem, and then special pool applied to the suspect tags or the driververifier to a suspect driver.Arguments:Arg1: 0000000000000003, the pool freelist is corrupt.Arg2: ffffe00194c0d220, the pool entry being checked.Arg3: ffffe00194c0d220, the read back flink freelist value (should be the same as 2).Arg4: 6c894cce8b495f45, the read back blink freelist value (should be the same as 2).Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x19_3CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  HD-Network.exeCURRENT_IRQL:  2LAST_CONTROL_TRANSFER:  from fffff800c7a8a97e to fffff800c7964240STACK_TEXT:  ffffd000`225214f8 fffff800`c7a8a97e : 00000000`00000019 00000000`00000003 ffffe001`94c0d220 ffffe001`94c0d220 : nt!KeBugCheckExffffd000`22521500 fffff800`c7862051 : ffffe001`00000200 00000000`00001000 00000000`00000001 00000000`00000000 : nt!ExFreePool+0xcb6ffffd000`225215e0 fffff800`47701a51 : fffff800`c7b70d00 ffffe001`917c6f70 ffffd001`50646641 fffff800`00000001 : nt!ExAllocatePoolWithQuotaTag+0x61ffffd000`22521670 fffff800`477189ae : ffffe001`92c50100 ffffd000`225216e0 00000000`000007ff ffffd001`28292000 : afd!AfdPollGetInfo+0x21ffffd000`225216b0 fffff800`47700d15 : 00000000`00012000 ffffe001`917c6f20 ffffe001`c000000d ffffd000`22521b80 : afd!AfdPoll32+0xf6ffffd000`225217d0 fffff800`c7c4417d : 00000000`00000000 ffffd000`22521b80 ffffe001`94c51e10 fffff800`00000001 : afd!AfdPoll+0x35ffffd000`22521800 fffff800`c7c43a56 : e00190a3`49406ce9 00000000`001f0003 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x71dffffd000`22521a20 fffff800`c796e863 : 00000000`00000000 00000000`00000001 00000000`00000001 00000000`67c7bb01 : nt!NtDeviceIoControlFile+0x56ffffd000`22521a90 00000000`67be1e52 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`0009efd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x67be1e52STACK_COMMAND:  kbFOLLOWUP_IP: nt!ExFreePool+cb6fffff800`c7a8a97e cc              int     3SYMBOL_STACK_INDEX:  1SYMBOL_NAME:  nt!ExFreePool+cb6FOLLOWUP_NAME:  Pool_corruptionIMAGE_NAME:  Pool_CorruptionDEBUG_FLR_IMAGE_TIMESTAMP:  0MODULE_NAME: Pool_CorruptionFAILURE_BUCKET_ID:  X64_0x19_3_nt!ExFreePool+cb6BUCKET_ID:  X64_0x19_3_nt!ExFreePool+cb6Followup: Pool_corruption 
Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16463.amd64fre.th1.150819-1946Machine Name:Kernel base = 0xfffff801`ce081000 PsLoadedModuleList = 0xfffff801`ce3a6030Debug session time: Wed Sep  2 12:01:52.058 2015 (UTC - 4:00)System Uptime: 0 days 5:26:26.707********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high.  This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: ffffe00286c42130, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000000, value 0 = read operation, 1 = write operationArg4: fffff8002b8e2b18, address which referenced memoryDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2READ_ADDRESS: unable to get nt!MmSpecialPoolStartunable to get nt!MmSpecialPoolEndunable to get nt!MmPagedPoolEndunable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes ffffe00286c42130 CURRENT_IRQL:  2FAULTING_IP: NETIO!RtlGetNextExpiredTimerWheelEntry+e8fffff800`2b8e2b18 418b4010        mov     eax,dword ptr [r8+10h]CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  AVPROCESS_NAME:  SystemTRAP_FRAME:  fffff801cfc38530 -- (.trap 0xfffff801cfc38530)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffffe00086c42120 rbx=0000000000000000 rcx=ffffe00086c41638rdx=ffffe00086c42120 rsi=0000000000000000 rdi=0000000000000000rip=fffff8002b8e2b18 rsp=fffff801cfc386c8 rbp=fffff801cfc387d0 r8=ffffe00286c42120  r9=00000000012adef2 r10=000000000000001dr11=00000000012c5e88 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei pl nz na pe ncNETIO!RtlGetNextExpiredTimerWheelEntry+0xe8:fffff800`2b8e2b18 418b4010        mov     eax,dword ptr [r8+10h] ds:ffffe002`86c42130=????????Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff801ce1d9ba9 to fffff801ce1cf240STACK_TEXT:  fffff801`cfc383e8 fffff801`ce1d9ba9 : 00000000`0000000a ffffe002`86c42130 00000000`00000002 00000000`00000000 : nt!KeBugCheckExfffff801`cfc383f0 fffff801`ce1d83c8 : 00000000`00000000 ffffe000`897c5000 ffffe000`897c3000 00000000`ffffffff : nt!KiBugCheckDispatch+0x69fffff801`cfc38530 fffff800`2b8e2b18 : fffff800`2b9d5767 00000000`012adf2e ffffe000`884fe010 00000000`0000001c : nt!KiPageFault+0x248fffff801`cfc386c8 fffff800`2b9d5767 : 00000000`012adf2e ffffe000`884fe010 00000000`0000001c ffffe000`884fe010 : NETIO!RtlGetNextExpiredTimerWheelEntry+0xe8fffff801`cfc386d0 fffff801`ce0d0735 : fffff801`ce3e6f00 ffffd000`ca1465b0 fffff801`cfc38b20 ffffe000`884fe0b0 : tcpip!TcpPeriodicTimeoutHandler+0xe67fffff801`cfc388c0 fffff801`ce0cfe10 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x275fffff801`cfc38a10 fffff801`ce1d1f9a : fffff801`ce3e4180 fffff801`ce3e4180 fffff801`ce45a740 ffffe000`8d49a080 : nt!KiRetireDpcList+0xe0fffff801`cfc38c60 00000000`00000000 : fffff801`cfc39000 fffff801`cfc33000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5aSTACK_COMMAND:  kbFOLLOWUP_IP: NETIO!RtlGetNextExpiredTimerWheelEntry+e8fffff800`2b8e2b18 418b4010        mov     eax,dword ptr [r8+10h]SYMBOL_STACK_INDEX:  3SYMBOL_NAME:  NETIO!RtlGetNextExpiredTimerWheelEntry+e8FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: NETIOIMAGE_NAME:  NETIO.SYSDEBUG_FLR_IMAGE_TIMESTAMP:  559f3890FAILURE_BUCKET_ID:  X64_AV_NETIO!RtlGetNextExpiredTimerWheelEntry+e8BUCKET_ID:  X64_AV_NETIO!RtlGetNextExpiredTimerWheelEntry+e8Followup: MachineOwner 
Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16463.amd64fre.th1.150819-1946Machine Name:Kernel base = 0xfffff801`8ca18000 PsLoadedModuleList = 0xfffff801`8cd3d030Debug session time: Fri Sep  4 14:26:57.426 2015 (UTC - 4:00)System Uptime: 0 days 0:03:59.075********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************KMODE_EXCEPTION_NOT_HANDLED (1e)This is a very common bugcheck.  Usually the exception address pinpointsthe driver/function that caused the problem.  Always note this addressas well as the link date of the driver/image that contains this address.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff8018cabd0c7, The address that the exception occurred atArg3: 0000000000000000, Parameter 0 of the exceptionArg4: ffffffffffffffff, Parameter 1 of the exceptionDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".FAULTING_IP: nt!KeIntSteerSnapPerf+e7fffff801`8cabd0c7 480391b0000000  add     rdx,qword ptr [rcx+0B0h]EXCEPTION_PARAMETER1:  0000000000000000EXCEPTION_PARAMETER2:  ffffffffffffffffREAD_ADDRESS: unable to get nt!MmSpecialPoolStartunable to get nt!MmSpecialPoolEndunable to get nt!MmPagedPoolEndunable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes ffffffffffffffff ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".BUGCHECK_STR:  0x1e_c0000005CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  2EXCEPTION_RECORD:  ffffe000ea8264d8 -- (.exr 0xffffe000ea8264d8)Cannot read Exception record @ ffffe000ea8264d8TRAP_FRAME:  ffffd00091a09198 -- (.trap 0xffffd00091a09198)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffffe000ea907600 rbx=0000000000000000 rcx=0000000000000000rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000rip=ffffd00091a092f0 rsp=fffff8018d26b372 rbp=ffffe00000000000 r8=ffffd00022ff3400  r9=ffffe000ea907600 r10=0000000000000000r11=ffffe000edeff010 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up di pl nz na pe ncaf99:ffffd000`91a092f0 0000            add     byte ptr [rax],al ds:ffffe000`ea907600=??Resetting default scopeUNALIGNED_STACK_POINTER:  fffff8018d26b372LAST_CONTROL_TRANSFER:  from fffff8018cc099d6 to fffff8018cb66240CONTEXT:  8349000000c88103 -- (.cxr 0x8349000000c88103)Unable to read context, Win32 error 0n30STACK_TEXT:  ffffd000`91a081c8 fffff801`8cc099d6 : 00000000`0000001e ffffffff`c0000005 fffff801`8cabd0c7 00000000`00000000 : nt!KeBugCheckExffffd000`91a081d0 fffff801`8cb6c27d : fffff801`8cd8f000 fffff801`8ca18000 0004c41c`00852000 ffffd000`91a08202 : nt!KiFatalExceptionHandler+0x22ffffd000`91a08210 fffff801`8ca8c050 : 00000000`00000000 fffff801`8cd92a00 ffffd000`91a09168 fffff800`4b173519 : nt!RtlpExecuteHandlerForException+0xdffffd000`91a08240 fffff801`8ca88c78 : ffffd000`91a09168 ffffd000`91a08e80 ffffd000`91a09168 00000000`00000001 : nt!RtlDispatchException+0x4e8ffffd000`91a08950 fffff801`8cb70c82 : ffffe000`ea8264d8 00000000`00000000 ffffd000`91a09198 ffffe000`ea8a9100 : nt!KiDispatchException+0x144ffffd000`91a09030 fffff801`8cb6f17e : 00000000`00000001 ffffe000`ec534040 ffff174a`87a4b289 00000000`00000000 : nt!KiExceptionDispatch+0xc2ffffd000`91a09210 fffff801`8cabd0c7 : 00000000`00075bd0 ffffd000`91a09500 00000000`00000000 fffff801`8d26b854 : nt!KiGeneralProtectionFault+0xfeffffd000`91a093a0 fffff801`8cabb1a2 : 00000000`00000002 00000000`2f58674d 00000000`00075bd0 ffffd000`91a09500 : nt!KeIntSteerSnapPerf+0xe7ffffd000`91a09400 fffff801`8ca21308 : 00000000`00075bd0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PpmParkSteerInterrupts+0x92ffffd000`91a09810 fffff801`8ca67735 : ffffd000`96647180 ffffd000`96649f00 ffffd000`91a099c0 ffffd000`91a09b20 : nt!PpmCheckStart+0x178ffffd000`91a098c0 fffff801`8ca66e10 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x275ffffd000`91a09a10 fffff801`8cb68f9a : ffffd000`96647180 ffffd000`96647180 ffffd000`96653bc0 ffffe000`ea6c7080 : nt!KiRetireDpcList+0xe0ffffd000`91a09c60 00000000`00000000 : ffffd000`91a0a000 ffffd000`91a04000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5aFOLLOWUP_IP: nt!KeIntSteerSnapPerf+e7fffff801`8cabd0c7 480391b0000000  add     rdx,qword ptr [rcx+0B0h]SYMBOL_STACK_INDEX:  7SYMBOL_NAME:  nt!KeIntSteerSnapPerf+e7FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP:  55d5626bSTACK_COMMAND:  .cxr 0x8349000000c88103 ; kbFAILURE_BUCKET_ID:  X64_0x1e_c0000005_nt!KeIntSteerSnapPerf+e7BUCKET_ID:  X64_0x1e_c0000005_nt!KeIntSteerSnapPerf+e7Followup: MachineOwner 
Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16463.amd64fre.th1.150819-1946Machine Name:Kernel base = 0xfffff800`35c1d000 PsLoadedModuleList = 0xfffff800`35f42030Debug session time: Fri Sep  4 14:22:23.259 2015 (UTC - 4:00)System Uptime: 0 days 3:52:26.907********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************MEMORY_MANAGEMENT (1a)    # Any other values for parameter 1 must be individually examined.Arguments:Arg1: 0000000000061941, The subtype of the bugcheck.Arg2: 000000005e1d49f0Arg3: 000000000000000dArg4: ffffd00024555b00Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x1a_61941CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  Battle.net.exeCURRENT_IRQL:  0LAST_CONTROL_TRANSFER:  from fffff80035d89888 to fffff80035d6b240STACK_TEXT:  ffffd000`245559a8 fffff800`35d89888 : 00000000`0000001a 00000000`00061941 00000000`5e1d49f0 00000000`0000000d : nt!KeBugCheckExffffd000`245559b0 fffff800`35d742bd : ffffe000`91bf2840 00000000`00000dd1 ffffd000`00000000 ffffe000`91412c10 : nt! ?? ::FNODOBFM::`string'+0xfa88ffffd000`24555b00 00000000`5e11b339 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13d00000000`00c7f794 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5e11b339STACK_COMMAND:  kbFOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+fa88fffff800`35d89888 cc              int     3SYMBOL_STACK_INDEX:  1SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+fa88FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP:  55d5626bFAILURE_BUCKET_ID:  X64_0x1a_61941_nt!_??_::FNODOBFM::_string_+fa88BUCKET_ID:  X64_0x1a_61941_nt!_??_::FNODOBFM::_string_+fa88Followup: MachineOwner 
Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16463.amd64fre.th1.150819-1946Machine Name:Kernel base = 0xfffff802`15672000 PsLoadedModuleList = 0xfffff802`15997030Debug session time: Fri Sep  4 10:29:10.563 2015 (UTC - 4:00)System Uptime: 1 days 11:41:13.212********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)The video memory manager encountered a condition that it can't recover from. By crashing,the video memory manager is attempting to get enough information into the minidump such thatsomebody can pinpoint what lead to this condition.Arguments:Arg1: 000000000000002e, The subtype of the bugcheck:Arg2: ffffc00177e6c7e0Arg3: ffffc0018cfcbad0Arg4: ffffd00143eb1730Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x10e_2eCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  0LAST_CONTROL_TRANSFER:  from fffff800472c3c3d to fffff802157c0240STACK_TEXT:  ffffd001`43eb16c8 fffff800`472c3c3d : 00000000`0000010e 00000000`0000002e ffffc001`77e6c7e0 ffffc001`8cfcbad0 : nt!KeBugCheckExffffd001`43eb16d0 fffff800`47181e81 : ffffc001`7a354420 ffffc001`77e6c7e0 ffffc001`77e6c7e0 ffffe001`00000003 : watchdog!WdLogEvent5_WdCriticalError+0xcdffffd001`43eb1710 fffff800`471e0167 : ffffc001`77e6c7e0 ffffe001`afce8e40 ffffc001`7b9dcea0 ffffc001`8cfcbad0 : dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+0x121ffffd001`43eb1760 fffff800`471be885 : 00000000`00000000 00000000`00000001 ffffd001`43eb1959 00000000`000000a3 : dxgmms2!VIDMM_SEGMENT::InvalidateAllVirtualAddress+0x19bffffd001`43eb1840 fffff800`4740c486 : ffffe001`afc413b0 00000000`00000000 ffff77e6`aae3ad27 fffff800`471ea94b : dxgmms2!VIDMM_GLOBAL::InvalidateAllVirtualAddresses+0x31ffffd001`43eb1870 fffff800`47422255 : ffffe001`bebb64c0 00000000`000000a3 ffffe001`bebb64c0 00000000`00000000 : dxgkrnl!DXGADAPTER::PrepareToReset+0x76ffffd001`43eb18c0 fffff800`4718e481 : ffffe001`bebb64c0 ffffd001`43eb1959 00000000`00a39d15 fffff800`471e6bea : dxgkrnl!TdrIsRecoveryRequired+0x1c5ffffd001`43eb18f0 fffff800`471bb0cc : ffffe001`afccb000 ffffd001`43eb1b00 ffffe001`afccb000 ffffe001`afc3e000 : dxgmms2!VidSchiReportHwHang+0x3fdffffd001`43eb19c0 fffff800`47175cac : ffffe001`afc3e000 00000000`007d75a5 00000000`00000001 00000000`00000002 : dxgmms2!VidSchiCheckHwProgress+0x137bcffffd001`43eb1a00 fffff800`471b3403 : ffffe001`afc3e000 ffffd001`43eb1bc8 ffffe001`bdbc7010 ffffe001`00000000 : dxgmms2!VidSchiScheduleCommandToRun+0x33cffffd001`43eb1b90 fffff800`471b33e0 : ffffe001`afc3e000 00000000`00000000 ffffe001`ad05a840 ffffe001`ad05a800 : dxgmms2!VidSchiRun_PriorityTable+0x1fffffd001`43eb1bc0 fffff802`15758e88 : ffffe001`ad05a840 ffffd001`43eb1c90 fffff802`159d5180 fffff802`157c5250 : dxgmms2!VidSchiWorkerThread+0x80ffffd001`43eb1c00 fffff802`157c5326 : fffff802`159d5180 ffffe001`afc3f840 fffff802`15a4b740 00000000`00000000 : nt!PspSystemThreadStartup+0x58ffffd001`43eb1c60 00000000`00000000 : ffffd001`43eb2000 ffffd001`43eac000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16STACK_COMMAND:  kbFOLLOWUP_IP: dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+121fffff800`47181e81 488bcb          mov     rcx,rbxSYMBOL_STACK_INDEX:  2SYMBOL_NAME:  dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+121FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: dxgmms2IMAGE_NAME:  dxgmms2.sysDEBUG_FLR_IMAGE_TIMESTAMP:  55bec217FAILURE_BUCKET_ID:  X64_0x10e_2e_dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+121BUCKET_ID:  X64_0x10e_2e_dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+121Followup: MachineOwner 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5967806
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Okay, ran the dump files through WinDBG:

 

Okay. Do you have BlueStacks installed? One of the faulting processes was "hd-network" which belongs to Bluestacks (the android app emulator).

I'm also seeing "NDU.sys" crashed a few times.

 

Did you by chance have any memory leaks and followed instructions to change anything in the registry? I also saw the post about the net.tcp issue, which actually showed up in a few BSODs as well.

 

You're best bet would be to:

Uninstall Bluestacks.

Repair install Windows after uninstalling Bluestacks: http://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html

 

As for your power issues, did this happen recently, or is it something new? Did you install Windows in UEFI mode or legacy mode?

 

I installed Bluestacks on the 27th I believe. And all these crashes started after the 27th, so that might be right.

The posting but not booting issue started back 1 - 2 weeks ago. It's happened about 4 times as well.

This morning, yesterday morning, and twice before that. It's also been VERY cold though and I tend to leave my window open and my PC is on the desk right next to the open window.

I'm not sure if it's UEFI or Legacy, how could I check?

 

Edit: Any idea about the Net.Tcp Listener Adapter?

Also I ran a memtest, 10 passed with 100%.

Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16463.amd64fre.th1.150819-1946Machine Name:Kernel base = 0xfffff803`be480000 PsLoadedModuleList = 0xfffff803`be7a5030Debug session time: Sun Sep  6 14:00:53.521 2015 (UTC - 4:00)System Uptime: 1 days 22:09:41.170********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high.  This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: 0000000000000036, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000001, value 0 = read operation, 1 = write operationArg4: fffff80147501d64, address which referenced memoryDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2WRITE_ADDRESS: unable to get nt!MmSpecialPoolStartunable to get nt!MmSpecialPoolEndunable to get nt!MmPagedPoolEndunable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes 0000000000000036 CURRENT_IRQL:  2FAULTING_IP: Ndu!NduOutboundMacClassifyProcessSingleNbl+d4fffff801`47501d64 4c8933          mov     qword ptr [rbx],r14CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  AVPROCESS_NAME:  SystemTRAP_FRAME:  ffffd001cafa8030 -- (.trap 0xffffd001cafa8030)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=ffffd001cafa8250rdx=ffffe000c041d710 rsi=0000000000000000 rdi=0000000000000000rip=fffff80147501d64 rsp=ffffd001cafa81c0 rbp=ffffd001cafa8240 r8=0000000000000000  r9=0000000000000000 r10=0000000000000051r11=0000000000000002 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei pl nz na po ncNdu!NduOutboundMacClassifyProcessSingleNbl+0xd4:fffff801`47501d64 4c8933          mov     qword ptr [rbx],r14 ds:00000000`00000000=0000000000000000Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff803be5d8ba9 to fffff803be5ce240STACK_TEXT:  ffffd001`cafa7ee8 fffff803`be5d8ba9 : 00000000`0000000a 00000000`00000036 00000000`00000002 00000000`00000001 : nt!KeBugCheckExffffd001`cafa7ef0 fffff803`be5d73c8 : 00000000`00000206 fffff803`be4c8639 ffffe000`c4127a40 ffffe000`c0595840 : nt!KiBugCheckDispatch+0x69ffffd001`cafa8030 fffff801`47501d64 : ffffe000`c54478e0 ffffd001`cafa8240 00000000`00000000 ffffe000`c41277c0 : nt!KiPageFault+0x248ffffd001`cafa81c0 fffff801`47501c62 : ffffe000`c41277c0 00060000`06000000 00000000`00000000 ffffe000`c41277c0 : Ndu!NduOutboundMacClassifyProcessSingleNbl+0xd4ffffd001`cafa8290 fffff801`44c3203d : ffffe000`b9540990 ffffd001`cafa8359 ffffe000`00000000 ffffe000`c41277c0 : Ndu!NduOutboundMacClassify+0x102ffffd001`cafa82f0 fffff801`44f3155b : ffffe000`b6d229a0 ffffd001`cafa8708 ffffe000`c41277c0 ffffe000`b82aa010 : NETIO!KfdClassify2+0x17dffffd001`cafa83c0 fffff801`44afc5fb : ffff50cd`ffbc1880 00000000`00000000 ffffe000`bca51010 00000000`000005ac : wfplwfs!LwfLowerSendNetBufferLists+0xdbffffd001`cafa8500 fffff801`44af191c : ffffd001`cafa85a0 ffffd001`00000000 00000004`00000008 ffffe000`bd985210 : ndis!ndisCallSendHandler+0x3bffffd001`cafa8550 fffff801`44d35cb8 : ffffe000`b82a6860 ffffe000`c41277c0 ffffe000`00000000 00000000`00000000 : ndis!NdisSendNetBufferLists+0x23cffffd001`cafa86d0 fffff801`44d30e45 : 00000000`0000003c ffffe000`ba941f00 ffffd001`cafa87c1 ffffe000`b82a6360 : tcpip!FlFastSendPackets+0xf8ffffd001`cafa8720 fffff801`44cdcbfe : 00000000`00000001 00000000`00000014 ffffe000`b82a9010 00000000`00000000 : tcpip!IpNlpFastContinueSendDatagram+0x335ffffd001`cafa8810 fffff801`44d309b3 : ffffd001`cafa8cf0 000005ac`00003e07 fffff801`44e89310 ffffe000`c877e360 : tcpip!IppSendDatagramsCommon+0x77effffd001`cafa8a80 fffff801`44d272a4 : 00000000`00000002 00000000`00000000 ffffe000`b9f9aa40 fffff801`44cf9c15 : tcpip!IpNlpFastSendDatagram+0x313ffffd001`cafa8b60 fffff801`44d266d1 : 00000000`00000002 00000000`00000000 ffffe000`b829f3b0 ffffe000`c3193350 : tcpip!TcpTcbHeaderSend+0x784ffffd001`cafa8e30 fffff801`44ce2bad : ffffe000`b7afd380 00000000`09e7ce97 ffffd001`cb719a22 00000182`ebb24473 : tcpip!TcpFlushDelay+0x131ffffd001`cafa8ec0 fffff801`44ce1b99 : ffffe000`b7af73c0 ffffd001`cafa9169 ffffd001`cafa9130 fffff801`00000000 : tcpip!TcpPreValidatedReceive+0x3adffffd001`cafa8fb0 fffff801`44ce1792 : 00000000`00000000 00001f80`0041026b 00000000`00000000 00000000`00000006 : tcpip!IppDeliverListToProtocol+0x59ffffd001`cafa9060 fffff801`44ce0be4 : 00000000`00000006 00000000`00000000 ffffd001`cafa9169 00000000`00000000 : tcpip!IppProcessDeliverList+0x62ffffd001`cafa90d0 fffff801`44ce1f28 : fffff801`44e89310 ffffe000`b7b13330 00000000`00000001 00000000`00000001 : tcpip!IppReceiveHeaderBatch+0x214ffffd001`cafa91d0 fffff801`44d4342f : ffffe000`b82a6360 ffffe000`b82a33b0 ffffd001`cafa9301 00000000`00000000 : tcpip!IppFlcReceivePacketsCore+0x338ffffd001`cafa92f0 fffff801`44d42a90 : 00000000`00000002 ffffd001`00000001 fffff801`44d338a0 00060000`00000001 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x25fffffd001`cafa93d0 fffff803`be4fc1f5 : 00000000`00000002 00000000`00000000 ffffe000`b79fb840 fffff801`44d429d0 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xc0ffffd001`cafa9500 fffff801`44d33cf6 : ffffe000`b7b10230 00000000`00000000 ffffe000`b7b101d0 ffffe000`b82a3300 : nt!KeExpandKernelStackAndCalloutInternal+0x85ffffd001`cafa9550 fffff801`44af95d3 : 00000000`00000000 ffffd001`cafa9650 ffffe000`00000001 fffff801`44afcf67 : tcpip!FlReceiveNetBufferListChain+0xb6ffffd001`cafa95d0 fffff801`44af930d : 00000000`00000001 ffffe000`b82a0000 00000000`00000000 fffff801`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0x133ffffd001`cafa9690 fffff801`44afcc33 : ffffe000`b812b1a0 00000000`00000000 fffff801`44af90e0 00000000`00000000 : ndis!ndisMTopReceiveNetBufferLists+0x22dffffd001`cafa9790 fffff801`44af2929 : ffffe000`b81f0402 ffffd001`cafa98e0 ffffd001`cafa9a78 fffff803`be5d2c76 : ndis!ndisCallReceiveHandler+0x43ffffd001`cafa97e0 fffff801`46a08ada : 00000000`00000000 ffffe000`b81ee000 ffffe000`b81eea30 ffffd001`cafa9a78 : ndis!NdisMIndicateReceiveNetBufferLists+0x479ffffd001`cafa9950 00000000`00000000 : ffffe000`b81ee000 ffffe000`b81eea30 ffffd001`cafa9a78 ffffe000`00000001 : e22w7x64+0x8adaSTACK_COMMAND:  kbFOLLOWUP_IP: Ndu!NduOutboundMacClassifyProcessSingleNbl+d4fffff801`47501d64 4c8933          mov     qword ptr [rbx],r14SYMBOL_STACK_INDEX:  3SYMBOL_NAME:  Ndu!NduOutboundMacClassifyProcessSingleNbl+d4FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: NduIMAGE_NAME:  Ndu.sysDEBUG_FLR_IMAGE_TIMESTAMP:  559f3a77FAILURE_BUCKET_ID:  X64_AV_Ndu!NduOutboundMacClassifyProcessSingleNbl+d4BUCKET_ID:  X64_AV_Ndu!NduOutboundMacClassifyProcessSingleNbl+d4Followup: MachineOwner 
Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16431.amd64fre.th1.150810-2333Machine Name:Kernel base = 0xfffff800`2f07f000 PsLoadedModuleList = 0xfffff800`2f3a4030Debug session time: Sat Aug 29 13:06:47.827 2015 (UTC - 4:00)System Uptime: 1 days 5:30:20.476********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************IRQL_NOT_LESS_OR_EQUAL (a)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high.  This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: ffffffffc2b60f06, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000001, bitfield :	bit 0 : value 0 = read operation, 1 = write operation	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)Arg4: fffff8002f1237e3, address which referenced memoryDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2WRITE_ADDRESS: unable to get nt!MmSpecialPoolStartunable to get nt!MmSpecialPoolEndunable to get nt!MmPagedPoolEndunable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes ffffffffc2b60f06 CURRENT_IRQL:  2FAULTING_IP: nt!KiIntSteerCalculateDistribution+93fffff800`2f1237e3 c1e106          shl     ecx,6CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  AVPROCESS_NAME:  SystemTRAP_FRAME:  fffff80030c36140 -- (.trap 0xfffff80030c36140)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000rip=fffff8002f1237e3 rsp=fffff80030c362d0 rbp=fffff80030c36300 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000r11=fffff80030c362f0 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei pl nz na po cynt!KiIntSteerCalculateDistribution+0x93:fffff800`2f1237e3 c1e106          shl     ecx,6Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff8002f1d76a9 to fffff8002f1ccd00STACK_TEXT:  fffff800`30c35ff8 fffff800`2f1d76a9 : 00000000`0000000a ffffffff`c2b60f06 00000000`00000002 00000000`00000001 : nt!KeBugCheckExfffff800`30c36000 fffff800`2f1d5ec8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69fffff800`30c36140 fffff800`2f1237e3 : ffffe001`ea403530 fffff800`2f1237ab ffffe001`e91d0ae0 00000000`00000000 : nt!KiPageFault+0x248fffff800`30c362d0 fffff800`2f123345 : fffff800`30c36460 fffff800`2f123cb8 00000000`00000001 00000000`00000000 : nt!KiIntSteerCalculateDistribution+0x93fffff800`30c36340 fffff800`2f122145 : 00000000`00000014 fffff800`30c36500 00000000`0cb08c62 fffff800`30c36500 : nt!KeIntSteerPeriodic+0x65fffff800`30c36400 fffff800`2f088308 : 00000000`0cb08c62 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PpmParkSteerInterrupts+0x575fffff800`30c36810 fffff800`2f0ce735 : ffffe001`ed0fe080 fffff800`2f3e4f00 fffff800`30c369c0 fffff800`30c36b30 : nt!PpmCheckStart+0x178fffff800`30c368c0 fffff800`2f0cde10 : ffffe001`fb44ca20 fffff800`30c36b20 fffff800`30c36b10 00000000`00000001 : nt!KiExecuteAllDpcs+0x275fffff800`30c36a10 fffff800`2f1cfa5a : fffff800`2f3e2180 fffff800`2f3e2180 fffff800`2f458740 ffffe001`eb7b7080 : nt!KiRetireDpcList+0xe0fffff800`30c36c60 00000000`00000000 : fffff800`30c37000 fffff800`30c31000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5aSTACK_COMMAND:  kbFOLLOWUP_IP: nt!KiIntSteerCalculateDistribution+93fffff800`2f1237e3 c1e106          shl     ecx,6SYMBOL_STACK_INDEX:  3SYMBOL_NAME:  nt!KiIntSteerCalculateDistribution+93FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP:  55c9bcb6FAILURE_BUCKET_ID:  X64_AV_nt!KiIntSteerCalculateDistribution+93BUCKET_ID:  X64_AV_nt!KiIntSteerCalculateDistribution+93Followup: MachineOwner 
Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16431.amd64fre.th1.150810-2333Machine Name:Kernel base = 0xfffff801`d7409000 PsLoadedModuleList = 0xfffff801`d772e030Debug session time: Mon Aug 31 09:45:18.336 2015 (UTC - 4:00)System Uptime: 1 days 20:37:51.984********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************UNEXPECTED_KERNEL_MODE_TRAP (7f)This means a trap occurred in kernel mode, and it's a trap of a kindthat the kernel isn't allowed to have/catch (bound trap) or thatis always instant death (double fault).  The first number in thebugcheck params is the number of the trap (8 = double fault, etc)Consult an Intel x86 family manual to learn more about what thesetraps are. Here is a *portion* of those codes:If kv shows a taskGate        use .tss on the part before the colon, then kv.Else if kv shows a trapframe        use .trap on that valueElse        .trap on the appropriate frame will show where the trap was taken        (on x86, this will be the ebp that goes with the procedure KiTrap)Endifkb will then show the corrected stack.Arguments:Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULTArg2: fffff801d903ae70Arg3: 0000000000000000Arg4: fffff801d742fa6cDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x7f_8CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  Origin.exeCURRENT_IRQL:  2LAST_CONTROL_TRANSFER:  from fffff801d75616a9 to fffff801d7556d00STACK_TEXT:  fffff801`d903ad28 fffff801`d75616a9 : 00000000`0000007f 00000000`00000008 fffff801`d903ae70 00000000`00000000 : nt!KeBugCheckExfffff801`d903ad30 fffff801`d755f774 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69fffff801`d903ae70 fffff801`d742fa6c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb400000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFlushTbList+0x2ccSTACK_COMMAND:  kbFOLLOWUP_IP: nt!KiDoubleFaultAbort+b4fffff801`d755f774 90              nopSYMBOL_STACK_INDEX:  2SYMBOL_NAME:  nt!KiDoubleFaultAbort+b4FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP:  55c9bcb6FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b4BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b4Followup: MachineOwner 
Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16431.amd64fre.th1.150810-2333Machine Name:Kernel base = 0xfffff801`a7a7a000 PsLoadedModuleList = 0xfffff801`a7d9f030Debug session time: Tue Sep  1 16:56:47.829 2015 (UTC - 4:00)System Uptime: 1 days 7:10:48.479********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************PAGE_FAULT_IN_NONPAGED_AREA (50)Invalid system memory was referenced.  This cannot be protected by try-except,it must be protected by a Probe.  Typically the address is just plain bad or itis pointing at freed memory.Arguments:Arg1: ffffd00023f6f598, memory referenced.Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.Arg3: fffff801a7e845df, If non-zero, the instruction address which referenced the bad memory	address.Arg4: 0000000000000000, (reserved)Debugging Details:------------------Could not read faulting driver nameTRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2WRITE_ADDRESS: unable to get nt!MmSpecialPoolStartunable to get nt!MmSpecialPoolEndunable to get nt!MmPagedPoolEndunable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes ffffd00023f6f598 FAULTING_IP: nt!MiInsertSharedCommitNode+37ffffff801`a7e845df c68424d800000000 mov     byte ptr [rsp+0D8h],0MM_INTERNAL_CODE:  0CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  AVPROCESS_NAME:  ts3client_win6CURRENT_IRQL:  2TRAP_FRAME:  ffffd00023f6d330 -- (.trap 0xffffd00023f6d330)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=ffffe000a6beb840rdx=ffffc00173f61840 rsi=0000000000000000 rdi=0000000000000000rip=fffff801a7e845df rsp=ffffd00023f6d4c0 rbp=0000000000000003 r8=ffffe000a6487ad0  r9=0000000000000001 r10=ffffc00165c70598r11=0000000000000000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei pl zr na po ncnt!MiInsertSharedCommitNode+0x37f:fffff801`a7e845df c68424d800000000 mov     byte ptr [rsp+0D8h],0 ss:0018:ffffd000`23f6d598=00Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff801a7c1804a to fffff801a7bc7d00STACK_TEXT:  ffffd000`23f6d0e8 fffff801`a7c1804a : 00000000`00000050 ffffd000`23f6f598 00000000`00000002 ffffd000`23f6d330 : nt!KeBugCheckExffffd000`23f6d0f0 fffff801`a7a99536 : 00000000`00000002 00000000`00000000 ffffd000`23f6d330 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4174affffd000`23f6d1e0 fffff801`a7bd0dbd : 00000002`0000000c 00000000`00000000 ffffc001`6a06fe20 ffffe000`a6aed290 : nt!MmAccessFault+0x696ffffd000`23f6d330 fffff801`a7e845df : 00000000`00000000 00000000`00000000 00000000`000007ff ffffd001`5608f000 : nt!KiPageFault+0x13dffffd000`23f6d4c0 fffff801`a7e845a3 : ffffc001`65310f00 ffffe000`a6beb840 00000000`00000000 00000000`00000000 : nt!MiInsertSharedCommitNode+0x37fffffd000`23f6d580 fffff801`a7e9d52c : ffffc001`6547add0 00000000`00000000 00000000`00000001 ffffe000`a6bebf01 : nt!MiInsertSharedCommitNode+0x343ffffd000`23f6d640 fffff801`a7e9b493 : ffffe000`a1d09f30 00000000`00000000 00000000`00000002 ffffc001`654177f0 : nt!ObpIncrementHandleCountEx+0x3acffffd000`23f6d730 fffff801`a7f004d7 : ffffe000`ad270010 00000000`00000000 ffffc001`64e6d1a8 ffffe000`a1d09f20 : nt!ObpCreateHandle+0x373ffffd000`23f6d970 fffff801`a7f8c0e7 : ffffe000`00000001 000000aa`7610f7a8 00007ff8`26302058 00000000`00000020 : nt!ObOpenObjectByName+0x337ffffd000`23f6daa0 fffff801`a7bd2363 : ffffe000`a6a2a080 00000000`ffffffff 00000000`00000000 ffffe000`a686bf00 : nt!NtOpenSection+0x67ffffd000`23f6db00 00007ff8`48ec386a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13000000aa`7610f6f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff8`48ec386aSTACK_COMMAND:  kbFOLLOWUP_IP: nt!MiInsertSharedCommitNode+37ffffff801`a7e845df c68424d800000000 mov     byte ptr [rsp+0D8h],0SYMBOL_STACK_INDEX:  4SYMBOL_NAME:  nt!MiInsertSharedCommitNode+37fFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP:  55c9bcb6IMAGE_NAME:  memory_corruptionFAILURE_BUCKET_ID:  X64_AV_nt!MiInsertSharedCommitNode+37fBUCKET_ID:  X64_AV_nt!MiInsertSharedCommitNode+37fFollowup: MachineOwner 
Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16463.amd64fre.th1.150819-1946Machine Name:Kernel base = 0xfffff800`c7816000 PsLoadedModuleList = 0xfffff800`c7b3b030Debug session time: Wed Sep  2 16:14:10.907 2015 (UTC - 4:00)System Uptime: 0 days 4:11:41.555********************************************************************************                                                                             **                        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 ofthe problem, and then special pool applied to the suspect tags or the driververifier to a suspect driver.Arguments:Arg1: 0000000000000003, the pool freelist is corrupt.Arg2: ffffe00194c0d220, the pool entry being checked.Arg3: ffffe00194c0d220, the read back flink freelist value (should be the same as 2).Arg4: 6c894cce8b495f45, the read back blink freelist value (should be the same as 2).Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x19_3CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  HD-Network.exeCURRENT_IRQL:  2LAST_CONTROL_TRANSFER:  from fffff800c7a8a97e to fffff800c7964240STACK_TEXT:  ffffd000`225214f8 fffff800`c7a8a97e : 00000000`00000019 00000000`00000003 ffffe001`94c0d220 ffffe001`94c0d220 : nt!KeBugCheckExffffd000`22521500 fffff800`c7862051 : ffffe001`00000200 00000000`00001000 00000000`00000001 00000000`00000000 : nt!ExFreePool+0xcb6ffffd000`225215e0 fffff800`47701a51 : fffff800`c7b70d00 ffffe001`917c6f70 ffffd001`50646641 fffff800`00000001 : nt!ExAllocatePoolWithQuotaTag+0x61ffffd000`22521670 fffff800`477189ae : ffffe001`92c50100 ffffd000`225216e0 00000000`000007ff ffffd001`28292000 : afd!AfdPollGetInfo+0x21ffffd000`225216b0 fffff800`47700d15 : 00000000`00012000 ffffe001`917c6f20 ffffe001`c000000d ffffd000`22521b80 : afd!AfdPoll32+0xf6ffffd000`225217d0 fffff800`c7c4417d : 00000000`00000000 ffffd000`22521b80 ffffe001`94c51e10 fffff800`00000001 : afd!AfdPoll+0x35ffffd000`22521800 fffff800`c7c43a56 : e00190a3`49406ce9 00000000`001f0003 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x71dffffd000`22521a20 fffff800`c796e863 : 00000000`00000000 00000000`00000001 00000000`00000001 00000000`67c7bb01 : nt!NtDeviceIoControlFile+0x56ffffd000`22521a90 00000000`67be1e52 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`0009efd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x67be1e52STACK_COMMAND:  kbFOLLOWUP_IP: nt!ExFreePool+cb6fffff800`c7a8a97e cc              int     3SYMBOL_STACK_INDEX:  1SYMBOL_NAME:  nt!ExFreePool+cb6FOLLOWUP_NAME:  Pool_corruptionIMAGE_NAME:  Pool_CorruptionDEBUG_FLR_IMAGE_TIMESTAMP:  0MODULE_NAME: Pool_CorruptionFAILURE_BUCKET_ID:  X64_0x19_3_nt!ExFreePool+cb6BUCKET_ID:  X64_0x19_3_nt!ExFreePool+cb6Followup: Pool_corruption 
Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16463.amd64fre.th1.150819-1946Machine Name:Kernel base = 0xfffff801`ce081000 PsLoadedModuleList = 0xfffff801`ce3a6030Debug session time: Wed Sep  2 12:01:52.058 2015 (UTC - 4:00)System Uptime: 0 days 5:26:26.707********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high.  This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: ffffe00286c42130, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000000, value 0 = read operation, 1 = write operationArg4: fffff8002b8e2b18, address which referenced memoryDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2READ_ADDRESS: unable to get nt!MmSpecialPoolStartunable to get nt!MmSpecialPoolEndunable to get nt!MmPagedPoolEndunable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes ffffe00286c42130 CURRENT_IRQL:  2FAULTING_IP: NETIO!RtlGetNextExpiredTimerWheelEntry+e8fffff800`2b8e2b18 418b4010        mov     eax,dword ptr [r8+10h]CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  AVPROCESS_NAME:  SystemTRAP_FRAME:  fffff801cfc38530 -- (.trap 0xfffff801cfc38530)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffffe00086c42120 rbx=0000000000000000 rcx=ffffe00086c41638rdx=ffffe00086c42120 rsi=0000000000000000 rdi=0000000000000000rip=fffff8002b8e2b18 rsp=fffff801cfc386c8 rbp=fffff801cfc387d0 r8=ffffe00286c42120  r9=00000000012adef2 r10=000000000000001dr11=00000000012c5e88 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei pl nz na pe ncNETIO!RtlGetNextExpiredTimerWheelEntry+0xe8:fffff800`2b8e2b18 418b4010        mov     eax,dword ptr [r8+10h] ds:ffffe002`86c42130=????????Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff801ce1d9ba9 to fffff801ce1cf240STACK_TEXT:  fffff801`cfc383e8 fffff801`ce1d9ba9 : 00000000`0000000a ffffe002`86c42130 00000000`00000002 00000000`00000000 : nt!KeBugCheckExfffff801`cfc383f0 fffff801`ce1d83c8 : 00000000`00000000 ffffe000`897c5000 ffffe000`897c3000 00000000`ffffffff : nt!KiBugCheckDispatch+0x69fffff801`cfc38530 fffff800`2b8e2b18 : fffff800`2b9d5767 00000000`012adf2e ffffe000`884fe010 00000000`0000001c : nt!KiPageFault+0x248fffff801`cfc386c8 fffff800`2b9d5767 : 00000000`012adf2e ffffe000`884fe010 00000000`0000001c ffffe000`884fe010 : NETIO!RtlGetNextExpiredTimerWheelEntry+0xe8fffff801`cfc386d0 fffff801`ce0d0735 : fffff801`ce3e6f00 ffffd000`ca1465b0 fffff801`cfc38b20 ffffe000`884fe0b0 : tcpip!TcpPeriodicTimeoutHandler+0xe67fffff801`cfc388c0 fffff801`ce0cfe10 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x275fffff801`cfc38a10 fffff801`ce1d1f9a : fffff801`ce3e4180 fffff801`ce3e4180 fffff801`ce45a740 ffffe000`8d49a080 : nt!KiRetireDpcList+0xe0fffff801`cfc38c60 00000000`00000000 : fffff801`cfc39000 fffff801`cfc33000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5aSTACK_COMMAND:  kbFOLLOWUP_IP: NETIO!RtlGetNextExpiredTimerWheelEntry+e8fffff800`2b8e2b18 418b4010        mov     eax,dword ptr [r8+10h]SYMBOL_STACK_INDEX:  3SYMBOL_NAME:  NETIO!RtlGetNextExpiredTimerWheelEntry+e8FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: NETIOIMAGE_NAME:  NETIO.SYSDEBUG_FLR_IMAGE_TIMESTAMP:  559f3890FAILURE_BUCKET_ID:  X64_AV_NETIO!RtlGetNextExpiredTimerWheelEntry+e8BUCKET_ID:  X64_AV_NETIO!RtlGetNextExpiredTimerWheelEntry+e8Followup: MachineOwner 
Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16463.amd64fre.th1.150819-1946Machine Name:Kernel base = 0xfffff801`8ca18000 PsLoadedModuleList = 0xfffff801`8cd3d030Debug session time: Fri Sep  4 14:26:57.426 2015 (UTC - 4:00)System Uptime: 0 days 0:03:59.075********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************KMODE_EXCEPTION_NOT_HANDLED (1e)This is a very common bugcheck.  Usually the exception address pinpointsthe driver/function that caused the problem.  Always note this addressas well as the link date of the driver/image that contains this address.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff8018cabd0c7, The address that the exception occurred atArg3: 0000000000000000, Parameter 0 of the exceptionArg4: ffffffffffffffff, Parameter 1 of the exceptionDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".FAULTING_IP: nt!KeIntSteerSnapPerf+e7fffff801`8cabd0c7 480391b0000000  add     rdx,qword ptr [rcx+0B0h]EXCEPTION_PARAMETER1:  0000000000000000EXCEPTION_PARAMETER2:  ffffffffffffffffREAD_ADDRESS: unable to get nt!MmSpecialPoolStartunable to get nt!MmSpecialPoolEndunable to get nt!MmPagedPoolEndunable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes ffffffffffffffff ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".BUGCHECK_STR:  0x1e_c0000005CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  2EXCEPTION_RECORD:  ffffe000ea8264d8 -- (.exr 0xffffe000ea8264d8)Cannot read Exception record @ ffffe000ea8264d8TRAP_FRAME:  ffffd00091a09198 -- (.trap 0xffffd00091a09198)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffffe000ea907600 rbx=0000000000000000 rcx=0000000000000000rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000rip=ffffd00091a092f0 rsp=fffff8018d26b372 rbp=ffffe00000000000 r8=ffffd00022ff3400  r9=ffffe000ea907600 r10=0000000000000000r11=ffffe000edeff010 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up di pl nz na pe ncaf99:ffffd000`91a092f0 0000            add     byte ptr [rax],al ds:ffffe000`ea907600=??Resetting default scopeUNALIGNED_STACK_POINTER:  fffff8018d26b372LAST_CONTROL_TRANSFER:  from fffff8018cc099d6 to fffff8018cb66240CONTEXT:  8349000000c88103 -- (.cxr 0x8349000000c88103)Unable to read context, Win32 error 0n30STACK_TEXT:  ffffd000`91a081c8 fffff801`8cc099d6 : 00000000`0000001e ffffffff`c0000005 fffff801`8cabd0c7 00000000`00000000 : nt!KeBugCheckExffffd000`91a081d0 fffff801`8cb6c27d : fffff801`8cd8f000 fffff801`8ca18000 0004c41c`00852000 ffffd000`91a08202 : nt!KiFatalExceptionHandler+0x22ffffd000`91a08210 fffff801`8ca8c050 : 00000000`00000000 fffff801`8cd92a00 ffffd000`91a09168 fffff800`4b173519 : nt!RtlpExecuteHandlerForException+0xdffffd000`91a08240 fffff801`8ca88c78 : ffffd000`91a09168 ffffd000`91a08e80 ffffd000`91a09168 00000000`00000001 : nt!RtlDispatchException+0x4e8ffffd000`91a08950 fffff801`8cb70c82 : ffffe000`ea8264d8 00000000`00000000 ffffd000`91a09198 ffffe000`ea8a9100 : nt!KiDispatchException+0x144ffffd000`91a09030 fffff801`8cb6f17e : 00000000`00000001 ffffe000`ec534040 ffff174a`87a4b289 00000000`00000000 : nt!KiExceptionDispatch+0xc2ffffd000`91a09210 fffff801`8cabd0c7 : 00000000`00075bd0 ffffd000`91a09500 00000000`00000000 fffff801`8d26b854 : nt!KiGeneralProtectionFault+0xfeffffd000`91a093a0 fffff801`8cabb1a2 : 00000000`00000002 00000000`2f58674d 00000000`00075bd0 ffffd000`91a09500 : nt!KeIntSteerSnapPerf+0xe7ffffd000`91a09400 fffff801`8ca21308 : 00000000`00075bd0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PpmParkSteerInterrupts+0x92ffffd000`91a09810 fffff801`8ca67735 : ffffd000`96647180 ffffd000`96649f00 ffffd000`91a099c0 ffffd000`91a09b20 : nt!PpmCheckStart+0x178ffffd000`91a098c0 fffff801`8ca66e10 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x275ffffd000`91a09a10 fffff801`8cb68f9a : ffffd000`96647180 ffffd000`96647180 ffffd000`96653bc0 ffffe000`ea6c7080 : nt!KiRetireDpcList+0xe0ffffd000`91a09c60 00000000`00000000 : ffffd000`91a0a000 ffffd000`91a04000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5aFOLLOWUP_IP: nt!KeIntSteerSnapPerf+e7fffff801`8cabd0c7 480391b0000000  add     rdx,qword ptr [rcx+0B0h]SYMBOL_STACK_INDEX:  7SYMBOL_NAME:  nt!KeIntSteerSnapPerf+e7FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP:  55d5626bSTACK_COMMAND:  .cxr 0x8349000000c88103 ; kbFAILURE_BUCKET_ID:  X64_0x1e_c0000005_nt!KeIntSteerSnapPerf+e7BUCKET_ID:  X64_0x1e_c0000005_nt!KeIntSteerSnapPerf+e7Followup: MachineOwner 
Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16463.amd64fre.th1.150819-1946Machine Name:Kernel base = 0xfffff800`35c1d000 PsLoadedModuleList = 0xfffff800`35f42030Debug session time: Fri Sep  4 14:22:23.259 2015 (UTC - 4:00)System Uptime: 0 days 3:52:26.907********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************MEMORY_MANAGEMENT (1a)    # Any other values for parameter 1 must be individually examined.Arguments:Arg1: 0000000000061941, The subtype of the bugcheck.Arg2: 000000005e1d49f0Arg3: 000000000000000dArg4: ffffd00024555b00Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x1a_61941CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  Battle.net.exeCURRENT_IRQL:  0LAST_CONTROL_TRANSFER:  from fffff80035d89888 to fffff80035d6b240STACK_TEXT:  ffffd000`245559a8 fffff800`35d89888 : 00000000`0000001a 00000000`00061941 00000000`5e1d49f0 00000000`0000000d : nt!KeBugCheckExffffd000`245559b0 fffff800`35d742bd : ffffe000`91bf2840 00000000`00000dd1 ffffd000`00000000 ffffe000`91412c10 : nt! ?? ::FNODOBFM::`string'+0xfa88ffffd000`24555b00 00000000`5e11b339 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13d00000000`00c7f794 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5e11b339STACK_COMMAND:  kbFOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+fa88fffff800`35d89888 cc              int     3SYMBOL_STACK_INDEX:  1SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+fa88FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP:  55d5626bFAILURE_BUCKET_ID:  X64_0x1a_61941_nt!_??_::FNODOBFM::_string_+fa88BUCKET_ID:  X64_0x1a_61941_nt!_??_::FNODOBFM::_string_+fa88Followup: MachineOwner 
Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16463.amd64fre.th1.150819-1946Machine Name:Kernel base = 0xfffff802`15672000 PsLoadedModuleList = 0xfffff802`15997030Debug session time: Fri Sep  4 10:29:10.563 2015 (UTC - 4:00)System Uptime: 1 days 11:41:13.212********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)The video memory manager encountered a condition that it can't recover from. By crashing,the video memory manager is attempting to get enough information into the minidump such thatsomebody can pinpoint what lead to this condition.Arguments:Arg1: 000000000000002e, The subtype of the bugcheck:Arg2: ffffc00177e6c7e0Arg3: ffffc0018cfcbad0Arg4: ffffd00143eb1730Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x10e_2eCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  0LAST_CONTROL_TRANSFER:  from fffff800472c3c3d to fffff802157c0240STACK_TEXT:  ffffd001`43eb16c8 fffff800`472c3c3d : 00000000`0000010e 00000000`0000002e ffffc001`77e6c7e0 ffffc001`8cfcbad0 : nt!KeBugCheckExffffd001`43eb16d0 fffff800`47181e81 : ffffc001`7a354420 ffffc001`77e6c7e0 ffffc001`77e6c7e0 ffffe001`00000003 : watchdog!WdLogEvent5_WdCriticalError+0xcdffffd001`43eb1710 fffff800`471e0167 : ffffc001`77e6c7e0 ffffe001`afce8e40 ffffc001`7b9dcea0 ffffc001`8cfcbad0 : dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+0x121ffffd001`43eb1760 fffff800`471be885 : 00000000`00000000 00000000`00000001 ffffd001`43eb1959 00000000`000000a3 : dxgmms2!VIDMM_SEGMENT::InvalidateAllVirtualAddress+0x19bffffd001`43eb1840 fffff800`4740c486 : ffffe001`afc413b0 00000000`00000000 ffff77e6`aae3ad27 fffff800`471ea94b : dxgmms2!VIDMM_GLOBAL::InvalidateAllVirtualAddresses+0x31ffffd001`43eb1870 fffff800`47422255 : ffffe001`bebb64c0 00000000`000000a3 ffffe001`bebb64c0 00000000`00000000 : dxgkrnl!DXGADAPTER::PrepareToReset+0x76ffffd001`43eb18c0 fffff800`4718e481 : ffffe001`bebb64c0 ffffd001`43eb1959 00000000`00a39d15 fffff800`471e6bea : dxgkrnl!TdrIsRecoveryRequired+0x1c5ffffd001`43eb18f0 fffff800`471bb0cc : ffffe001`afccb000 ffffd001`43eb1b00 ffffe001`afccb000 ffffe001`afc3e000 : dxgmms2!VidSchiReportHwHang+0x3fdffffd001`43eb19c0 fffff800`47175cac : ffffe001`afc3e000 00000000`007d75a5 00000000`00000001 00000000`00000002 : dxgmms2!VidSchiCheckHwProgress+0x137bcffffd001`43eb1a00 fffff800`471b3403 : ffffe001`afc3e000 ffffd001`43eb1bc8 ffffe001`bdbc7010 ffffe001`00000000 : dxgmms2!VidSchiScheduleCommandToRun+0x33cffffd001`43eb1b90 fffff800`471b33e0 : ffffe001`afc3e000 00000000`00000000 ffffe001`ad05a840 ffffe001`ad05a800 : dxgmms2!VidSchiRun_PriorityTable+0x1fffffd001`43eb1bc0 fffff802`15758e88 : ffffe001`ad05a840 ffffd001`43eb1c90 fffff802`159d5180 fffff802`157c5250 : dxgmms2!VidSchiWorkerThread+0x80ffffd001`43eb1c00 fffff802`157c5326 : fffff802`159d5180 ffffe001`afc3f840 fffff802`15a4b740 00000000`00000000 : nt!PspSystemThreadStartup+0x58ffffd001`43eb1c60 00000000`00000000 : ffffd001`43eb2000 ffffd001`43eac000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16STACK_COMMAND:  kbFOLLOWUP_IP: dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+121fffff800`47181e81 488bcb          mov     rcx,rbxSYMBOL_STACK_INDEX:  2SYMBOL_NAME:  dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+121FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: dxgmms2IMAGE_NAME:  dxgmms2.sysDEBUG_FLR_IMAGE_TIMESTAMP:  55bec217FAILURE_BUCKET_ID:  X64_0x10e_2e_dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+121BUCKET_ID:  X64_0x10e_2e_dxgmms2!VIDMM_CPU_HOST_APERTURE::UnmapRange+121Followup: MachineOwner 
Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5969040
Share on other sites
Link to post
Share on other sites
Posted
  • Author

@ionbasa

 

Computer just lost power or something. I was using google chrome (about 6 tabs), skype, spotify, and teamspeak. The power supply was still running the water cooler leds were on and all the other board lights were on but the fans were not spinning on anything. I had to hold down power button then flip power supply switch to turn it back on again. No idea why it's doing that, I should have more than enough power and the power supply isn't old.

 

Lost power again, Event viewer says this for both time : The Service KMSELDI service terminated unexpectedly.  It has done this 1 time(s).

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5970531
Share on other sites
Link to post
Share on other sites
Posted

@ionbasa

 

Computer just lost power or something. I was using google chrome (about 6 tabs), skype, spotify, and teamspeak. The power supply was still running the water cooler leds were on and all the other board lights were on but the fans were not spinning on anything. I had to hold down power button then flip power supply switch to turn it back on again. No idea why it's doing that, I should have more than enough power and the power supply isn't old.

Bad PSU. I'd get it RMA'd. Would also explain your problematic power issues.

After you get an replacement PSU, go ahead and run a repair install of Windows: http://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5970938
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Bad PSU. I'd get it RMA'd. Would also explain your problematic power issues.

After you get an replacement PSU, go ahead and run a repair install of Windows: http://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html

 

Faaaaaq...

 

Maybe my other psu will work. I replaced it with this current one because I thought the last one was busted but it ended up being my GPU.

I'll try hooking it up tomorrow I guess. 

 

I'm running a repair install for Windows right now actually.

 

 

It says I'll need proof of purchase.. I purchased this from best buy like 6 months ago I doubt I still have the receipt for it lying around.

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5971143
Share on other sites
Link to post
Share on other sites
Posted

Faaaaaq...

 

Maybe my other psu will work. I replaced it with this current one because I thought the last one was busted but it ended up being my GPU.

I'll try hooking it up tomorrow I guess. 

 

I'm running a repair install for Windows right now actually.

 

 

It says I'll need proof of purchase.. I purchased this from best buy like 6 months ago I doubt I still have the receipt for it lying around.

If you paid with Debit/Credit they can look it up. You have to bring our card with you and they'll run it in their system. You should be able to ask for an copy of the receipt that way.

 

Note: if they say they can't ask if they can check with their bookkeeping dept/person; they're legally required to keep copies for accountability.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5971172
Share on other sites
Link to post
Share on other sites
Posted
  • Author

If you paid with Debit/Credit they can look it up. You have to bring our card with you and they'll run it in their system. You should be able to ask for an copy of the receipt that way.

 

Note: if they say they can't ask if they can check with their bookkeeping dept/person; they're legally required to keep copies for accountability.

 

I found the debt card purchase on my paypal. It's from December 2014, so I should be able to go in to best buy with my paypal card and get the receipt?

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5971195
Share on other sites
Link to post
Share on other sites
Posted
  • Author

If you paid with Debit/Credit they can look it up. You have to bring our card with you and they'll run it in their system. You should be able to ask for an copy of the receipt that way.

 

Note: if they say they can't ask if they can check with their bookkeeping dept/person; they're legally required to keep copies for accountability.

 

What would your suggestion be for saying in the rma ticket? Like what is wrong with it.

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5971261
Share on other sites
Link to post
Share on other sites
Posted

What would your suggestion be for saying in the rma ticket? Like what is wrong with it.

Have you verified that your backup PSU doesn't have that issue? You could just simply state that the PSU cuts off and sometimes wont power on your motherboard.

 

I found the debt card purchase on my paypal. It's from December 2014, so I should be able to go in to best buy with my paypal card and get the receipt?

Possibly. They may say no, but it's worth a shot. I pay with business accounts and have never been denied an recept copy from any brick and mortar store. Not sure about consumer accounts though.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5971312
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Have you verified that your backup PSU doesn't have that issue? You could just simply state that the PSU cuts off and sometimes wont power on your motherboard.

 

Possibly. They may say no, but it's worth a shot. I pay with business accounts and have never been denied an recept copy from any brick and mortar store. Not sure about consumer accounts though.

 

It's a business paypal and from what their FAQ says they can get receipts for up to 2 years ago.

 

Edit: I can't verify if my backup PSU works or not right now, I have the actual PSU in my hands but the wires are modular and in my closet in a box a bit out of the way. It's too late to go rummaging around through the closet. I'll have to wait til day time.

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5971335
Share on other sites
Link to post
Share on other sites
Posted
  • Author

@ionbasa

 

Would you say the psu is causing all of these BSODs?

 

I just got another one while watching a youtube video,

 

 On Mon 9/7/2015 6:03:00 AM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\090615-10765-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x2197C4)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800E01F97C4, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 355.82
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 355.82
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 355.82 , NVIDIA Corporation).
Google query: NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED 

 

Let me know if you want dump files or something.

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5971539
Share on other sites
Link to post
Share on other sites
Posted

@ionbasa

 

Would you say the psu is causing all of these BSODs?

 

I just got another one while watching a youtube video,

 

 On Mon 9/7/2015 6:03:00 AM GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\090615-10765-01.dmp

This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x2197C4)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800E01F97C4, 0x0, 0xFFFFFFFFFFFFFFFF)

Error: KMODE_EXCEPTION_NOT_HANDLED

file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys

product: NVIDIA Windows Kernel Mode Driver, Version 355.82

company: NVIDIA Corporation

description: NVIDIA Windows Kernel Mode Driver, Version 355.82

Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 355.82 , NVIDIA Corporation).

Google query: NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED 

 

Let me know if you want dump files or something.

Im guessing you already repair installed windows per the instructions I provided?

 

Looking at the log you provided, it was GPu related, but here is the deal: If your PSU isn't providing the wattage needed to the components, and you've been having issues with power offs, hangs, and issues at boot, then it would likely be an PSU issue.

 

What wattage PSU are you running? If you can check with another PSU, then you can know for sure. 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5971561
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Im guessing you already repair installed windows per the instructions I provided?

 

Looking at the log you provided, it was GPu related, but here is the deal: If your PSU isn't providing the wattage needed to the components, and you've been having issues with power offs, hangs, and issues at boot, then it would likely be an PSU issue.

 

What wattage PSU are you running? If you can check with another PSU, then you can know for sure. 

 

750w.

 

I don't know if my backup PSU actually works or not. 

I'm going to go to bed in a few minutes here, and find out tomorrow if for one the backup works and if I have the same issues.

The back up is a 850w EVGA.

 

The gpu I have has been refurbished by MSI once. I had to rma it because a transistor or something like that blew up on it and it started a small smoke pile in my computer. I sent it to them and they fixed it, this was about 5 months ago.

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5971575
Share on other sites
Link to post
Share on other sites
Posted

750w.

 

I don't know if my backup PSU actually works or not. 

I'm going to go to bed in a few minutes here, and find out tomorrow if for one the backup works and if I have the same issues.

The back up is a 850w EVGA.

 

The gpu I have has been refurbished by MSI once. I had to rma it because a transistor or something like that blew up on it and it started a small smoke pile in my computer. I sent it to them and they fixed it, this was about 5 months ago.

Keep us posted. Honestly, I;d trust the Evga PSU over what you are currently running. Never had any issues with EVGA, although I had one ship DOA on a friends build.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5971604
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Keep us posted. Honestly, I;d trust the Evga PSU over what you are currently running. Never had any issues with EVGA, although I had one ship DOA on a friends build.

 

I'll post an update when I wake up and test it out, just need to grab the wires out of the closet and plug it all up and see what happens. I'm off for now though.

Thanks for the endless help, once again.

Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5971655
Share on other sites
Link to post
Share on other sites
Posted (edited)
  • Author

Bad PSU. I'd get it RMA'd. Would also explain your problematic power issues.

After you get an replacement PSU, go ahead and run a repair install of Windows: http://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html

 

I plugged the EVGA psu to the motherboard and plugged it to an outlet. Whenever I hit the power button the fan on the psu and the fans on the computer spin for about 2 seconds then stop. If I held the power button on the computer the fans lasted much longer (4 - 10 seconds) but then turned off again. Any thoughts or is it dead?

 

Edit: I've submitted an RMA for the Corsair and the EVGA PSU. (EVGA is 750W Gold not 850W.)

What I think would be the best for me is to RMA the EVGA first, wait for it to come back. Swap out the PSU's then RMA the Corsair so I have a back up PSU in the future. I can live with crashing every once in a while but I'd be unable to purchase a new PSU at the moment while these both RMA.

 

Got a response from Corsair already

 

Created By: Zack TS (9/7/2015 1:36 AM)

Please test your PSU with a paper clip test, check the voltage rails for your PSU by going to your BIOS and ensuring +3.3V, +5V, and +12V are within 5% of the values listed. And test your system with another PSU and GPU if possible. We'll be more than happy to replace it for you if it comes back with an error. Thank you. 

 

Please attach a photo/screenshot/PDF of the receipt/invoice to the ticket so that we can validate the warranty. The attachment area is at the bottom of this screen. Afterwards respond back with a ticket comment so that we know it's been attached, thanks.

 

I'll get the receipt within a week from now probably, and using the paper clip wouldn't help much, the crashes are so random. I could play an intense game for hours with no issues or I could be watching a youtube video and it crashes. So I don't think the paper clip would do much. Should I do any of that said? 

Edited by NewbixCube
Link to comment
https://linustechtips.com/topic/435902-bsod/page/3/#findComment-5975114
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×