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 IRQL/Memory Management/everything else

30 Jul 2010   #11

Win7 32-bit

Attached is another minidump - it indicated a driver on the crash screen, but I didn't have time to read what it was.

My System SpecsSystem Spec
30 Jul 2010   #12

Windows 7 Professional x64

This one looks pretty straightforward. It appears your nVidia graphics drivers are the cause.

I see they are dated September 2009, and there is a July 2010 update. Please install it: Drivers - Download NVIDIA Drivers

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

Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_073010-15787-01 -\073010-15787-01 - Copy.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a48000 PsLoadedModuleList = 0x82b90810
Debug session time: Fri Jul 30 18:00:13.926 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:10.565
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
2: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Attempt to reset the display driver and recover from timeout failed.
Arg1: 87421008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 91cce1a0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.

Debugging Details:

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

91cce1a0 55              push    ebp





96276b74 925ae92c 00000116 87421008 91cce1a0 nt!KeBugCheckEx+0x1e
96276b98 925af74b 91cce1a0 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
96276bbc 910cb92c 00000000 00000102 8745d008 dxgkrnl!TdrIsRecoveryRequired+0xb8
96276c34 910f5a32 fffffcfb 00002ee1 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
96276c5c 910f6153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
96276c98 910d28f0 96276c90 874b97d0 879d6978 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
96276d28 910f74b7 8745d008 82a843f1 8745d008 dxgmms1!VidSchiScheduleCommandToRun+0xaa
96276d3c 910f7573 8745d008 00000000 87472a48 dxgmms1!VidSchiRun_PriorityTable+0xf
96276d50 82c5666d 8745d008 b85d5c42 00000000 dxgmms1!VidSchiWorkerThread+0x7f
96276d90 82b080d9 910f74f4 8745d008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

STACK_COMMAND:  .bugcheck ; kb

91cce1a0 55              push    ebp

SYMBOL_NAME:  nvlddmkm+bf1a0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys


FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner

2: kd> lmvm nvlddmkm
start    end        module name
91c0f000 9251f160   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sun Sep 27 20:13:17 2009 (4ABFFF9D)
    CheckSum:         0091A611
    ImageSize:        00910160
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
30 Jul 2010   #13

Win7 32-bit

I installed new drivers, but the bluescreens aren't stopping. The latest bluescreen showed dxgmms1.sys as the culprit.
My System SpecsSystem Spec

30 Jul 2010   #14

Windows 7 Ultimate 32 bit

dxgmms1.sys points to your video card. Both of these dumps have an error code of 7E - Memory corruption.


Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
BSOD Index

Please recap for us what steps of those suggested you have completed so far.

I find these two of date drivers on your system.

AtiPcie.sys Tue May 05 11:00:16 2009 - ATI PCIE Driver for ATI PCIE chipset Update this driver

wdcsam.sys Wed Apr 16 04:27:02 2008 - WD SCSI Architecture Model (SAM) driver - WD External Storage - Western Digital Technologies. Western Digital External Drive RAID Manager Update this driver.
My System SpecsSystem Spec
30 Jul 2010   #15

Win7 32-bit

I've uninstalled Norton software and updated the video card driver, from the nVidia website. Since my last post, there has been another Driver IRQL error, showing usbohci.sys as the offending driver.
My System SpecsSystem Spec
30 Jul 2010   #16

Windows 7 Ultimate 32 bit

usbohci.sys is a Microsft driver and most likely not the cause. It just got blamed.

Since the error code of the last two dumps you uploaded are 7E, lets check your RAM. Download a copy of Memtest86+ - Advanced Memory Diagnostic Tool and burn the ISO to a CD using Boot from the CD, and leave it running for at least 7 passes. Post back with the results.

If Memtest checks back clean after 7+ passes, follow these instructions for enabling driver verifier: Using Driver Verifier to identify issues with Drivers
Please follow these instructions in order to run it:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link:
Using Driver Verifier to identify issues with Windows drivers for advanced users

My System SpecsSystem Spec
30 Jul 2010   #17

Microsoft Window 7 Professional 32 bit

In addtion to Carl great advise, USBOHCI.sys is a Windows core driver and it has to do with USB miniport, I would recommend to update your motherboard driver
My System SpecsSystem Spec
31 Jul 2010   #18

