Hey first post, I hope I put this in the right section of the forum, but anyway I get a blue screen error when I first boot up my computer, but if I reboot it a few times it will start like normal and as long as I don't turn it off, there are no issues. Instead of trying to describe it, I copied the minidump file so hopefully someone who knows more than me can help me interpret it:
Here is the main page:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffadf3b1d943a, 0, fffffadf29257290, 0}
Could not read faulting driver name
Unable to load image atapi.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atapi.sys
Unable to load image CLASSPNP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** WARNING: Unable to verify timestamp for disk.sys
Probably caused by : disk.sys ( disk!DiskFlushDispatch+62 )
Followup: MachineOwner
---------
Here is the !analyze -v page:
*******************************************************************************
* *
* 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: fffffadf3b1d943a, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffffadf29257290, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: fffffadf3b1d943a
FAULTING_IP:
disk!DiskFlushDispatch+62
fffffadf`29257290 488b040a mov rax,qword ptr [rdx+rcx]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
LAST_CONTROL_TRANSFER: from fffff800010a6072 to fffff8000102e890
STACK_TEXT:
STACK_COMMAND: kb
FOLLOWUP_IP:
disk!DiskFlushDispatch+62
fffffadf`29257290 488b040a mov rax,qword ptr [rdx+rcx]
SYMBOL_STACK_INDEX: 49
SYMBOL_NAME: disk!DiskFlushDispatch+62
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: disk
IMAGE_NAME: disk.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45d69708
FAILURE_BUCKET_ID: X64_0x50_disk!DiskFlushDispatch+62
BUCKET_ID: X64_0x50_disk!DiskFlushDispatch+62
Followup: MachineOwner
If you guys need the full stack text I could include that as well, but I think this info should be enough. Looks like a driver error but I'm not exactly sure what to reinstall.
Erock
Here is the main page:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffadf3b1d943a, 0, fffffadf29257290, 0}
Could not read faulting driver name
Unable to load image atapi.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atapi.sys
Unable to load image CLASSPNP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** WARNING: Unable to verify timestamp for disk.sys
Probably caused by : disk.sys ( disk!DiskFlushDispatch+62 )
Followup: MachineOwner
---------
Here is the !analyze -v page:
*******************************************************************************
* *
* 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: fffffadf3b1d943a, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffffadf29257290, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: fffffadf3b1d943a
FAULTING_IP:
disk!DiskFlushDispatch+62
fffffadf`29257290 488b040a mov rax,qword ptr [rdx+rcx]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
LAST_CONTROL_TRANSFER: from fffff800010a6072 to fffff8000102e890
STACK_TEXT:
STACK_COMMAND: kb
FOLLOWUP_IP:
disk!DiskFlushDispatch+62
fffffadf`29257290 488b040a mov rax,qword ptr [rdx+rcx]
SYMBOL_STACK_INDEX: 49
SYMBOL_NAME: disk!DiskFlushDispatch+62
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: disk
IMAGE_NAME: disk.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45d69708
FAILURE_BUCKET_ID: X64_0x50_disk!DiskFlushDispatch+62
BUCKET_ID: X64_0x50_disk!DiskFlushDispatch+62
Followup: MachineOwner
If you guys need the full stack text I could include that as well, but I think this info should be enough. Looks like a driver error but I'm not exactly sure what to reinstall.
Erock