BSOD when restarting windows after exteneded user session.

You need to supply a fresh copy of your System Information as my system is indicating that the file is corrupt. The recorded file size is unusually large.

I ran the uninstaller for spdt.sys.

the ireg.sys was part of WinDVD BD for TOSHIBA, I went ahead and uninstalled it since I know have PowerDVD 13.

as for Diskeeper, I have completely turned it off for now. I do find it odd however that Microsoft uses a 'lite' version of Diskeeper in windows with out issues, but the full feature version sometimes causes problems.

I have enabled driver verifier with all the specified options. normally the error occurs after an extended session when I restart windows. by extended, I mean more than a couple of days. I leave the PC in s3 during the night but don't restart it unless asked to by windows.

Hi,

BlueScreenView is not as accurate for the cause as WinDBG. However it is excellent for checking

the driver information in the lower panel.

Check with Nvidia and the other device makers - as suggested above run DriverView - set VIEW

to Hide Microsoft drivers - update those without Dump in their names. There are likely to be a

lot of them available which are not at Toshiba. This is a Toshiba laptop I am on now.

As Patrick indicated DiskKeeper has been known to cause issues. I doubt it is causing this one

however it is possible.

My general feeling is the real issue is the video hardware just can't play some games which is

normal for most laptops not actually built specifically for gaming.

After you do all the driver updates run Driver Verifier as Patrick and I have both suggested.

Hope this helps.

Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle <- Mark Twain said it right!

Thanks for the DMP files!

As Rob mentioned, the attached DMP files of the DRIVER_POWER_STATE_FAILURE (9f) bug check.

*This bug check indicates that the driver is in an inconsistent or invalid power state.*As opposed to your traditional *9F bug check that contains a blocked IRP on the 4th parameter of the bug check held by a driver, this *9F indicates that there is a lock being caused by a driver.

-------------

1. sptd.sys is not a system driver, I don't know where you got that information from. sptd.sys is listed and loaded in your modules list; SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win 7 and 8). Please remove it ASAP with the uninstaller tool - http://www.duplexsecure.com/en/downloads
2. Diskeeper is known to cause crashes, please remove it for troubleshooting purposes.
3. regi.sys - Mon Apr 16 11:19:10 2007

^^ InterVideo regi.sys driver, dated from 2007. Fairly dated, so please go ahead and remove Intervideo for troubleshooting purposes.

4. Enable Driver Verifier if you're crashing after all of the above so we can get more information:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point

Windows 7 - START | type create | select "Create a Restore Point"

Windows 8 - http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -

• Special Pool
• Pool Tracking
• Force IRQL Checking
• Deadlock Detection
• Security Checks (Windows 7 & 8)
• DDI compliance checking (Windows 8)
• Miscellaneous Checks

4. Select  - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is [B]NOT[/B] provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

• If Driver Verifier finds a violation, the system will BSOD.
• After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

• Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
• Once in Safe Mode - Start > Search > type "cmd" without the quotes.
• To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.

・    Restart and boot into normal Windows.

If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

• Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
• Once in Safe Mode - Start > type "system restore" without the quotes.
• Choose the restore point you created earlier.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in %systemroot%\Minidump

Any other questions can most likely be answered by this article:

http://support.microsoft.com/kb/244617

Regards,

Patrick

I AM NOT overclocking at all, unless you count the i7's built-in turboboost feature as overclocking.

SPTD.SYS is a system driver. description is SCSI Pass through Direct Host. driver is by Duplex Secure Ltd.

I do not have Daemon Tool or Alcohol installed.

bluescreenview (as I already stated) indicates ntoskrnl.exe as the only cause of the crash not ntkrnlmp.exe

My laptop runs a wide variety of games just fine with out any issues what so ever. this is due to the fact that my unit has a discrete (dedicated) video card with it's own separate memory (although upto 1768Mb of memory can be dynamically shared from system memory using NVidia turbocache )

My bios and drivers are up to date. there may or may not be issues with my bios, but Toshiba is no longer releasing updating bios/drivers for my unit (even though it is less than 4 years old)

as the error only occurs after windows has been booted for an extended period when I try to restart, clean booting will not help.