Win7 32-bit

I didn't record any problem with the RAM, but I'm still getting IQRL errors. With driver verifier on, I was not able to boot the OS - it would hang at the windows 7 screen.

The memory dumps taken in the morning were without driver verifier on, and should not show it. I activated verifier.exe a few minutes ago, and attached that memory dump separately. It showed a different error than before - something with a D at the end.
My System SpecsSystem Spec
31 Jul 2010   #19

Microsoft Window 7 Professional 32 bit

There are different stop codes with different things were blamed. Personally, I suspect this is graphic card issue as I can see a stop code 8E with dxgkrnl.sys was blamed. Do you have another graphic card that you can test?

Also with exception code c0000005, which is memory access violation, I would follow Carl advise to test the Ram using memtestx86. Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

Update this driver please:
AsIO     AsIO.sys     Mon Dec 17 16:10:20 2007 (47663CFC)
It is Asus PCProbe Utility, ASUSTeK Computer Inc.-Support-

BugCheck 5, {1, 85d17858, 0, 0}

Probably caused by : ndis.sys ( ndis!ndisPassIrpDownTheStack+3d )

Followup: MachineOwner
BugCheck C5, {80b47dcc, 2, 0, 82b3204d}

Probably caused by : ntkrpamp.exe ( nt!ExAllocatePoolWithTag+49d )

Followup: MachineOwner
BugCheck 1A, {41284, 213e001, 964, c0802000}

Probably caused by : memory_corruption ( nt!MiLocateWsle+c1 )

Followup: MachineOwner
BugCheck 7F, {0, 0, 0, 0}

Probably caused by : ntkrpamp.exe ( nt!KiTrap00+8b )

Followup: MachineOwner
BugCheck 1000008E, {c0000005, 82a97f3d, 9ed17b64, 0}

Probably caused by : dxgkrnl.sys ( dxgkrnl+1512 )

Followup: MachineOwner

My System SpecsSystem Spec
31 Jul 2010   #20

Win7 32-bit

The machine only comes with two slots for DIMMs, and the ram comes as a set. Would it make sense to just test both sticks at the same time? There isn't much recourse I can take if one of them turns out to be bad.

EDIT: I'm afraid there is no other graphics card I can test.
My System SpecsSystem Spec

 BSOD IRQL/Memory Management/everything else

Thread Tools

Similar help and support threads
Thread Forum
Bsod: Irql not less or equal & memory management upon startup
Please help it has happened overnight somehow my computer is blue screening no less than a minute of startup.. i have tried EVERYTHING from virus scans, re installing, etc... Safe mode seems to work okay. for some reason, i do not have a minidump folder... please let me know what i need...
BSOD Help and Support
BSOD of IRQL or Memory Management
Greetings Everyone! Recently I have been getting BSOD with error messages such as IRQL not equal or less or memory management. After countless hours of research I did several things to check of it was my driver problem or simply RAM problem. I followed the driver verification and MEM86+ test. I...
BSOD Help and Support
BSOD, Memory Management & IRQL not less or equal
Hi, two days ago my computer was running smoothly and fine. Then the day after, i got a bunch of BSODs. Help me pretty please :) Here are the dump files i got and my PC specs. OS: Windows 7 Professional 32-bit Processor: AMD Athlon 64 x2 5000+ Memory: 2GB RAM Mobo: ASRock N68C-S UCC...
BSOD Help and Support
Repeating BSOD - Memory Management + IRQL.
Hows it going guys/gals, first post :) unfortunatly it has to be a sad one :( As the name states i have been having many BSOD in the past months the exact error codes im unsure of as untill recently i was unsure how to stop instant restarting. Anywho the problems are a range of Memory...
BSOD Help and Support
BSOD irql not less or equal, memory management and more
I am at my wits end! i have had my custom built computer for almost 2 years now used to have an ASUS P5N32-E SLI Plus AiLifestyle nForce 650i SLI/570 SLI Socket 775 8 channel audio ATX Motherboard and thought that it was causing my blue screens due to the chipset on the board being quite...
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 00:22.
Twitter Facebook Google+