IRQL BSOD problems

Okay so a little back story here. I built a computer about a year ago and had a lot of trouble getting it up and running because of an incompatibility issue between the mobo and my memory. Since then I got new memory and have had no issues except for "random" IRQL BSODs. This past summer I was getting these screens that said


DRIVER_IRQL_NOT_LESS_OR_EQUAL
...
STOP: 0x000000D1 (...)
USBPORT.SYS - Address B92696AF base at B9264000


or some variation of this about once a day. I spent a lot of time troubleshooting this and eventually I tried increasing the voltage to my memory from 1.80v to 1.90v. I have had no more issues with the above errors until today when I opened Adobe Photoshop and got


IRQL_NOT_LESS_OR_EQUAL
...
STOP: 0x0000000A (...)


I don't know why I randomly got this error after almost 3 months of smooth operation since I increased the voltage to my memory. I did a WinDbg dump anaylsis on this crash and I have the output if anyone can analyze that...I just didn't want to scare people away with such a large first post. Thank you for any help/advice you may have.

 

Well I ran through the suggested crash dump program and this is what I got. From what I can see it looks like it is saying that Adobelmsvc.exe is the problem, but I don't really think that makes sense because I've had similar crashes before and they didn't involve Photoshop...then again I don't know much about these reports so if anyone has any ideas please let me know.


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


Loading Dump File [C:\WINDOWS\Minidump\Mini100707-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Program Files\Debugging Tools for Windows\sym
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.061219-0316
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sun Oct 7 14:20:33.359 2007 (GMT-5)
System Uptime: 2 days 0:01:36.048
Loading Kernel Symbols
..........................................................................................................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {96b55e4c, 2, 0, 8050e252}

Probably caused by : memory_corruption ( nt!MiFlushSectionInternal+292 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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.
Arguments:
Arg1: 96b55e4c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 8050e252, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: 96b55e4c

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiFlushSectionInternal+292
8050e252 8b460c mov eax,dword ptr [esi+0Ch]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: Adobelmsvc.exe

LAST_CONTROL_TRANSFER: from 8050edda to 8050e252

STACK_TEXT:
ad459714 8050edda e4bd0e00 e4bd1000 e4bd0ef0 nt!MiFlushSectionInternal+0x292
ad459750 804e4341 8941e848 00000000 00000000 nt!MmFlushSection+0x1f2
ad4597d8 ba647b75 89420184 00000000 00000000 nt!CcFlushCache+0x1d3
ad459804 ba661924 8a771598 e4b250d0 00000000 Ntfs!NtfsFlushUserStream+0x6c
ad459888 ba661dc9 8a771598 8a83a600 00000001 Ntfs!NtfsFlushVolume+0x22a
ad459928 ba655385 8a771598 8a697578 ad450000 Ntfs!NtfsCommonVolumeOpen+0x341
ad459a00 804ef095 8a83a520 8a697578 896ca2a8 Ntfs!NtfsFsdCreate+0x154
ad459a10 ba6c5876 8a697588 8a931968 896ca2a8 nt!IopfCallDriver+0x31
ad459a5c 804ef095 8a83ae88 00000001 8a697578 sr!SrCreate+0x150
ad459a6c 80581f6e 8a898998 896505ac ad459c04 nt!IopfCallDriver+0x31
ad459b4c 805bddc0 8a8989b0 00000000 89650508 nt!IopParseDevice+0xa12
ad459bc4 805ba448 00000000 ad459c04 00000040 nt!ObpLookupObjectName+0x53c
ad459c18 80574ec1 00000000 00000000 781df801 nt!ObOpenObjectByName+0xea
ad459c94 80575838 007dfe64 80100080 007dfe04 nt!IopCreateFile+0x407
ad459cf0 80577f02 007dfe64 80100080 007dfe04 nt!IoCreateFile+0x8e
ad459d30 8054086c 007dfe64 80100080 007dfe04 nt!NtCreateFile+0x30
ad459d30 7c90eb94 007dfe64 80100080 007dfe04 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
007dfe5c 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiFlushSectionInternal+292
8050e252 8b460c mov eax,dword ptr [esi+0Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiFlushSectionInternal+292

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4587e148

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiFlushSectionInternal+292

BUCKET_ID: 0xA_nt!MiFlushSectionInternal+292

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

 

Thanks for clarifying that is was a memory error rather than something caused by Adobe. I actually have done a bit of testing with the memory back when I was still getting frequent BSOD related to IRQL errors.

Basically I tried running my 2, 1 gig sticks in a variety of slots until I got something that was working. My setup now is 1 gig of ram seated in slots 1 and 2 out of 4. I also ran memTest overnight this summer with this configuration and everything tested fine. I will try running it tonight though...maybe the memory has developed problems in the 3 months since then? Is there any chance that increasing the voltage by a small amount could have damaged the memory? Thanks for the help by the way

 

Update:

Since my last post I surprisingly haven't had ANY blue screen problems with my computer. However, since then it has started to run progressively slower. For example, last week I went to play Diablo II (a very old game that is NOT graphic intensive) and it was running at around 13 fps when usually it used to just stay at 60.

Does this sound like something that could be related to the memory trouble I was having before?

Also I downloaded a temperature reading program and it is telling me that my core is at 55C and that my +12v rail on my PSU is at 6.18v. Is it possible that my power supply is going bad? Thanks for any help!

 

Hi,
55*C is not bad, I would check it after you exited the game though. I suggest opening the case and checking all the fans are spinning freely (and maybe the PSU fan specifically).

That voltage is WAY out, but some third party software may not be able to read the sensors correctly. The best reading for voltage will be by going into the BIOS/startup settings and checking there. If there are no voltage readings in the BIOS, there may not be an accurate method of reading them anyway apart from using a volt meter.

If you can confirm that voltage reading, I would replace the PSU, it may be doing damage to your hardware.

Matt

 

Yeah after some searching around I found another program that read it correctly and I also confirmed it in the BIOS. So apparently the voltages are fine...I'm also pretty sure it's not overheating because I have a giant fan blasting into my case right now and Diablo II still runs like a slide show. I have no idea what is wrong...

 

Update:

So the other night I decided to try and run a different game besides HL2 or Diablo II just to see if it was all choppy too. I played an entire round of Unreal Tournament and it was completely fine! No lag whatsoever! Is it possible that I have a direct3D problem? I ran all of the diagnostics in dxdiag with direct draw and 3D both testing fine. The only weird part was when 3D did the spinning cube test, it spun so fast it looked like a tornado...I couldn't even tell what the picture was or that it was even a cube. Any suggestions? Thanks.