Sure, I've uploaded new dump on my Gdrive now.
Last edited:
[SOLVED] Help | Random BSODs. FIX: CLEAN INSTALLATION; later, SET RAM voltages/frequencies like advised by the manufacturer.
- Thread starter xman323
- Start date
- May 7, 2013
- 10,400
Rich (BB code):
REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
Arg2: ffffcc8ff2292960, Object whose reference count is being lowered
Arg3: 0000000000000001, Reserved
Arg4: ffffcc8f00000128, ReservedI think those bugcheck parameters are messed up because the second parameter actually points to the Flags field of an I/O packet (IRP). I've managed to find the address of the packet. Looks some network-related stuff was going on at the time of the crash which makes sense since a torrent program was running.
Rich (BB code):
4: kd> !irp ffffcc8ff2292940+0x10 1
Irp is active with 4 stacks 6 is current (= 0xffffcc8ff32b9ab0)
No Mdl: System buffer=ffffcc8ff1b23f00: Thread ffffcc8ff350d080: Irp is completed. Pending has been returned
Flags = 00060040
ThreadListEntry.Flink = ffffcc8ff2292970
ThreadListEntry.Blink = ffffcc8ff2292970
IoStatus.Status = 00000102
IoStatus.Information = 000001f0
RequestorMode = 00000001
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 57cc3ff0e8
UserEvent = ffffcc8ff0c9fe60
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000
UserBuffer = 24997dc8040
&Tail.Overlay.DeviceQueueEntry = ffffcc8ff22929c8
Tail.Overlay.Thread = ffffcc8ff350d080
Tail.Overlay.AuxiliaryBuffer = fffff8061a68dd70
Tail.Overlay.ListEntry.Flink = 00000000
Tail.Overlay.ListEntry.Blink = 00000000
Tail.Overlay.CurrentStackLocation = ffffcc8ff32b9ab0
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = f0581712
Tail.CompletionKey = ffffcc8ff0581712
cmd flg cl Device File Completion-Context
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[IRP_MJ_DEVICE_CONTROL(e), N/A(0)]
0 0 ffffcc8fe05aaa80 00000000 00000000-00000000
\Driver\AFD
Args: 00000000 00000000 0x0 00000000The Flags of the above IRP which is what the second parameter is pointing to, I'm not sure why, something really has gone wrong here!
Rich (BB code):
4: kd> dd ffffcc8f`f2292960 L1
ffffcc8f`f2292960 00060040So, it would seem that the object which was meant to be dereferenced was the event object associated to the IRP. It makes the most sense.
Rich (BB code):
4: kd> knL
# Child-SP RetAddr Call Site
00 fffff38a`f5d25638 fffff806`1a21762e nt!KeBugCheckEx
01 fffff38a`f5d25640 fffff806`1a00827e nt!ObfDereferenceObjectWithTag+0x20f39e << Crash here, can't dereference some random I/O field
02 fffff38a`f5d25680 fffff806`1a08694e nt!HalPutDmaAdapter+0xe
03 fffff38a`f5d256b0 fffff806`1a00ec90 nt!IopCompleteRequest+0xace << I/O request takes too long and times out
04 fffff38a`f5d25770 fffff806`1a00cb27 nt!KiDeliverApc+0x1b0
05 fffff38a`f5d25820 fffff806`1a00bd2f nt!KiSwapThread+0x827
06 fffff38a`f5d258d0 fffff806`1a00b5d3 nt!KiCommitThreadWait+0x14f << Wait on IRP to complete
07 fffff38a`f5d25970 fffff806`1a3f7b51 nt!KeWaitForSingleObject+0x233
08 fffff38a`f5d25a60 fffff806`1a3f7bfa nt!ObWaitForSingleObject+0x91
09 fffff38a`f5d25ac0 fffff806`1a208cb8 nt!NtWaitForSingleObject+0x6a << Waiting on Event object
0a fffff38a`f5d25b00 00007ffe`c1e6cdf4 nt!KiSystemServiceCopyEnd+0x28
0b 00000057`cc3fef48 00000000`00000000 0x00007ffe`c1e6cdf4
Rich (BB code):
07 fffff38af5d25970 fffff8061a3f7b51 nt!KeWaitForSingleObject+233
Parameter[0] = ffffcc8ff0c9fe60
Parameter[1] = 0000000000000006
Parameter[2] = 0000000000000001
Parameter[3] = 0000000000000001
Rich (BB code):
4: kd> dt _IRP -y UserEvent ffffcc8ff2292950
nt!_IRP
+0x050 UserEvent : 0xffffcc8f`f0c9fe60 _KEVENTI'm not sure what exactly caused the problem to lead to the crash, but at the moment, I would suggest ensuring that you have all latest Windows Updates.
Thanks my friend, already had latest updates.
I've run memtest86 for 4 passes yesterday, test took nearly 8-9 hours to complete, no errors were detected and passed test successfully, reinstalled my OS from scratch, before logging on windows (on final installation step) I had repeated BSODs with various errors, done some searching and found out that the MB runs ram on 1.2v and it should be 1.35 as recommended by manufacturer, done that and manually set frequency to 3000mhz, booted again to windows installed all drivers from Mobos website, not a single BSOD since then, I'll keep monitoring and don't know whether it's allowed to post again after testing in the same thread or not, but I'll be leaving this feedback here in case someone faces the same issue as me.
many thanks for both of you for being supportive, I really can't thank you enough. @zbook @x BlueRobot
- May 7, 2013
- 10,400
Thanks for the update, glad you managed to get the issue resolved in the end. Hopefully you'll continue to be problem free.
Has Sysnative Forums helped you? Please consider donating to help us support the site!