Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Windows 7 rare bsod

  • Please log in to reply
7 replies to this topic

#1 Biscuiti


  • Members
  • 2 posts
  • Local time:07:49 AM

Posted 31 March 2018 - 07:38 AM

But guaranteed with driver verifier enabled.

It happens rarely after the desktop has loaded, since two weeks ago. Two total bsods. Nothing new (soft or hardware) installed.

It happens evey time after the desktop has loaded with dverifier enabled. Also the resolution is very low when verif is enabled.


Can't upload archived dump since it's 99MB. 1.6GB original size.



Debugger says this :


Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Biscuiti\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a1a000 PsLoadedModuleList = 0xfffff800`02c5fe90
Debug session time: Sat Mar 31 14:31:23.441 2018 (UTC + 3:00)
System Uptime: 0 days 0:01:21.033
Loading Kernel Symbols
Loading User Symbols

Loading unloaded module list
The context is partially valid. Only x86 user-mode context is available.
The wow64exts extension must be loaded to access 32-bit state.
.load wow64exts will do this if you haven't loaded it already.
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff980820ccff0, 2, 1, fffff80002b5b908}

Probably caused by : Unknown_Image ( nt!IoEnumerateDeviceObjectList+68 )

Followup: MachineOwner

16.4: kd:x86> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arg1: fffff980820ccff0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002b5b908, address which referenced memory

Debugging Details:

WRITE_ADDRESS:  fffff980820ccff0


fffff800`02b5b908 48              dec     eax



LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

00000000 00000000 00000000 00000000 00000000 0x0

STACK_COMMAND:  .bugcheck ; kb

