Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Random browsing - 0x0000009f

28 Jul 2017   #1
EmKal

Windows 7 Ultimate x64
 
 
BSOD Random browsing - 0x0000009f

Hi,

I had a few BSODs recently, initially the problem was with a one of four 4gb memory sticks giving errors when running MemTest 86. So I decided to upgrade the memory to 24 gb (from original 16gb) instead of just replacing the faulty unit as I usually max out my memory when having too many Chrome tabs plus Photoshop running at the same time. I bought two 8gb DDR3 (9-9-9-24) G.Skills sticks to replace 2 of 4 4gb DDR3 (9-9-9-24) G. Skills (one of which was faulty). So the current memory configuration is 2x4gb plus 2x8gb (DDR3 (9-9-9-24) G. Skills, all identical manufacturer and speed, only different size pairs). I did not turn on xmp profile in bios as I don't have time to fiddle around with it right now and just wanted to increase total memory size.

In order to use more than 16gb of memory I needed to upgrade Windows from Home to Ultimate, which I did through the online tool that did not require a clean install of Win7. After the upgrade I received an error that one of the drivers was missing or something, I did not take a print screen so I can't recall the exact error. Since then (been running Win7 Ultimate since July 10, for almost three weeks) I had several BSODs related to drivers. I tried updating drivers through device manager, even attempted updating Motherboard drivers with a CD, but the BSOD happened right after anyways, so I did a system restore to remove the drivers installed from a CD, as the system has been otherwise stable for years with the previous drivers.

I am not sure what the culprit is, I went through all the drivers one by one, and these show as missing:

High precision event timer
Direct memory access controller
Intel(R) 7Series/C216 Chipset Family SMBus Host Controller - 1E22
Intel (R 82802 Firmware Hub Device
Numeric Data Processor for Chipset LPC Controller 1E44
Programmable Interrupt Controller for Chipset LPC Controller 1E44
System Timer for Chipset LPC Controller 1E44

It is overwhelming to do all this research, but from searching the names of individual missing drivers, it seems that these are fine to not be installed??

I am attaching a few printscreens from NirSoft BlueScreen View, Speccy and so on, but I am unable to attach a minidump zip file that was collected by DM Log Collector, as it tells me I don't have admin privileges (which I do). I did try to take ownership of the generated .zip file file as suggested in this article (Windows 7 Take Ownership & Grant Permissions to Access Files & Folder)


Please help to sort all of this out
Thanks in advance.

Emilia

Attachment 400074

Attachment 400075

Attachment 400076

Attachment 400077


My System SpecsSystem Spec
.
28 Jul 2017   #2
EmKal

Windows 7 Ultimate x64
 
 

Was able to manually archive three latest minidump files from my desktop. If anyone could take a look.
My System SpecsSystem Spec
28 Jul 2017   #3
EmKal

Windows 7 Ultimate x64
 
 

Let Driver Verifier run for all non-Microsoft drivers, the system would usually BSOD when put to sleep, here is what BlueScreenView is saying, please see images attached.
Attachment 400083

Attachment 400084

Attachment 400085

Attachment 400086


This is from WhoCrashed:
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 7/28/2017 11:46:06 PM your computer crashed
crash dump file: C:\Windows\Minidump\072817-11575-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0xA (0xFFFFF98027EC2FA0, 0x2, 0x1, 0xFFFFF800035A62B8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 7/28/2017 11:46:06 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hcmon.sys (hcmon+0x66B9)
Bugcheck code: 0xA (0xFFFFF98027EC2FA0, 0x2, 0x1, 0xFFFFF800035A62B8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\hcmon.sys
product: VMware USB monitor
company: VMware, Inc.
description: VMware USB monitor
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hcmon.sys (VMware USB monitor, VMware, Inc.).
Google query: VMware, Inc. IRQL_NOT_LESS_OR_EQUAL



On Fri 7/28/2017 11:43:59 PM your computer crashed
crash dump file: C:\Windows\Minidump\072817-19780-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x142FD)
Bugcheck code: 0xC9 (0x21A, 0xFFFFF880014142FD, 0xFFFFF98074578CF0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 7/28/2017 7:26:58 PM your computer crashed
crash dump file: C:\Windows\Minidump\072817-18345-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x142FD)
Bugcheck code: 0xC9 (0x21A, 0xFFFFF8800182A2FD, 0xFFFFF980538CACF0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 7/28/2017 1:53:55 PM your computer crashed
crash dump file: C:\Windows\Minidump\072817-10530-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8015BCD060, 0xFFFFF80000B9A3D8, 0xFFFFFA8013CA5B80)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Thanks Again!!
My System SpecsSystem Spec
.

30 Jul 2017   #4
axe0

Windows 10 Pro
 
 

When do you exactly get the message that you don't have permission to access the zip? While the DM Log Collector is running?
My System SpecsSystem Spec
31 Jul 2017   #5
EmKal

Windows 7 Ultimate x64
 
 

Thanks for replying.

I get errors when I try to access the resulting zip file, or to upload it here. I was able to just zip up and upload here the last three .dmp files after coping them to desktop (please see my second post). I do have the ownership of the mini-dump folder and each of the individual files (when looking in the advance option of the security tab in properties), and I have the ownership of the zip file created by the tool. I don't get any errors while the log tool is running, just cannot access or upload the resulting zip file.

Thanks again!
Attachment 400123
My System SpecsSystem Spec
31 Jul 2017   #6
mrjimphelps

Linux Mint 18.2 xfce 64-bit (VMWare host) / Windows 8.1 Pro 32-bit (VMWare guest)
 
 

Please check this post to see how to get the drivers you need.
My System SpecsSystem Spec
31 Jul 2017   #7
axe0

Windows 10 Pro
 
 

Before closing the tool, if I remember correctly the tool creates a new folder. You may be able to zip this folder and upload it instead of the zip created by the tool.
My System SpecsSystem Spec
31 Jul 2017   #8
EmKal

Windows 7 Ultimate x64
 
 

I ran the tool a few more times and this time watched the complete operation, and there is an error that pops up before the end. The tool does create a zip file that I then cannot open, but this is what I see just before it completes:
Attachment 400138
My System SpecsSystem Spec
31 Jul 2017   #9
EmKal

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by mrjimphelps View Post
Please check this post to see how to get the drivers you need.
I looked at the linked post, and not sure about which drivers on that list would be useful. My pc was not giving me any BSODs errors related to drivers prior to upgrading from Home to Ultimate. Since I replaced the faulty memory sticks, my MemTests are coming clean of errors as well.

When I ran the driver Verifier tool for a few hours, it would cause BSOD only when I put my computer to sleep (I did have to exclude all the Windows drivers, or my pc would not boot past Windows screen, only in safe mode), but I am not sure about how applicable the results are for my current problem. You can see in my 3rd post pictures -- what drivers were identified as problematic BlueScreenView.exe (failed the verifier when put under a strain test). Again not sure if it is useful info to fix the original driver issue.
My System SpecsSystem Spec
03 Aug 2017   #10
EmKal

Windows 7 Ultimate x64
 
 

Not sure if the file collected by the DM LOG Collector tool is special and different from simply zipping up some minidump files, but here are the minidumps related to this issue if somebody can please take a look. I also attached the excel version of the xml file created during the last BSOD as well as the original .xml file.

Attachment 400210

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8015C19060
BCP3: FFFFF80000BA0748
BCP4: FFFFFA801CC6D930
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\080317-10670-01.dmp
C:\Users\Userman\AppData\Local\Temp\WER-29796-0.sysdata.xml




From WhoCrashed:

On Thu 8/3/2017 9:09:05 AM your computer crashed
crash dump file: C:\Windows\Minidump\080317-10670-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8015C19060, 0xFFFFF80000BA0748, 0xFFFFFA801CC6D930)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Many thanks in advance!
My System SpecsSystem Spec
Reply

 BSOD Random browsing - 0x0000009f




Thread Tools




Similar help and support threads
Thread Forum
BSOD DRIVER_POWER_STATE_FAILURE Random occurrence, error 0x0000009f
It started about 3-4 weeks ago, after I installed new RAM and changed the nVidia drivers ("luck"" has it i did both at the same time). It seemed to have no actual cause, no set time for the BSOD to show up and no real sense behind it. I've since reinstalled my system and ran through pretty much...
BSOD Help and Support
Random BSOD: DRIVER_POWER_STATE_FAILURE with 0x0000009f, slow PC
Hello, friend of mine has problem on one computer, it is Lenovo E540 with i7 CPU and is incredible slow - after Win logon he has to wait like 2 or 3 minutes to be able to work normally, PC is freezing sometimes, it is slow and displaying some errors occasionally. Sometimes he also gets BSOD,...
BSOD Help and Support
Random BSOD, error 0x0000009f
I actually rarely get the BSOD. Usually the computer just reboots with no error displayed, nothing recorded in the event log. Only Twice has the error, 0x0000009f, been recorded. I have attached the grab all from SF diagnostics tool. As far as I can tell there is no particular event that triggers...
BSOD Help and Support
Random BSOD crashes...error code 0x0000009f
Hello, I've been having BSOD crashes for some time now and haven't been able to attribute them to any particular action. They sometimes occur when the computer is just sitting idle. System Specs Windows 7 Home Premium 64-bit Original OS (OEM) Hardware age: 2 yrs OS Installation age: 2...
BSOD Help and Support
Need help with random BSOD crashes, error 0x0000009f
Hi, Would appreciate some help with some random BSODs that seem to have got worse on Christmas Day. Is Windows 7 x86 (32-bit) or x64 ? x64 the original installed OS on the system? No an OEM or full retail version? Full Retail What is the age of system (hardware)? About 2 years What...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 01:59.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App