BSOD Problems - Techist - Tech Forum

Go Back   Techist - Tech Forum > Computer Hardware > Hardware Repairs and Troubleshooting
Click Here to Login
Reply
 
Thread Tools Display Modes
 
Old 12-18-2015, 04:54 PM   #1 (permalink)
Newb Techie
 
Join Date: Dec 2009
Posts: 25
Default BSOD Problems

So I built a new comp recently at first everything was fine then all hell broke loose. Below is a link to my dump files and notes. I just started this so there is a small sample size compared to the length of the actual problem.

Things Ive done after fresh install of windows.
Memtest 9 passes 0 errors
sfc /scannow 0 erros
windows mem test 0 errors
update network driver from intel site
nvidia driver from nvidia
all other drivers are from mother board disk.

Error is most common shortly after start up while either doing nothing or browsing internet. I have not crashed at all during gaming which is about 2 hours a night.

My Build:
ASROCK z170 extreme 4
I5 skylake 6600
EVGA GeForce GTX 980
EVGA 220-G2-0650-Y1 80 PLUS GOLD 650W ECO
CORSAIR Vengeance LPX 16GB (2 x 8GB) 288-Pin DDR4 2400
SAMSUNG 850 EVO 500GB
Windows 10 64b Home
https://onedrive.live.com/redir?resi...hint=folder%2c

Errors I have gotten include
Memory_Management (most common)
irql_not_less_or_equal (runnerUP)
bad_pool_header
**another that I cant remember at the moment will update later

Backstory:
So I built it got everything running installed drivers from disks updated drivers from nvidia. Downloaded some bf4. Everything ran great for a few days. Picked up Rainbow six siege and I had a copy of assassin creed from asrock somewhere in the redemption process I got the app from asrock that checks your system from updates and ran that. Friend also got R6S he ran into problems with the game so we spent the night troubleshooting. Next day I get home from work boot up my computer and this is where the BSOD begin. Pretty frequent so I started trying to figure it out changing drivers etc. I noticed that windows updates were failing to install so I tried multiple times to get one to install finally it did and then windows wouldnt boot anymore, couldnt even get in to safemode. I rolled it back and back to normal bsod I was getting but at least able to load windows
At this point I say **** it and just wipe it and do a fresh install of windows.
Slowly updated drivers this time, didnt get the asrock app as I thought it might of been a driver from that. Everything ran fine for a day or 2 but now its happening again. started running tests, and recording dump files.
__________________

valakas is offline   Reply With Quote
Old 12-18-2015, 05:07 PM   #2 (permalink)
Build Guru
 
PP Mguire's Avatar
 
Join Date: Dec 2004
Location: Fort Worth, Texas
Posts: 28,279
Default Re: BSOD Problems

When you did a clean install did you use disk drivers or directly off the site? Never use CD drivers.
__________________

__________________
"Resolution is just a number." #Ubisoft
Origin/Steam = PP_Mguire Twitch = pp_mguire Instagram = ppmguire PSN = PP_Mguire

Access to my Plex PM me.
PP Mguire is offline   Reply With Quote
Old 12-18-2015, 05:09 PM   #3 (permalink)
Newb Techie
 
Join Date: Dec 2009
Posts: 25
Default Re: BSOD Problems

disk drives that came with the motherboard
valakas is offline   Reply With Quote
Old 12-18-2015, 05:16 PM   #4 (permalink)
Private Joker
 
carnageX's Avatar
 
Join Date: Feb 2007
Location: South Dakota
Posts: 24,506
Default Re: BSOD Problems

Install the updated drivers from the motherboard manufacturer's website.
__________________
Laptop: MSI GT70 2OC-059us | i7-4700MQ | 16GB | GTX 770m | 500GB SSD / 750GB HDD | 17.3" | Win10 Pro
Desktop: 4690k | 12GB g.Skill RipJaws | GTX 970 | 520hx | Z87X-UD4H | Corsair Vengeance C70 | Corsair H110 | Acer 25" | Acer 22" | Win10
Mobile: Samsung Galaxy Note 5


If I help you, or you just like what I said, rep me by clicking the under my post
carnageX is offline   Reply With Quote
Old 12-18-2015, 05:32 PM   #5 (permalink)
Newb Techie
 
Join Date: Dec 2009
Posts: 25
Default Re: BSOD Problems

