Skip to content
View in the app

A better way to browse. Learn more.

MSFN

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Siig0680 driver causing BAD_POOL_CALLER BSOD on startup

Featured Replies

I installed my nLite build, XP SP2 with Xables update pack included. Items checked for removal were mostly cosmetic (language and keyboard setups, etc.).

Installed okay, but with each login attempt a window appears "Windows Desktop Update" and shortly afterwards I get BSOD BAD_POOL_CALLER (parameters varying each time). Googling tells me there is a faulty device driver that isn't playing well with system drivers.

I am able to boot in safe mode, and found the following:

I looked in the Event Viewer and the error reported there was that Fips and Processor drivers failed to load. I tried to open the dump files, but dumpchk is not loaded on the machine. I sorted through it in notepad, and did manage to find this clue - dump_pnp680.sys - pnp680 is a driver for my SIIG 0680 PCI IDE controller. I included the only driver I could find (direct from siig, recent, and supposedly good for XP) in the nLite build. I don't have a floppy drive, so I cannot use the F6 method to install the card at the beginning of setup (which is primarily why I'm using nLite, plus all the hotfix updates etc.) The drive I'm installing on is a Seagate 300GB, which is too large to work on my old GA7DX mainboard (so removing the siig controller is not an option)

This is the only unsigned driver on the install. I thought it was odd that I could boot up in safe mode if the driver really is problematic, so to be sure I removed all other components and drivers, and still got BSODs at the same point in startup, but this time with different errors:

BAD_POOL_HEADER

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

Googling these also indicates the same problem, a device driver that is conflicting with a system driver.

Suggestions here?

Edited by guyin808


Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.