Windows 7 BSODs and Crashes

yossarian23 · 09 Nov 2009

Hi. I have had several crashes over the past few days, usually when I am not at the computer, but sometimes when I am working on it as well.

Here is what WhoCrashed reported:

On Mon 11/9/2009 4:42:36 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000046, 0xFFFFF80002CA37F8, 0xFFFFF880059DD770, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\110809-22245-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.

On Mon 11/9/2009 4:23:39 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000046, 0xFFFFF80002CAE7F8, 0xFFFFF88009A1F770, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\110809-21356-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.

On Sun 11/8/2009 8:51:06 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x9F (0x3, 0xFFFFFA8007DAE0C0, 0xFFFFF80000B9C518, 0xFFFFFA800B5181E0)
Error: DRIVER_POWER_STATE_FAILURE
Dump file: C:\Windows\Minidump\110809-22588-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.

On Sun 11/8/2009 5:55:23 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x9F (0x3, 0xFFFFFA80079B6060, 0xFFFFF80000B9C518, 0xFFFFFA800A20FC60)
Error: DRIVER_POWER_STATE_FAILURE
Dump file: C:\Windows\Minidump\110809-27908-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.

On Sun 11/8/2009 9:58:48 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x9F (0x3, 0xFFFFFA8004F05060, 0xFFFFF8000400A518, 0xFFFFFA80052143A0)
Error: DRIVER_POWER_STATE_FAILURE
Dump file: C:\Windows\Minidump\110809-41043-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.

On Sun 11/8/2009 9:16:45 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x9F (0x3, 0xFFFFFA800A4D4060, 0xFFFFF80000B9C518, 0xFFFFFA80090E2B10)
Error: DRIVER_POWER_STATE_FAILURE
Dump file: C:\Windows\Minidump\110809-53180-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.

Also, here are the reports from the Event Viewer. I have tried to update my video card driver, but still had crashes. I know that there are dump reports, but I am not sure how to open them.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000046, 0xfffff80002ca37f8, 0xfffff880059dd770, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 110809-22245-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000046, 0xfffff80002cae7f8, 0xfffff88009a1f770, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 110809-21356-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xfffffa8007dae0c0, 0xfffff80000b9c518, 0xfffffa800b5181e0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 110809-22588-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xfffffa80079b6060, 0xfffff80000b9c518, 0xfffffa800a20fc60). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 110809-27908-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xfffffa8004f05060, 0xfffff8000400a518, 0xfffffa80052143a0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 110809-41043-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xfffffa800a4d4060, 0xfffff80000b9c518, 0xfffffa80090e2b10). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 110809-53180-01.

H2SO4 · 09 Nov 2009

Hello and welcome to SF :)

https://www.sevenforums.com/crash-loc...d-problem.html

yossarian23 · 09 Nov 2009

Sorry about that. The contents of my minidump folder are attached.

I have had a variety of errors since installing (clean) Windows 7, including several BSODs. Some I attribute to errors I had with DVDFab6 software when I had inserted a scratched DVD that my DVD drive struggled to read. However, the other errors are a mystery to me. I have come to my computer several times after having been away for several hours with a message that the computer has rebooted, has shut down unexpectedly, etc.

H2SO4 · 09 Nov 2009

yossarian23 said:

Sorry about that. The contents of my minidump folder are attached.

I have had a variety of errors since installing (clean) Windows 7, including several BSODs. Some I attribute to errors I had with DVDFab6 software when I had inserted a scratched DVD that my DVD drive struggled to read. However, the other errors are a mystery to me. I have come to my computer several times after having been away for several hours with a message that the computer has rebooted, has shut down unexpectedly, etc.

Two of these crashes are caused by this old driver:

Image path: \SystemRoot\System32\Drivers\pcouffin.sys
Image name: pcouffin.sys
Timestamp: Wed Dec 06 01:39:30 2006 (457584A2)

The others are caused by a combination of a USB-connected device and its driver doing weird stuff, though I can't tell which device from a minidump. Try to temporarily disconnect some or all of your USB devices, as a test.

yossarian23 · 10 Nov 2009

Thanks. That makes me feel better that the installation itself is not the culprit.

Elan643 · 04 Aug 2010

How does one go about determining the cause of a crash by using the mini dump file? Is there a tool to read it and understand it? Mine is attached as well after a random blue screen. Thanks in advance.

sh4ne · 08 Aug 2010

Make a new thread for your problem, Elan643 -- you won't get a reply here in an old thread

ttran · 08 Aug 2010

How does one go about determining the cause of a crash by using the mini dump file? Is there a tool to read it and understand it? Mine is attached as well after a random blue screen. Thanks in advance.

Hi and Welcome to SF!

A couple of KB articles that relate to the errors that you're getting and the sleep/hibernate functions:

KB 975599 Stop error when you put a computer that is running Windows 7 or Windows Server 2008 R2 to sleep or into hibernation, or when you restart the computer: "0x9F"
KB 977186 Error message when you try to resume a Windows 7-based or a Windows Server 2008 R2-based computer from hibernation: "Stop 0x0000009F"

I'm not sure about the exact cause - but I would check to see if the KB articles above apply to your system

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: http://www.duplexsecure.com/en/downloads

BUGCHECK SUMMARY:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.453\080310-23665-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`04144500?
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a15000 PsLoadedModuleList = 0xfffff800`02c52e50
Debug session time: Wed Aug  4 07:27:25.756 2010 (UTC + 7:00)
System Uptime: 5 days 8:29:52.254
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8004e8d060, fffff80004144518, fffffa800563e260}

Probably caused by : atapi.sys

Followup: MachineOwner
---------

And yes, next time please make your new thread. We use what is called WinDbg to read your DMP
https://www.sevenforums.com/crashes-d...tructions.html

Regard,

Tuan