Ok installed the ones that were not the latest drivers for:
ME driver
INF driver
Rapid storage tech driver
Audio driver.
Hopefully that fixes it, will update if I get more BSOD. Thanks.
valakas is offline   Reply With Quote
Old 12-18-2015, 05:43 PM   #6 (permalink)
Private Joker
 
carnageX's Avatar
 
Join Date: Feb 2007
Location: South Dakota
Posts: 24,506
Default Re: BSOD Problems

If you get more BSOD's, please zip & upload the dump files from C:\Windows\Minidump and we can analyze them for you to see what's causing them.
__________________
Laptop: MSI GT70 2OC-059us | i7-4700MQ | 16GB | GTX 770m | 500GB SSD / 750GB HDD | 17.3" | Win10 Pro
Desktop: 4690k | 12GB g.Skill RipJaws | GTX 970 | 520hx | Z87X-UD4H | Corsair Vengeance C70 | Corsair H110 | Acer 25" | Acer 22" | Win10
Mobile: Samsung Galaxy Note 5


If I help you, or you just like what I said, rep me by clicking the under my post
carnageX is offline   Reply With Quote
Old 12-19-2015, 11:03 AM   #7 (permalink)
Newb Techie
 
Join Date: Dec 2009
Posts: 25
Default Re: BSOD Problems

Went out to xmas party got home started up shortly after BSOD went to bed woke up started up shortly after BSOD different this time tho. KSTOP something minidumps here for the 2 BSOD
https://onedrive.live.com/redir?resi...int=file%2czip
edit forgot to zip added zip

Had another this time page fault in non paged area
valakas is offline   Reply With Quote
Old 12-19-2015, 02:46 PM   #8 (permalink)
Private Joker
 
carnageX's Avatar
 
Join Date: Feb 2007
Location: South Dakota
Posts: 24,506
Default Re: BSOD Problems

Just for your reference...i'll post your dump files.

First dump:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff803e44b8a00, 0, ffffffffffffffff}

Probably caused by : memory_corruption ( nt!MiObtainReferencedVad+370 )

Followup:     MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff803e44b8a00, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10586.17.amd64fre.th2_release.151121-2308

SYSTEM_PRODUCT_NAME:  To Be Filled By O.E.M.

SYSTEM_SKU:  To Be Filled By O.E.M.

SYSTEM_VERSION:  To Be Filled By O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  P2.40

BIOS_DATE:  11/23/2015

BASEBOARD_MANUFACTURER:  ASRock

BASEBOARD_PRODUCT:  Z170 Extreme4

BASEBOARD_VERSION:                        

DUMP_TYPE:  2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff803e44b8a00

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: fffff803e47fe520: Unable to get MiVisibleState
 ffffffffffffffff 

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP: 
nt!MiObtainReferencedVad+370
fffff803`e44b8a00 0fb64b21        movzx   ecx,byte ptr [rbx+21h]

EXCEPTION_PARAMETER2:  ffffffffffffffff

BUGCHECK_STR:  0x1E_c0000005_R

CPU_COUNT: 4

CPU_MHZ: cf0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: 49'00000000 (cache) 49'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  ShellExperienc

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  MAKO

ANALYSIS_SESSION_TIME:  12-19-2015 13:26:25.0766

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER:  from fffff803e45f36b0 to fffff803e45c2760

STACK_TEXT:  
ffffd000`25ab58f8 fffff803`e45f36b0 : 00000000`0000001e ffffffff`c0000005 fffff803`e44b8a00 00000000`00000000 : nt!KeBugCheckEx
ffffd000`25ab5900 fffff803`e45cd3c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x225b0
ffffd000`25ab5fe0 fffff803`e45cb87d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
ffffd000`25ab61c0 fffff803`e44b8a00 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0xfd
ffffd000`25ab6350 fffff803`e4850a64 : 00000000`00000000 ffffd000`25ab6440 00000026`00000000 00007ffe`b6f40000 : nt!MiObtainReferencedVad+0x370
ffffd000`25ab63d0 fffff803`e48507f0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiAllocateVirtualMemory+0x264
ffffd000`25ab65a0 fffff803`e45ccfa3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtAllocateVirtualMemory+0x40
ffffd000`25ab6600 fffff803`e45c5650 : fffff803`e48fa2ac 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
ffffd000`25ab6808 fffff803`e48fa2ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
ffffd000`25ab6810 fffff803`e44b90ed : 00000000`80000001 00000026`5b0feff8 00000000`00003000 00000026`5b0fb000 : nt!MiCheckForUserStackOverflow+0x128
ffffd000`25ab6890 fffff803`e45cb9bc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x59d
ffffd000`25ab6a00 00007ffe`b6f66ebf : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c
00000026`5b0ff000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`b6f66ebf


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  d1605126bd793849d98daedb78343a2dd7d206e3

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  0aa426a5630ef27561bb31b165520bea05b7beb0

