Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

luweitest

Member
  • Posts

    199
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    China

About luweitest

Profile Information

  • OS
    XP Pro x86

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

luweitest's Achievements

60

Reputation

  1. The problem gets more interesting. I could use F8 to select boot logging. The normal boot and safe mode boot log is attached below. It is strange that safe mode log only has one line, not the first driver, nor likely the last driver. The more strange thing is: it cannot be opened in recovery console, either using "type ntbtlog.txt" or "more ntbtlog.txt", which will trigger BSoD of BAD_POOL_HEADER 0x19. I did some experiment: Changing the file name has same BSoD effect; Changing the file length could make it open; Changing the file encoding could make it open (It is natively Unicode LE encoded, i.e. starting with FFFE); Changing the file content while keeping the length has same effect; Hex editing the ending 0D00 0A00, if edited to 0D00 6100 or 6100 0A00, same effect; if edited to 6100 6100, it opens. So it seems recovery console and safe mode boot of my machine cannot handle this specific text: 112 bytes of Unicode LE encoded text with one or half new line ending. Could someone try opening the attached ntbtlog_safe.txt in recovery console or safe mode command line? ntbtlog_normal.txt ntbtlog_safe.txt
  2. I've got some new information, from https://atkdinosaurus.wordpress.com/2015/08/01/windows-services-and-service-start-order/: "The HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServiceGroupOrder subkey determines the order in which Service Groups are loaded. The List value is a REG_MULT_SZ entry that specifies the Service Group order. The HKEY_LOCAL_MACHINE\CurrentControlSet\Control\GroupOrderList subkey determines the order in which services within a Service Group are loaded. Services in a Service Group are assigned a tag, a unique numeric value within a Service Group which determines the service load order. Each value entry in GroupOrderList represents a Service Group. The value of the entry is a series of tags in a specified order. The first entry in this REG_BINARY value is the number of services in the group, followed by the tags in load sequence. " So I tried two methods: 1, Delete items from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal which are not in the ServiceGroupOrder; 2, Add items to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal which are in the ServiceGroupOrder, with the value "Driver Group" . Both method failed to work.
  3. I got two new places to check for possible drivers list: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal Don't know which one takes precedence, but they both have iaStor.sys related item as: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2829&cc_0106 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\{4D36E96A-E325-11CE-BFC1-08002BE10318} And as @jaclaz pointed out about 7E error, it seems SATA driver is loaded. I recorded a video of safe mode booting. After a screen of drivers list (iaStor.sys is in the last of that screen list), the following drivers only flashes at the bottom line. After "press Esc to cancel loading d347bus.sys" (strange the driver was shown at the first screen before, but loaded after sometime. It is from virtual CD driver Daemon tools and has been excluded from suspicion), I pressed Esc and then BSOD. The last driver I can catch before that "cancel loading" screen is APS***.sys, which is APSX86.sys or ApsHM86.sys from hardware driver (ThinkVantage active protection to suspend hard disk when shaking, should be excluded from suspicion). I now don't know what to look for, since SATA driver iaStor.sys seems to be excluded. safe mode boot.mp4
  4. Yes, all drivers are official and latest (except wifi card I deliberately installed a little older one, which should not matter). "inaccessible boot device" seems accord with my speculation that the SATA disk driver (iastore.sys) is not loaded in safe mode. Reasonable because I guess safe mode only includes drivers at OS setup stage. Another evidence is, if I add "/bootlog" parameter to normal boot, it will get BSOD too. I suspect the disk driver is not loaded yet when trying opening the log file.
  5. In Serpent you could do this: bookmark a duckduckgo page, then menu-> bookmark->right click the duckduckgo item under "recently bookmarked"->properties, this will bring up edit dialogue: Modify as above (you could choose another keyword other than "d"), then you could type "d <query word>" in the address bar.
  6. My chipset: BSOD message is STOP: 0x0000007E (0xC0000005, 0xF76E0211,0xF78EA700,0xF78EA3FC) The Intel's SATA driver is installed after Windows XP is installed in compatibility mode, then restart and change to AHCI mode in BIOS, and then Windows XP works in new mode. But I am not sure if this driver is the culprit; It is only my speculation. Thus I hope there's a way to check drivers one by one. "/sos" parameter just lets drivers loading flashes away and I can't catch up.
  7. I've published my key to keyserver too; its not legally prohibited anyway -- though you know PRC gov does not act according to laws. My concern is he not get targeted. Maybe it won't happen since XP is becoming a minority platform.
  8. My Windows XP would go to BSOD in booting to safe mode. If there is an interactive booting mode like Windows 98, letting me choose whether to load a driver or not, I think the troubleshooting would be easier. I could boot into recovery console mode, in which I see SATA driver iaStor.sy_ is loaded. So I think of a possibility that in safe mode Windows XP do not load AHCI|SATA drivers. If I could add the driver to that "minimal" driver list of safe mode, the problem may be solved. Could that be done?
  9. I tested 4 Github tabs in 4 process separately without problem. My relevant setting: browser.tabs.remote.force-enable;true dom.ipc.processCount;8 layers.acceleration.enabled;false Correction: I concluded too quickly; Github actually crippled in various ways with e10s and latest github-wc-polyfill, though downloading works.
  10. Finally I found the culprit. Since stop services and kill processes do not solve the problem, and the problem occurs after logging in, then it must be some device driver, as @RainyShadow said, but not the normal driver that loaded before logging in. I then used Autoruns, found in the device list ADS812S and ADSIO, which is used for Advantech's data card before, deleted them, and all standby and hibernation functions returned! The record in the previous powercfg /devicequery all_devices_verbose is attached, in which it seems nothing unusual. Enumerating Device: 175 =================== Device Information: DeviceName: ADS812S HardwareID(s): UNKNOWN Device Present. Device is not capable of waking the system. Device Power Capabilities: D0 supported D3 supported Device State Mappings: S0 -> D0 S1 -> D3 S2 -> D3 S3 -> D3 S4 -> D3 S5 -> D3 Derived System State Mappings: S0 supported S1 supported S2 supported S3 supported S4 supported S5 supported Address: Unavailable Bus Number: Unavailable Class GUID: {8ECC055D-047F-11D1-A537-0000F8753ED1} Compatible device ID(s): Unavailable Device Description: ADS812S Driver Name: {8ECC055D-047F-11D1-A537-0000F8753ED1}\0051 Device Enumerator: ROOT Device Location: Unavailable Lower Filter(s): Unavailable Upper Filter(s): Unavailable Service Name: ADS812S Security Description: Unavailable SPDRP_REMOVAL_POLICY: CM_REMOVAL_POLICY_EXPECT_NO_REMOVAL Hardware Removal Policy: CM_REMOVAL_POLICY_EXPECT_NO_REMOVAL Override Removal Policy: Unavailable Physical Device Object name: \Device\00000007 Manufacturer: Unavailable Enumerating Device: 176 =================== Device Information: DeviceName: ADSIO HardwareID(s): UNKNOWN Device Present. Device is not capable of waking the system. Device Power Capabilities: D0 supported D3 supported Device State Mappings: S0 -> D0 S1 -> D3 S2 -> D3 S3 -> D3 S4 -> D3 S5 -> D3 Derived System State Mappings: S0 supported S1 supported S2 supported S3 supported S4 supported S5 supported Address: Unavailable Bus Number: Unavailable Class GUID: {8ECC055D-047F-11D1-A537-0000F8753ED1} Compatible device ID(s): Unavailable Device Description: ADSIO Driver Name: {8ECC055D-047F-11D1-A537-0000F8753ED1}\0050 Device Enumerator: ROOT Device Location: Unavailable Lower Filter(s): Unavailable Upper Filter(s): Unavailable Service Name: ADSIO Security Description: Unavailable SPDRP_REMOVAL_POLICY: CM_REMOVAL_POLICY_EXPECT_NO_REMOVAL Hardware Removal Policy: CM_REMOVAL_POLICY_EXPECT_NO_REMOVAL Override Removal Policy: Unavailable Physical Device Object name: \Device\00000008 Manufacturer: Unavailable
  11. Title edited. Sorry for the typo :) powercfg /H OFF|On both gives: System does not support hibernation powercfg /devicequery all_devices_verbose gives long list; what to look for? The list is like: Enumerating Device: 006 =================== Device Information: DeviceName: PS/2 TrackPoint HardwareID(s): ACPI\IBM3780 *IBM3780 Device Present. Device is not capable of waking the system. Device Power Capabilities: D0 supported D3 supported Device State Mappings: S0 -> D0 S1 -> UNSPECIFIED (PowerStateMapping 0x0) S2 -> UNSPECIFIED (PowerStateMapping 0x0) S3 -> D3 S4 -> D3 S5 -> D3 Derived System State Mappings: S0 supported S3 supported S4 supported S5 supported Address: Unavailable Bus Number: Unavailable Class GUID: {4D36E96F-E325-11CE-BFC1-08002BE10318} Compatible device ID(s): *PNP0F13 Device Description: PS/2 TrackPoint Driver Name: {4D36E96F-E325-11CE-BFC1-08002BE10318}\0000 Device Enumerator: ACPI Device Location: Unavailable Lower Filter(s): Unavailable Upper Filter(s): Tp4Track Service Name: i8042prt Security Description: Unavailable SPDRP_REMOVAL_POLICY: CM_REMOVAL_POLICY_EXPECT_NO_REMOVAL Hardware Removal Policy: CM_REMOVAL_POLICY_EXPECT_NO_REMOVAL Override Removal Policy: Unavailable Physical Device Object name: \Device\00000093 Manufacturer: Lenovo I searched the list and there is no word "unsupported".
  12. My laptop (thinkpad x61) have been unable to standby for sometime. It used to work fine. I googled a lot and failed to find a solution. The symptom: 1, Power button or start->shutdown, the menu shows: greyed Standby (press shift will not switch it to Hibernate), Shutdown and Restart. But if I do it before user login, the Standby button is normal and Standby actually works, yet only once, after back from standby, it becomes grey again. 2, Control panel -> Power options, there is no Hibernation tab; but in Advanced tab ->close the lid, there are two options: Do nothing and Hibernate, without Standby. Closing the lid will make the screen dark when Do nothing is chosen. 3, Cmd -> "powercfg /a" gives: The following sleep states are not available on this system: Standby (S1) Standby (S2) Standby (S3) Hibernate. 4, Under C:\ there is hiberfil.sys, which cannot be deleted. Even if I deleted it after closed the file handle by procexp, it recreates after reboot. 5, In Lenovo's power management software, "Enable hibernation" is greyed out. I have reinstalled Intel chips driver, Intel video driver, ACPI driver, power management software; checked BIOS, nothing relevant. Switched memory from 4G to 2G; stopped services and killed processes one by one, while checking the shutdown Standby menu, still grey. Group policy has no relevant option either. The last thing I won't try is reinstalling Windows. I think maybe Windows is given the false information about sleep ability after user logged in. Is this information hidden somewhere in the registry? Any suggestion is appreciated.
  13. Hopefully @roytam1 could recreate another key; I do have concerns about his special identity as a HKer.
  14. Yes! works with: @="cmd /c \"pause|\"C:\\Program Files\\GnuPG\\bin\\gpg.exe\" --verify \"%1\"\""
  15. Well maybe in their opinion it's not gnupg breaking things but windows xp's bug in batch processing, since windows 7 could handle it. Who knows. Anyway, gnupg could still be used on xp, if no bat|cmd file is concerned. Edit: oops, just find the latest gnupg 2.3.2 cannot decrypt (gpg-agent cannot start; though encryption works). 2.3.1 is the last one now.

×
×
  • Create New...