New
#31
That's what we're here for. We'll help as much as possible, but you are the one who has to do the work. Just hang in there.
That's what we're here for. We'll help as much as possible, but you are the one who has to do the work. Just hang in there.
Almost all the calls within the the call stack are reserved for the use of Microsoft only, so they're not documented with the WDK (Windows Driver Kit) docs, which is really irritating.
I'm also guessing that the SiCheckForUfdWinpeBoot function, is a way of system is checking for a Windows PE (Preinstallation Environment) on a UFD (or bootable USB Flash Drive).Code:0: kd> k # Child-SP RetAddr Call Site 00 fffff880`086c6098 fffff800`02f55bf0 nt!KeBugCheckEx 01 fffff880`086c60a0 fffff800`02ed5cee nt! ?? ::FNODOBFM::`string'+0x4518f 02 fffff880`086c6200 fffff800`02f2636e nt!KiPageFault+0x16e 03 fffff880`086c6398 fffff800`032df7fe nt!wcsstr+0x56 04 fffff880`086c63a0 fffff800`032df860 nt!SiIsWinPEBoot+0x4e 05 fffff880`086c63e0 fffff800`032e2952 nt!SiCheckForUfdWinpeBoot+0x30 06 fffff880`086c64c0 fffff800`032e2a1d nt!SiCheckForAlternateSystemDisk+0x12 07 fffff880`086c64f0 fffff800`032e479e nt!SiGetBiosSystemDisk+0x9d 08 fffff880`086c6570 fffff800`032fa4a7 nt!SiGetBiosSystemPartition+0x2e 09 fffff880`086c65c0 fffff800`032dfb5a nt!SiGetSystemPartition+0x27 0a fffff880`086c65f0 fffff800`0326554d nt!SiGetSystemDeviceName+0x3a 0b fffff880`086c6650 fffff800`032e5207 nt!IopRetrieveSystemDeviceName+0xac 0c fffff880`086c66b0 fffff800`0323c6f9 nt!IoQuerySystemDeviceName+0x37 0d fffff880`086c66f0 fffff800`031e33ad nt! ?? ::NNGAKEGL::`string'+0x52a6c 0e fffff880`086c6aa0 fffff800`02ed6e53 nt!NtQuerySystemInformation+0x4d 0f fffff880`086c6ae0 00000000`76fe161a nt!KiSystemServiceCopyEnd+0x13 10 00000000`0104c098 00000000`00000000 0x76fe161a
wcsstr is a C++ string library function, which is used to search a substring (selected group of characters) within a wide string.
To be honest, I'm not completely sure why it's being called, but the problem is generated when the Kernel attempts to page some data into physical memory, but isn't able to because of a I/O error.
SiCheckForAlternateSystemDisk function makes me feel that there is a problem with the hard-drive too, checking for a alternate bootable partition?
Since, it maybe can't read the boot sector on your current Active partition.
I just clean installed windows on my new hard drive. Got a western digital 1tb black drive. No problems and it's been about 12 hours. I will mark this as solved in a few days if no errors occur if not, I'll be back :)
That's great to know, let's hope it solves the issue :)