THREAD_SHA1_HASH_MOD:  dc844b1b94baa204d070855e43bbbd27eee98b94

FOLLOWUP_IP: 
nt!MiObtainReferencedVad+370
fffff803`e44b8a00 0fb64b21        movzx   ecx,byte ptr [rbx+21h]

FAULT_INSTR_CODE:  214bb60f

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiObtainReferencedVad+370

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  565189c8

IMAGE_VERSION:  10.0.10586.17

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  370

FAILURE_BUCKET_ID:  0x1E_c0000005_R_nt!MiObtainReferencedVad

BUCKET_ID:  0x1E_c0000005_R_nt!MiObtainReferencedVad

PRIMARY_PROBLEM_CLASS:  0x1E_c0000005_R_nt!MiObtainReferencedVad

TARGET_TIME:  2015-12-19T04:19:38.000Z

OSBUILD:  10586

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-11-22 03:24:24

BUILDDATESTAMP_STR:  151121-2308

BUILDLAB_STR:  th2_release

BUILDOSVER_STR:  10.0.10586.17.amd64fre.th2_release.151121-2308

ANALYSIS_SESSION_ELAPSED_TIME: 385

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1e_c0000005_r_nt!miobtainreferencedvad

FAILURE_ID_HASH:  {4e9171a1-097a-073a-7332-30a74092f767}

Followup:     MachineOwner
---------
Second dump:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffc800dd036990, 0, fffff8004a6b8840, 2}


Could not read faulting driver name
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a0 )

Followup:     Pool_corruption
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffc800dd036990, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8004a6b8840, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10586.17.amd64fre.th2_release.151121-2308

SYSTEM_PRODUCT_NAME:  To Be Filled By O.E.M.

SYSTEM_SKU:  To Be Filled By O.E.M.

SYSTEM_VERSION:  To Be Filled By O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  P2.40

BIOS_DATE:  11/23/2015

BASEBOARD_MANUFACTURER:  ASRock

BASEBOARD_PRODUCT:  Z170 Extreme4

BASEBOARD_VERSION:                        

DUMP_TYPE:  2

BUGCHECK_P1: ffffc800dd036990

BUGCHECK_P2: 0

BUGCHECK_P3: fffff8004a6b8840

BUGCHECK_P4: 2

READ_ADDRESS: fffff8004a805520: Unable to get MiVisibleState
 ffffc800dd036990 

FAULTING_IP: 
nt!ExDeferredFreePool+a0
fffff800`4a6b8840 488b10          mov     rdx,qword ptr [rax]

MM_INTERNAL_CODE:  2

CPU_COUNT: 4

CPU_MHZ: cf0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: 49'00000000 (cache) 49'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  cleanmgr.exe

CURRENT_IRQL:  1

ANALYSIS_SESSION_HOST:  MAKO

ANALYSIS_SESSION_TIME:  12-19-2015 13:31:40.0306

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

DEVICE_OBJECT: 00000000000005e4

