Help me lock down this error, getting blue screen on start up

Erock

Distinguished
Oct 12, 2008
2
0
18,510
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
 
You should post your system specs.

I doubt if this is a software issue. The fact that it will start after several tries would seem to indicate that something isn't functioning well until it warms up.

You could try updating chipset drivers and possibly BIOS.

I would certainly back up anything important on the drive right away, then check for errors there.
 

Erock

Distinguished
Oct 12, 2008
2
0
18,510
Done memtest, no problems there. When I meant that it starts up is that it gets all the way to windows and opens a few of the start up programs and then it goes to the blue screen and shuts down, so it seems like something that is loaded after windows starts. You guys can't tell from the memory dump? I thought you guys would.

Erock
 

dokk2

Distinguished
Jul 1, 2007
1,450
0
19,310
HMMMMMM try this :: go to control panel,system,device manager,hardware,and under hardware tell the system to update the hdd driver,,,,if that does not work you can try two more actions,reinstall right over existing install [not likely eh what???] or format and do a clean install,,it looks like your classpnp.sys driver is snookered,which seems to be like it says the classpnp driver, in other words the pnp driver sys for a whole class of hardware is snookered,if your hdd is partitioned then you just have to reinstall on the "C" partition,,dosen't windoze have a repair option wherein you can repair an existing install,if you can google for it could be the easiest way to go otherwise you might be looking at a complete reinstall,,anyhow that's what i see..:) ??? anybody else,,,,,,,,,,,,,,,,??
 

Zorg

Splendid
May 31, 2004
6,732
0
25,790
A quick Google search yielded this. It's a start anyway.

BSOD - disk.sys