Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Random BSOD (W/ MiniDumps)
New Posts  All Forums:Forum Nav:

Random BSOD (W/ MiniDumps)

post #1 of 3
Thread Starter 
3 random BSOD. all I really saw was NTFS.sys.
Not that great with BSOD ><<br /> A field I should really learn more of.

+rep for help

MiniDump.zip 79k .zip file
Mishra
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7 6700K ASUS Maximus Hero VIII ASUS GTX 1070 Strix  Corsair Vengeance 8GB 2x4GB 3000Mhz 
Hard DriveCoolingOSMonitor
Kingston HyperX Savage 240GB Corsair H100 Windows 7 Ultimate 2x Acer S230hldrbd 23' LED 
KeyboardPowerCaseMouse
KB Paradise V60 CoolerMaster Slient Pro 850w Phanteks Enthoo Pro M Acrylic Window Edition Steelseries Rival Fade 
  hide details  
Reply
Mishra
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7 6700K ASUS Maximus Hero VIII ASUS GTX 1070 Strix  Corsair Vengeance 8GB 2x4GB 3000Mhz 
Hard DriveCoolingOSMonitor
Kingston HyperX Savage 240GB Corsair H100 Windows 7 Ultimate 2x Acer S230hldrbd 23' LED 
KeyboardPowerCaseMouse
KB Paradise V60 CoolerMaster Slient Pro 850w Phanteks Enthoo Pro M Acrylic Window Edition Steelseries Rival Fade 
  hide details  
Reply
post #2 of 3
Three dumps, two point to core Windows files that are MORE THAN LIKELY not the origin cause of the crash, and the third points to memory_corruption (mem corruption can link to drivers, unstable overclock, bad memory, etc).

Before we begin, please reset your overclock to stock. I know a lot of people get a little defensive when it comes to their overclock not being a possible culprit as they "know" it's stable, etc, but please realize that an unstable overclock can & will cause a boatload of issue if it IS unstable. If we set all overclocks to stock and your issue still continues, then you know it wasn't your overclock. Do note that you're more than welcome to overclock as you were before after we diagnose your cause smile.gif

Now, after resetting clocks back to default values, two things I'd like for you to do, memtest being one of them considering mem corruption:
Quote:
Memtest:

Read the following to test your memory for errors. I would recommend no less than 5-6 passes as I have seen memory fail on the sixth pass before.

Driver Verifier:

Read the following
to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.

Before enabling Driver Verifier, my recommendation is to set a backup / restore point as in severe cases Driver Verifier can break your Windows. If you have difficulty getting into Windows, boot into Safe Mode and disable Driver Verifier there.

Drivers list looks good, nothing out of date or in serious need of update.

So, here's what we'll do as a final list:

1. Reset overclocks back to stock and see how the system runs. Agin, you're more than welcome to re-overclock once we're finished.

2. If resetting overclocks didn't help, memtest is next. KEEP SYSTEM AT STOCK UNTIL WE SOLVED ISSUES!.

3. If memtest came back clean after at least 6 passes, Driver Verifier is next. Driver Verifier will specifically stress all non-Microsoft third party drivers, and if it finds a faulting driver, will crash and generate a detailed dump file.

4. We also spoke on Steam about SATA ports, so stay on 2GBs for now and see if that helps as well since Marvel's port produced BSODs.

Dumps for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\032812-19546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03059000 PsLoadedModuleList = 0xfffff800`0329d650
Debug session time: Wed Mar 28 22:15:41.875 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:16.984
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffff8a001fff5b0, fffff8a001fff620, 5070103}

GetPointerFromAddress: unable to read from fffff80003307100
Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+dc )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8a001fff5b0, The pool entry we were looking for within the page.
Arg3: fffff8a001fff620, The next pool entry.
Arg4: 0000000005070103, (reserved)

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


BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  fffff8a001fff5b0 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003202cae to fffff800030d5d40

STACK_TEXT:  
fffff880`03562b08 fffff800`03202cae : 00000000`00000019 00000000`00000020 fffff8a0`01fff5b0 fffff8a0`01fff620 : nt!KeBugCheckEx
fffff880`03562b10 fffff800`033ba2ac : 00000000`00000000 fffff8a0`02b3aa00 fffff8a0`624e4d43 00000000`00d160a3 : nt!ExDeferredFreePool+0x12da
fffff880`03562bc0 fffff800`033ba340 : fffff8a0`0191cde8 00000000`d9071bcf fffff8a0`00757010 ffffffff`ffffffff : nt!CmpDereferenceNameControlBlockWithLock+0xdc
fffff880`03562bf0 fffff800`0339a39f : fffff8a0`0191cde8 fffff800`033b88c0 fffff800`624e4d43 fffffa80`00000000 : nt!CmpCleanUpKcbCacheWithLock+0x34
fffff880`03562c20 fffff800`033b8ab1 : fffff8a0`0191cde8 00000000`0719c97b fffff8a0`00757010 00000000`00000000 : nt!CmpDereferenceKeyControlBlockWithLock+0x13f
fffff880`03562c50 fffff800`030df471 : fffff800`032752b8 fffffa80`09dda680 00000000`00000000 00000000`00000657 : nt!CmpDelayDerefKCBWorker+0x1f1
fffff880`03562cb0 fffff800`0336ff7a : 00000000`00000000 fffffa80`09dda680 00000000`00000080 fffffa80`09d61740 : nt!ExpWorkerThread+0x111
fffff880`03562d40 fffff800`030c69c6 : fffff880`03386180 fffffa80`09dda680 fffff880`033910c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03562d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!CmpDereferenceNameControlBlockWithLock+dc
fffff800`033ba2ac 488b15ddb5f1ff  mov     rdx,qword ptr [nt!CmpNameCacheTable (fffff800`032d5890)]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!CmpDereferenceNameControlBlockWithLock+dc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0x19_20_nt!CmpDereferenceNameControlBlockWithLock+dc