TRAP_FRAME:  ffffd00022d58be0 -- (.trap 0xffffd00022d58be0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffc800dd036990 rbx=0000000000000000 rcx=ffffe00150c3dc30
rdx=ffffc800dd036990 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8004a6b8840 rsp=ffffd00022d58d70 rbp=0000000000000000
 r8=ffffc000dd03c010  r9=ffffe00150c3d520 r10=ffffe00150c3d520
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!ExDeferredFreePool+0xa0:
fffff800`4a6b8840 488b10          mov     rdx,qword ptr [rax] ds:ffffc800`dd036990=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8004a5e9285 to fffff8004a5c9760

STACK_TEXT:  
ffffd000`22d58978 fffff800`4a5e9285 : 00000000`00000050 ffffc800`dd036990 00000000`00000000 ffffd000`22d58be0 : nt!KeBugCheckEx
ffffd000`22d58980 fffff800`4a4c017c : 00000000`00000000 00000000`00000003 ffffd000`22d58be0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x11185
ffffd000`22d58a70 fffff800`4a5d29bc : ffffe001`5964d080 00000000`00000003 00000000`000dd058 00000000`0000009a : nt!MmAccessFault+0x62c
ffffd000`22d58be0 fffff800`4a6b8840 : ffffc000`dd040770 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c
ffffd000`22d58d70 fffff800`4a6b776d : ffffc000`dd047770 ffffc000`dd040770 00000000`00000000 00000000`00000001 : nt!ExDeferredFreePool+0xa0
ffffd000`22d58df0 fffff800`2a01de87 : ffffe001`58f30670 00000000`00001000 ffffc000`dcff0c92 fffff800`6346744e : nt!ExFreePoolWithTag+0x76d
ffffd000`22d58ed0 fffff800`2a01d32c : 00000000`00000002 00000000`00000000 00020000`0001c983 00000000`0000000b : NTFS!NtfsBuildCorruptionCtx_CallStack+0x3ef
ffffd000`22d58fb0 fffff800`29ff9a72 : ffffe001`58f30528 ffffc000`dd030002 0000015f`0014110a fffff800`00000000 : NTFS!NtfsAttachCorruption_IndexSubtree+0x1b8
ffffd000`22d59050 fffff800`29f60fc8 : ffffe001`58f30528 ffffc000`d9278e90 ffffc000`cf695a70 ffffc000`00000000 : NTFS! ?? ::NNGAKEGL::`string'+0x1dfc2
ffffd000`22d59100 fffff800`29f609f7 : ffffe001`58f30528 ffffc000`00010000 ffffc000`dc003e40 ffffc000`dcbe7810 : NTFS!FindNextIndexEntry+0x328
ffffd000`22d591c0 fffff800`29f5ea5b : ffffe001`58f30528 ffffc000`dcbe7810 ffffc000`cfee1b40 00000000`00000001 : NTFS!NtfsContinueIndexEnumeration+0xc7
ffffd000`22d59270 fffff800`29f5dcf3 : 00000000`00000000 ffffe001`525fb9c0 ffffd000`22d597c0 00000000`00000000 : NTFS!NtfsQueryDirectory+0x60b
ffffd000`22d59660 fffff800`29f5dc09 : 00000000`00000000 ffffe001`596a5bd0 ffffe001`596a5b01 00000000`00000801 : NTFS!NtfsCommonDirectoryControl+0xa3
ffffd000`22d596a0 fffff800`28d57895 : ffffd000`22d597c0 ffffe001`596a5bd0 ffffe001`58f30528 ffffd000`22d596c8 : NTFS!NtfsFsdDirectoryControl+0xb9
ffffd000`22d59710 fffff800`28d55816 : ffffe001`52424e80 ffffd000`22d59a80 00000000`00000501 ffffe001`52434200 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x1a5
ffffd000`22d597a0 fffff800`4a889af6 : ffffe001`51831dd0 ffffd000`22d59881 00000000`00000001 ffffe001`51831d04 : FLTMGR!FltpDispatch+0xb6
ffffd000`22d59800 fffff800`4a88996f : 00000000`000005e4 00000000`00000000 00000000`00000000 00000073`c12eccc8 : nt!IopSynchronousServiceTail+0x176
ffffd000`22d598d0 fffff800`4a5d3fa3 : ffffc000`c954d790 fffff800`4a8c1bed 00000000`00000000 00000000`00000000 : nt!NtQueryDirectoryFile+0xcf
ffffd000`22d59990 00007ffc`1c4c5484 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000073`c12ecca8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`1c4c5484


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  3eebf363037384cf8e8f1b1506d4e6b03dad91b3

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  c128ac4ae9bf2b17d4710a122ce4c3d1e0c99469

THREAD_SHA1_HASH_MOD:  f0e9aaba51fbe3bf9b70ce80dbbcbb1f91977f00

FOLLOWUP_IP: 
nt!ExDeferredFreePool+a0
fffff800`4a6b8840 488b10          mov     rdx,qword ptr [rax]

FAULT_INSTR_CODE:  4c108b48

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!ExDeferredFreePool+a0

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.10586.17

MODULE_NAME: Pool_Corruption

BUCKET_ID_FUNC_OFFSET:  a0

FAILURE_BUCKET_ID:  AV_R_INVALID_nt!ExDeferredFreePool

BUCKET_ID:  AV_R_INVALID_nt!ExDeferredFreePool

PRIMARY_PROBLEM_CLASS:  AV_R_INVALID_nt!ExDeferredFreePool

TARGET_TIME:  2015-12-19T16:11:15.000Z

OSBUILD:  10586

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-11-22 03:24:24

BUILDDATESTAMP_STR:  151121-2308

BUILDLAB_STR:  th2_release

BUILDOSVER_STR:  10.0.10586.17.amd64fre.th2_release.151121-2308

ANALYSIS_SESSION_ELAPSED_TIME: 3a4

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_r_invalid_nt!exdeferredfreepool

FAILURE_ID_HASH:  {028c647e-835a-75c4-058d-04f80fc3ba93}

Followup:     Pool_corruption
Third dump:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff8010cad2b9a, 0, ffffffffffffffff}

Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+fa )