fffff800`02b5b908 48              dec     eax

SYMBOL_NAME:  nt!IoEnumerateDeviceObjectList+68

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  Unknown_Image



MODULE_NAME: Unknown_Module

Followup: MachineOwner




The PC doesn't show any errors while doing anything else.



Could I get some help ?

Edited by hamluis, 01 April 2018 - 06:52 AM.
Moved from Win 7 to Crashes/BSODs - Hamluis.

BC AdBot (Login to Remove)


#2 sflatechguy


  • BC Advisor
  • 2,255 posts
  • Gender:Male
  • Local time:11:49 PM

Posted 31 March 2018 - 08:54 AM

I assume you are running dverifier because you suspect one or more drivers are buggy. Any idea which ones? I suspect dverifier is the culprit here in the BSODs, as it tests drivers by stressing them. That's why the dump file is so huge. So unless you're willing to go through that file and identify the driver that is not performing properly, your best course of action is to either uninstall the drivers you suspect are causing the problem, or not run driver verifier.


The bugcheck 0xA error usually occurs after the installation of a faulty driver or BIOS.

#3 Biscuiti

  • Topic Starter

  • Members
  • 2 posts
  • Local time:07:49 AM

Posted 31 March 2018 - 09:26 AM

I enabled the verifier after the second bsod because it was the go to solution on this forum. Wanted to see which driver was the problem.

Without the verifier, when the two bsods occured, the dump was ~600MB. Of course I deleted them after I looked at them with BlueScreenView, which was very minimalistic in details : "Caused by Adddress" and "Cause By Driver" fields were empty.

#4 sflatechguy


  • BC Advisor
  • 2,255 posts
  • Gender:Male
  • Local time:11:49 PM

Posted 31 March 2018 - 09:52 AM

Unfortunately, dverifier isn't providing much more insight. You'll need to look at when the BSODs began, and what had been installed/updated around that time, and try removing it.

#5 hamluis



  • Moderator
  • 56,381 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:10:49 PM

Posted 31 March 2018 - 07:36 PM

Please download MiniToolBox  , save it to your desktop and run it.
Checkmark the following checkboxes:
  List last 10 Event Viewer log
  List Installed Programs
  List Users, Partitions and Memory size.
Click Go and paste the content into your next post.
Also...please Publish a Snapshot using Speccy taking care to post the link of the snapshot in your next post.

   Go to Piriform's website, and download the free version on the left.  Click Download from Piriform.com (the FileHippo link requires an extra click). Or if you want to use a portable version of Speccy (which doesn't require installation), click the builds page link and download the portable version. You will now be asked where you want to save the file. The best place to put it is the Desktop, as it will be easy to find later.

    After the file finishes downloading, you are ready to run Speccy. If you downloaded the installer, simply double-click on it and follow the prompts until installation is complete. If you downloaded the portable version, you will need to unzip it before use. Right-click the ZIP file and click Extract all. Click Next. Open up the extracted folder and double-click on Speccy.
     Once inside Speccy, it will look similar to this (with your computer's specifications, of course):

     Now, at the top, click File > Publish Snapshot.

     Click Yes > then Copy to Clipboard

Now, once you are back in the forum topic you are posting in, click the ADD REPLY or REPLY TO THIS TOPIC button. Right-click in the empty space of the Reply box and click Paste. Then, click Add Reply below the Reply box.


#6 bwv848


    Bleepin' Owl

  • BSOD Kernel Dump Expert
  • 3,029 posts
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:11:49 PM

Posted 31 March 2018 - 08:02 PM

Can you zip and attach the minidumps located in %SystemRoot%\Minidump? Do you have VMWare installed by any chance?


Edit: Now that your topic has been moved to our BSOD forum, can you follow https://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/ instead?

Edited by bwv848, 01 April 2018 - 08:09 AM.

If I do not reply in three days, please message me.
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)

#7 joseibarra


  • Members
  • 1,284 posts
  • Gender:Male
  • Location:Downstairs
  • Local time:11:49 PM

Posted 31 March 2018 - 11:56 PM

I suggest that you:

  • Provide fundamental information about your system
  • Make an adjustment to your Windows settings so your crash dump files are accumulated and a reasonable size for uploading
  • Then accumulate and upload several recent crash dumps to look for a pattern of failure then zero in on the cause

Here's how to get started:


On your Desktop right click Computer, Properties, Advanced system settings and make it look like this:




There is no need to create the Minidump folder as Windows will create one if it needs to.


The crash dumps will accumulate in the C:\Windows\Minidump folder (assuming Windows is installed on your C drive).


Then click OK enough times to close all the dialog boxes and restart your system for the changes to take effect.  After rebooting you can go back and check the settings again to be sure the adjustments "stick".


In your next reply you can supply more information that will reduce the number of question asking message cycles if you will do this:


If your system is a Dell what is the Service Tag number?

If your system is HP what is the serial number?


Describe your antivirus/antimalware environment.


Can you make the system crash at will - if there is something in particular you do that makes the system crash like watching videos, listening to music, etc. tell us what that something is that causes the system to crash every time.


Click the Start button/orb in the lower-left corner of your screen. Or, press the Windows logo key on your keyboard.


In the box enter:


Select/click msinfo32.exe and the System Information dialog box will open.

Click on System Summary, click Edit, Select All (Ctrl-A), Copy (Ctrl-C) and then paste (Ctrl-V) the information back here in your next reply.


For video driver information, expand the Components, click Display, click Edit, Select All (Ctrl-A), Copy (Ctrl-C) and then paste (Ctrl-V) the information back here.


There will be some personal information (like System Name and User Name), and whatever appears to be private information to you, just delete it from the pasted information.


Then do whatever you have to do get the system to crash again and you should have a crash dump file to upload for analysis.


Sometimes more than one crash dump is needed to pinpoint the cause so send some of the most recent ones.

Edited by joseibarra, 31 March 2018 - 11:58 PM.

The mediocre teacher tells. The good teacher explains. The superior teacher demonstrates.

#8 dmccoy


  • BSOD Kernel Dump Expert
  • 1,188 posts
  • Gender:Male
  • Local time:10:49 PM

Posted 01 April 2018 - 01:33 PM

I also recommend performing a clean boot as follows to help find the possible bad driver.



We are all volunteers so please by kind, courteous and respectful


I try to respond in 24-48 hours normally and I am more active on weekdays than weekends. However, sometimes due to my health, family or life it may take me a little longer. If you have not heard from me within 72 hours then please PM me a reminder. 


BC BSOD Posting Instructions 

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users