BUCKET_ID:  X64_0x19_20_nt!CmpDereferenceNameControlBlockWithLock+dc

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


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\032812-11154-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0305e000 PsLoadedModuleList = 0xfffff800`032a2650
Debug session time: Wed Mar 28 21:49:40.778 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:19.887
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8800966b588, 0, fffff880016c8ebb, 2}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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 it
is pointing at freed memory.
Arguments:
Arg1: fffff8800966b588, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880016c8ebb, If non-zero, the instruction address which referenced the bad memory
        address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330c100
 fffff8800966b588 

FAULTING_IP: 
ndis!ndisNsiEnumerateAllInterfaceInformation+48c
fffff880`016c8ebb 4c8bbc24a8000004 mov     r15,qword ptr [rsp+40000A8h]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800566b350 -- (.trap 0xfffff8800566b350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000105 rbx=0000000000000000 rcx=fffff88001728ec0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880016c8ebb rsp=fffff8800566b4e0 rbp=fffffa800ca1a230
 r8=0000000000000000  r9=0000000000000000 r10=fffff8a00109a8f0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
ndis!ndisNsiEnumerateAllInterfaceInformation+0x48c:
fffff880`016c8ebb 4c8bbc24a8000004 mov     r15,qword ptr [rsp+40000A8h] ss:0018:fffff880`0966b588=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003085c50 to fffff800030dad40

STACK_TEXT:  
fffff880`0566b1e8 fffff800`03085c50 : 00000000`00000050 fffff880`0966b588 00000000`00000000 fffff880`0566b350 : nt!KeBugCheckEx
fffff880`0566b1f0 fffff800`030d8e6e : 00000000`00000000 fffff880`0966b588 00000000`00020000 fffff880`01726a50 : nt! ?? ::FNODOBFM::`string'+0x43d76
fffff880`0566b350 fffff880`016c8ebb : fffff880`01725110 00000000`00000000 fffffa80`0b1f9a40 fffff880`01726a50 : nt!KiPageFault+0x16e
fffff880`0566b4e0 fffff880`01603aab : 00000000`00000000 fffffa80`0ca1a230 00000000`00000000 00000000`00000000 : ndis!ndisNsiEnumerateAllInterfaceInformation+0x48c
fffff880`0566b5d0 fffff880`042c1e29 : fffffa80`0ca1a230 fffff8a0`00000070 fffffa80`0c921590 00000000`0182f780 : NETIO!NsiEnumerateObjectsAllParametersEx+0x24f
fffff880`0566b7b0 fffff880`042c38e8 : fffffa80`0c921590 fffffa80`0c9214c0 fffff8a0`04a0fc00 fffffa80`0c9214f8 : nsiproxy!NsippEnumerateObjectsAllParameters+0x305
fffff880`0566b9a0 fffff880`042c39db : fffffa80`0b929060 00000000`00000000 00000000`00000001 00000000`00000003 : nsiproxy!NsippDispatchDeviceControl+0x70
fffff880`0566b9e0 fffff800`033f47e7 : fffffa80`0d5c14a0 fffffa80`0d5c14a0 fffffa80`0c9215d8 fffffa80`0c9214c0 : nsiproxy!NsippDispatch+0x4b
fffff880`0566ba10 fffff800`033f5046 : 00000000`0182f600 00000000`00000688 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`0566bb40 fffff800`030d9fd3 : fffffa80`0d5c5320 00000000`0182f5e8 fffff880`0566bbc8 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
fffff880`0566bbb0 00000000`7763138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0182f678 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7763138a


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !ndis
    fffff880016c8ec2 - ndis!ndisNsiEnumerateAllInterfaceInformation+493
        [ 00:04 ]
1 error : !ndis (fffff880016c8ec2)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\032812-10077-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03051000 PsLoadedModuleList = 0xfffff800`03295650
Debug session time: Wed Mar 28 21:52:01.894 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:20.003
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 34, {50853, fffff8800354d738, fffff8800354cf90, fffff8000310fdda}

Probably caused by : ntkrnlmp.exe ( nt!CcAcquireByteRangeForWrite+5c0 )

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

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

CACHE_MANAGER (34)
    See the comment for FAT_FILE_SYSTEM (0x23)
Arguments:
Arg1: 0000000000050853
Arg2: fffff8800354d738
Arg3: fffff8800354cf90
Arg4: fffff8000310fdda

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


EXCEPTION_RECORD:  fffff8800354d738 -- (.exr 0xfffff8800354d738)
ExceptionAddress: fffff8000310fdda (nt!CcAcquireByteRangeForWrite+0x00000000000005c0)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800354cf90 -- (.cxr 0xfffff8800354cf90)
rax=0001c6a000000000 rbx=0000000000000000 rcx=fffffa800b86cb90
rdx=00000000000002fd rsi=fffffa800b86cb80 rdi=000000000b86cb80
rip=fffff8000310fdda rsp=fffff8800354d970 rbp=fffff8800354dc58
 r8=fffff8800354daa8  r9=fffffa800b86cb80 r10=fffffa800b86cc90
r11=fffffa800b86cb80 r12=fffff8800354db68 r13=0000000000000000
r14=fffffa800b86cb80 r15=0001c69ffffffff0
iopl=0         nv up ei pl nz na pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010203
nt!CcAcquireByteRangeForWrite+0x5c0:
fffff800`0310fdda 66413917        cmp     word ptr [r15],dx ds:002b:0001c69f`fffffff0=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032ff100
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!CcAcquireByteRangeForWrite+5c0
fffff800`0310fdda 66413917        cmp     word ptr [r15],dx

FAULTING_IP: 
nt!CcAcquireByteRangeForWrite+5c0
fffff800`0310fdda 66413917        cmp     word ptr [r15],dx

BUGCHECK_STR:  0x34

LAST_CONTROL_TRANSFER:  from fffff8000310e7a2 to fffff8000310fdda

STACK_TEXT:  
fffff880`0354d970 fffff800`0310e7a2 : fffffa80`0b86cb80 fffff880`0354dc58 00000000`00000000 fffff880`0354daa8 : nt!CcAcquireByteRangeForWrite+0x5c0
fffff880`0354da50 fffff800`031123d6 : fffffa80`0b42fb48 00000000`00000001 fffffa80`00000001 fffffa80`00000000 : nt!CcFlushCache+0x2c2
fffff880`0354db50 fffff800`03112d98 : fffff880`00000000 fffff880`0354dc58 fffffa80`0e0811e0 fffff880`04196734 : nt!CcWriteBehind+0x1c6
fffff880`0354dc00 fffff800`030d7471 : fffffa80`09dd64f0 fffff800`033c3701 fffff800`032ce8a0 fffffa80`00000002 : nt!CcWorkerThread+0x1c8
fffff880`0354dcb0 fffff800`03367f7a : 00000000`00000000 fffffa80`09d82b60 00000000`00000080 fffffa80`09d64740 : nt!ExpWorkerThread+0x111
fffff880`0354dd40 fffff800`030be9c6 : fffff880`03386180 fffffa80`09d82b60 fffff880`033910c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0354dd80 00000000`00000000 : fffff880`0354e000 fffff880`03548000 fffff880`0354cd40 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!CcAcquireByteRangeForWrite+5c0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

STACK_COMMAND:  .cxr 0xfffff8800354cf90 ; kb

FAILURE_BUCKET_ID:  X64_0x34_nt!CcAcquireByteRangeForWrite+5c0

BUCKET_ID:  X64_0x34_nt!CcAcquireByteRangeForWrite+5c0

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




Edited by pjBSOD - 3/28/12 at 12:47am
post #3 of 3
Thread Starter 
Repped, Also I have not BSOD since I changed the sata port my Crucial M4 is plugged into.
The 3 said BSOD were instant when I booted into windows.
So I changed from the Marvel 3Gb/s(Which I now know NEVER to use)
Too the Intel 2Gb/s.

I will update if more BSOD occur smile.gif
Mishra
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7 6700K ASUS Maximus Hero VIII ASUS GTX 1070 Strix  Corsair Vengeance 8GB 2x4GB 3000Mhz 
Hard DriveCoolingOSMonitor
Kingston HyperX Savage 240GB Corsair H100 Windows 7 Ultimate 2x Acer S230hldrbd 23' LED 
KeyboardPowerCaseMouse
KB Paradise V60 CoolerMaster Slient Pro 850w Phanteks Enthoo Pro M Acrylic Window Edition Steelseries Rival Fade 
  hide details  
Reply
Mishra
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7 6700K ASUS Maximus Hero VIII ASUS GTX 1070 Strix  Corsair Vengeance 8GB 2x4GB 3000Mhz 
Hard DriveCoolingOSMonitor
Kingston HyperX Savage 240GB Corsair H100 Windows 7 Ultimate 2x Acer S230hldrbd 23' LED 
KeyboardPowerCaseMouse
KB Paradise V60 CoolerMaster Slient Pro 850w Phanteks Enthoo Pro M Acrylic Window Edition Steelseries Rival Fade 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Random BSOD (W/ MiniDumps)