Followup:     MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8010cad2b9a, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10586.17.amd64fre.th2_release.151121-2308

SYSTEM_PRODUCT_NAME:  To Be Filled By O.E.M.

SYSTEM_SKU:  To Be Filled By O.E.M.

SYSTEM_VERSION:  To Be Filled By O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  P2.40

BIOS_DATE:  11/23/2015

BASEBOARD_MANUFACTURER:  ASRock

BASEBOARD_PRODUCT:  Z170 Extreme4

BASEBOARD_VERSION:                        

DUMP_TYPE:  2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8010cad2b9a

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: fffff80378792520: Unable to get MiVisibleState
 ffffffffffffffff 

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP: 
NETIO!RtlGetNextExpiredTimerWheelEntry+fa
fffff801`0cad2b9a 418b4010        mov     eax,dword ptr [r8+10h]

EXCEPTION_PARAMETER2:  ffffffffffffffff

BUGCHECK_STR:  0x1E_c0000005_R

CPU_COUNT: 4

CPU_MHZ: cf0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: 49'00000000 (cache) 49'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  MAKO

ANALYSIS_SESSION_TIME:  12-19-2015 13:36:57.0814

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

TRAP_FRAME:  ffffe00114ae0870 -- (.trap 0xffffe00114ae0870)
Unable to read trap frame at ffffe001`14ae0870

LAST_CONTROL_TRANSFER:  from fffff803785d42ce to fffff80378556760

STACK_TEXT:  
ffffd001`801e32f8 fffff803`785d42ce : 00000000`0000001e ffffffff`c0000005 fffff801`0cad2b9a 00000000`00000000 : nt!KeBugCheckEx
ffffd001`801e3300 fffff803`7855c80d : fffff803`78745000 fffff803`78414000 0004c830`007cc000 ffffe001`00000001 : nt!KiFatalExceptionHandler+0x22
ffffd001`801e3340 fffff803`7848df39 : 00000000`00000000 00000000`000000e9 ffffd001`801e3940 00000000`00000001 : nt!RtlpExecuteHandlerForException+0xd
ffffd001`801e3370 fffff803`7848c34c : ffffd001`801e4288 ffffd001`801e3fa0 ffffd001`801e4288 00000000`00000001 : nt!RtlDispatchException+0x429
ffffd001`801e3a70 fffff803`785613c2 : 00000000`00000000 ffffe001`14ae0870 ffffe001`14ae0870 fffff801`0cc85b43 : nt!KiDispatchException+0x144
ffffd001`801e4150 fffff803`7855f87d : ffffe001`1a2b1170 ffffffff`feced300 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
ffffd001`801e4330 fffff801`0cad2b9a : fffff801`0dcf7cc6 ffffe001`14950cc0 fffff803`78414000 fffff780`00000300 : nt!KiGeneralProtectionFault+0xfd
ffffd001`801e44c8 fffff801`0dcf7cc6 : ffffe001`14950cc0 fffff803`78414000 fffff780`00000300 fffff803`78be25ac : NETIO!RtlGetNextExpiredTimerWheelEntry+0xfa
ffffd001`801e44d0 fffff801`0dcf69ba : 00000061`660efc98 00000000`00315a4b 0000001f`8169caf7 ffffe001`1495fd00 : tcpip!TcpProcessExpiredTcbTimers+0x86
ffffd001`801e45c0 fffff803`7845ddf0 : ffffd001`7a37cf00 00000000`6f42fcca ffffd001`801e4a30 ffffe001`1495fda0 : tcpip!TcpPeriodicTimeoutHandler+0x39a
ffffd001`801e47c0 fffff803`7845d509 : 00000000`00000008 ffffe001`1495fae0 ffffd001`801e4a18 00000000`00000000 : nt!KiExecuteAllDpcs+0x270
ffffd001`801e4910 fffff803`7855951a : 00000000`00000000 ffffd001`7a37a180 ffffd001`7a386bc0 ffffe001`18ca1840 : nt!KiRetireDpcList+0xe9
ffffd001`801e4b60 00000000`00000000 : ffffd001`801e5000 ffffd001`801de000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  4434700246d0c8bdb2162d225b663ff737d97853

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5dfec92cf13d793e02205e8fc03e00806e402bbd

THREAD_SHA1_HASH_MOD:  3f7952046da93f8cea99c4d89e5b05fa6b80aafe

FOLLOWUP_IP: 
NETIO!RtlGetNextExpiredTimerWheelEntry+fa
fffff801`0cad2b9a 418b4010        mov     eax,dword ptr [r8+10h]

FAULT_INSTR_CODE:  10408b41

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  NETIO!RtlGetNextExpiredTimerWheelEntry+fa

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  5632d715

IMAGE_VERSION:  10.0.10586.0

BUCKET_ID_FUNC_OFFSET:  fa

FAILURE_BUCKET_ID:  0x1E_c0000005_R_NETIO!RtlGetNextExpiredTimerWheelEntry

BUCKET_ID:  0x1E_c0000005_R_NETIO!RtlGetNextExpiredTimerWheelEntry

PRIMARY_PROBLEM_CLASS:  0x1E_c0000005_R_NETIO!RtlGetNextExpiredTimerWheelEntry

TARGET_TIME:  2015-12-19T15:57:17.000Z

OSBUILD:  10586

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-11-22 03:24:24

BUILDDATESTAMP_STR:  151121-2308

BUILDLAB_STR:  th2_release

BUILDOSVER_STR:  10.0.10586.17.amd64fre.th2_release.151121-2308

ANALYSIS_SESSION_ELAPSED_TIME: 1596d

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1e_c0000005_r_netio!rtlgetnextexpiredtimerwheelentry

FAILURE_ID_HASH:  {cfebd0ed-af9f-f49e-6fae-731930002c7a}

Followup:     MachineOwner
---------
Looking at these, specifically how the first one crashed, and the 2nd one... says to me it could possibly be a memory issue. I suggest running Memtest86+ to see if you have possible faulty memory.

Download the ISO from here: Memtest86+ - Advanced Memory Diagnostic Tool
Burn it to a disc or create a bootable flash drive, and boot off of it. Let it run for a minimum of 4 hours (longer the better) - unless you start seeing red errors right away. If you see any errors at all during the test...then you'll need to shutdown your system, and remove all but 1 stick of memory, and re-run Memtest. You'll need to repeat this (testing 1 stick at a time) either until you find a faulting memory module, or you find a possible bad slot on your board.
__________________
Laptop: MSI GT70 2OC-059us | i7-4700MQ | 16GB | GTX 770m | 500GB SSD / 750GB HDD | 17.3" | Win10 Pro
Desktop: 4690k | 12GB g.Skill RipJaws | GTX 970 | 520hx | Z87X-UD4H | Corsair Vengeance C70 | Corsair H110 | Acer 25" | Acer 22" | Win10
Mobile: Samsung Galaxy Note 5


If I help you, or you just like what I said, rep me by clicking the under my post
carnageX is offline   Reply With Quote
Old 12-19-2015, 04:00 PM   #9 (permalink)
Newb Techie
 
Join Date: Dec 2009
Posts: 25
Default Re: BSOD Problems

Is there a difference between memtest86 and memtest+
MemTest86 - Download now!

I ran that for 16 hours and got no errors. If the + version is infact different/better I will run it tonight when I go to bed. Thanks again : )
__________________

valakas is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
BSOD DRIVER_IRQL_NOT_EQUAL, BSOD help please? happyh1ppo Hardware Repairs and Troubleshooting 1 01-05-2012 03:52 PM
xp bsod problems afplayboy18 Microsoft Windows and Software 20 08-18-2006 12:40 AM
Problems updating XP x64: BSOD Jonathan Bones Microsoft Windows and Software 1 06-15-2006 12:26 PM
Booting up after new hard drive installation problems. Also BSOD problem hinker Hardware Repairs and Troubleshooting 3 01-14-2006 01:35 AM
bsod problems b1ng Monitors, Printers and Peripherals 9 11-22-2004 03:32 PM



Copyright 2002- Social Knowledge, LLC All Rights Reserved.

All times are GMT -5. The time now is 05:50 AM.


Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.