BleepingComputer.com > New Parts

BleepingComputer.com > Hardware > Internal Hardware

Pages: 1, 2

Rabid Ferrets of DOOM!!!

Jun 5 2007, 11:01 AM

Ok... So I recently bought an Asus M2N SLI Deluxe mobo (nforce 570), an AMD 64 X2 5200+ and 2 gigs of OCZ ATI Crossfire RAM. Now the computer is running great. Problem is after a little while I get a BSOD. From what I know there are (at least) 3 different possibilities none of which I really know how to solve... The error is DRIVER_IRQL_IS_NOT_LESS_OR_EQUAL or something like that I don't remember the file it's complaining about I'll write it down next BSOD I get. Ok I looked in the logs in the reliability monitor and I believe this is the error code: 0x000000d1 (0xffffff70, 0x00000001, 0x00000000, 0x8a90ee9e).

When I get the BSOD, my computer doesn't start for about 5 mins. If I press the power button it does nothing. However, after 2 mins or so if I try to turn it on I get 1 long beep followed by 2 short beeps. Apparantly this means a GPU issue. That would make sense I believe I have a defective GPU as when I run it for long enough I get a lot of graphical glitches on my screen. However, I see this as the least likely possibility because although I was getting these glitches for months before I upgraded my comp, I never got any crashes from it.

It seems that this motherboard has an issue with OCZ Gold RAM - the beeps "supposedly" can mistake this problem with GPU problems. Apparantly the RAM runs at 2 or 2.1 V (W? Can't remember. XD) when the mobo supports only up to 1.95. However... I am using OCZ RAM but I do not think it's "gold" ram. Also, the people with this problem sounded like they were unable to boot, and the solution given was to get the computer able to boot so they could flash the bios to the newest version... which I already have. Also in the BIOS the mobo has options up to 2.30 V for the RAM (Can't find what the max supported in the board manual is.) For the time being I took one of the two chips out seeing if that helps.'

Finally, the second of the four times this has happened, I booted into a BSOD (Only time I booted into one.) It told me I had a corrupt .dll and I needed to do a repair install. I rebooted once more and I booted just fine. However, I wasn't connected to the internet... After fooling around with device manager for a few hours I found that my drivers for the two "nVidia Network Bus Enumerator" devices had been wiped followed by my networking controllers. (I have only been able to get one of the networking controllers working...) From skimming the nvidia boards it seems that the LAN drivers are problematic so this seems pretty likely as well...

Oh and in case it helps I'm on Vista 32 bit and I'm using an MSI GeForce 7900 GT. One other note is that the BSODs seem to only happen when I'm gaming online. (Not sure if online has anything to do with it I'm just online all the time.) Except for one time it happened just sorta randomly although I think it may be because I tried to use readyboost on my iPod... I don't think it actually *let* me try though so I don't know if that had anything to do with it.

So one thing I read was that if I run only one chip of RAM it should be fine. If that works I'd put the second chip in but in single channel mode not dual channel. It took 2 hours, but with a single chip I got a BSOD.

Currently I am running both chips but I changed the voltage in the BIOS down to 1.95 V (Although supposedly it runs 2V originally I still don't know for a fact.)

I found out that in XP the error code meant usually a bad device driver which would make sense becuase I had driver troubles (see 4th paragraph) that were never fully resolved. I'm thinking this is most likely at this point since all the ram issues I read about were different circumstances involving dual channel not working with the ram. Single channel doesn't work either and my BIOS are up to date, and my RAM is the same brand as the problems but a different series. However, I'm not quite sure just how to resolve the problem if this is what's causing it. The device getting the error is one of my two network adapters and it is "This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)" So I think I'm going to disable that device and see if it is resolved.

If that doesn't work I'm going to run memtest86 but I really doubt that my memory is bad.

I'm sifting through event viewer right now I can't find much other than "Previous shutdown unexpected" However just before one BSOD I have a whole cluster of "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{8BC3F05E-D86B-11D0-A075-00C04FB68820}
to the user Ferret-PC\Ferret SID (S-1-5-21-3470726999-3793355774-3343032829-1000) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool." these. No idea what it means but there you go.

While I was attempting to get the drivers applied to the devices I described earlier, I have a whole mess of these: "IRQARB: ACPI BIOS does not contain an IRQ for the device in PCI slot 13, function 0. Please contact your system vendor for technical assistance." it goes from slot 10 to 15 I believe. BSOD is undocumented, though, I'm searching for my .dmp and .mdmp now.

I just realized something that might be important. I attempted to run windows memory test - the one that you pick when picking which OS to boot with. It froze at 3% of the first test. I don't know if that means bad memory or not because as I said the computer doesn't boot up for about 5 minutes after the BSOD which I think may be do to it freezing before it shows anything on screen. Either way it might be important, so yeah there you go... ... ... still waiting to hear from somebody.

Thanks in advance for your help!

Rabid Ferrets of DOOM!!!

Jun 5 2007, 12:54 PM

Ok. I'm going to give relevant errors to the best of my ability. (I've gotten 5 BSODs so far. There are more than 5 errors for unexpected shutdowns. I do not know which is which so I'm giving all my 6008s.)

Error code 6:

CODE

IRQARB: ACPI BIOS does not contain an IRQ for the device in PCI slot 15, function 0. Please contact your system vendor for technical assistance.

I get one of these for PCI slot 15,14,10,11,12,13 in that order. These are my Standard PCI-to-PCI Bridge devices according to device manager (I think these are the right ones. PCI BUS 0 - Device 10 - Function 0, etc.)

6008
6008
6008
6008

Error 6 for the same devices.

24620:

CODE

Encrypted volume check: Volume information on J: cannot be read.

Error 6 for the same devices 5 times (30 errors)

10000:

CODE

Unable to start a DCOM Server: {2692A9D5-61DF-46D5-A5A1-A6CCA921D578}. The error:
"740"
Happened while starting this command:
"C:\Program Files\Apple Software Update\SoftwareUpdate.exe" -Embedding

I get this error:

CODE

Windows Servicing failed to complete the process of changing update 936824-5_RTM_PACKAGE from package KB936824(Update) into Staging(Staging) state

And:

CODE

Windows Servicing failed to complete the process of changing update 936824-6_RTM_PACKAGE from package KB936824(Update) into Staging(Staging) state

Those two are my own fault, I think. I had started up my computer and was unable to connect to the internet. I had two "Other PCI Bridge Device" with errors in device manager. Neither had drivers. I have 2 Ethernet ports. That's what I assumed they were. So I tried to put the ethernet drivers onto them (running the driver program from nVidia didn't put any driver *on* the devices. I uninstalled and reinstalled 3 times.) I got this set twice more only the update got a _1 and then a _2.

Next I got three sets of:

CODE

Windows Servicing failed to complete the process of setting package KB936824 (Update) into Staging(Staging) state

And then another set of:

CODE

Windows Servicing failed to complete the process of changing update 929685-1_RTM_GDR from package KB929685(Update) into Staging(Staging) state

CODE

Windows Servicing failed to complete the process of changing update 929685-2_RTM_GDR from package KB929685(Update) into Staging(Staging) state

At that point I had the right drivers on the unknown PCI devices (Which turned out to be my nVidia Bus Enumerators.) That caused 2 new devices to show up which WERE my network adapters. However, I had trouble getting the drivers onto these two. (Only one of them currently has the driver second one still doesn't work.)

Then one more:

CODE

Windows Servicing failed to complete the process of setting package KB929685 (Update) into Staging(Staging) state

Now 10:

CODE

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{8BC3F05E-D86B-11D0-A075-00C04FB68820}
to the user Ferret-PC\Ferret SID (S-1-5-21-3470726999-3793355774-3343032829-1000) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Ran windows update. Unable to install a language pack I needed for some reason...

CODE

This computer must be restarted before attempting to install or remove languages

Application initialization failed. Last error: 0x80004004

Installation Failure: Windows failed to install the following update with error 0x80070643: Korean Language Pack.

2 more 6008s

Then another set of 6s

CODE

The IP address lease 192.168.230.104 for the Network Card with network address 001A92F02318 has been denied by the DHCP server 0.0.0.0 (The DHCP Server sent a DHCPNACK message).

Followed by one more 6008 which was my last BSOD so far.

I also know for sure that gaming has something to do with the BSODs. I have had my computer running for more than 12 hrs with no BSOD however I've had no games running. I do not know if it's caused by having high RAM usage, GPU usage, or Ethernet usage, but 2 runs of 3d mark didn't get a BSOD and bit torrent's been running all morning. Last night when I got the last BSOD I was playing CS:S. The program crashed 3 times and after the third time I got a BSOD. The game was running for about a 30-45 mins or so before the BSOD.

Sorry for the long post.

stevealmighty

Jun 5 2007, 01:03 PM

HERE's a chart for computer beep codes. One long and two short is a video issue.

Does this happen only when playing CS:S? Try a different game other than CS:S-as that game is known to have issues (lots of issues!). I'd reseat the video card, ensure that everything is plugged in correctly and reboot. Also, make sure that the power cord that powers your gfx card has nothing else plugged into it.

What type of PSU do you have (link would be nice also please)?

Rabid Ferrets of DOOM!!!

Jun 5 2007, 01:09 PM

No. It's also happened while playing BF2142. I know that the 1 long beep 2 short means video issue but it's been known to signify other issues as well with ASUS boards. Everything's installed properly and my GPU cable is fine. I doubt is a gfx issue because it's been running fine. I'm looking for a dmp so I find the file that the error brings up I'm sure that'd help quite a bit. Don't know what PSU I have off the top of my head. I'll crack the case open and tell you in just a minute.

Rabid Ferrets of DOOM!!!

Jun 5 2007, 01:12 PM

Dammit I don't see my PSU model printed anywhere I can see. Any other way I can see what it is? XD

Rabid Ferrets of DOOM!!!

Jun 5 2007, 01:22 PM

Ok. I am looking at the 1 dmp that's from a blue screen when I wasn't gaming. It seems to have been caused by usbport.sys. I think that's because I was trying to use readyboost on my ipod. XD

I've got two minidumps somewhere but search won't give me a path... This one was memory.dmp. I'll try to find them and post when I have.

Rabid Ferrets of DOOM!!!

Jun 5 2007, 01:23 PM

Wait... This might have something... Here's what it has:

CODE

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffff70, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8a90ee9e, address which referenced memory

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

READ_ADDRESS:  ffffff70

CURRENT_IRQL:  2

FAULTING_IP:
USBPORT!USBPORT_Core_iGetEpHwPendingTransferCount+101
8a90ee9e ff7018          push    dword ptr [eax+18h]

DEFAULT_BUCKET_ID:  VISTA_RC

BUGCHECK_STR:  0xD1

PROCESS_NAME:  WinSAT.exe

TRAP_FRAME:  82834e9c -- (.trap ffffffff82834e9c)
ErrCode = 00000000
eax=ffffff58 ebx=87ec6988 ecx=8795d580 edx=8779b0e8 esi=00000000 edi=81c91df4
eip=8a90ee9e esp=82834f10 ebp=82834f28 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
USBPORT!USBPORT_Core_iGetEpHwPendingTransferCount+0x101:
8a90ee9e ff7018          push    dword ptr [eax+18h]  ds:0023:ffffff70=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8a90ee9e to 81c8fc44

STACK_TEXT:
82834e9c 8a90ee9e badb0d00 8779b0e8 81fa98e5 nt!KiTrap0E+0x2ac
82834f28 8a90740f 8779b028 31636865 81c91df4 USBPORT!USBPORT_Core_iGetEpHwPendingTransferCount+0x101
82834f60 8a9055b9 8779b028 8779bac0 8779b002 USBPORT!USBPORT_Core_UsbMapDpc_Worker+0x239
82834f88 81ca93ae 8779bacc 34776478 00000000 USBPORT!USBPORT_Xdpc_Worker+0x273
82834ff4 81c90d8d c5edad10 00000000 00000000 nt!KiRetireDpcList+0x147
82834ff8 c5edad10 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x3d
WARNING: Frame IP not in any known module. Following frames may be wrong.
81c90d8d 00000000 0000001a 00c1850f bb830000 0xc5edad10

STACK_COMMAND:  kb

FOLLOWUP_IP:
USBPORT!USBPORT_Core_iGetEpHwPendingTransferCount+101
8a90ee9e ff7018          push    dword ptr [eax+18h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  USBPORT!USBPORT_Core_iGetEpHwPendingTransferCount+101

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4549b26d

FAILURE_BUCKET_ID:  0xD1_USBPORT!USBPORT_Core_iGetEpHwPendingTransferCount+101

BUCKET_ID:  0xD1_USBPORT!USBPORT_Core_iGetEpHwPendingTransferCount+101

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

Rabid Ferrets of DOOM!!!

Jun 5 2007, 01:27 PM

This is from one of the BSODs that happened when I was gaming I THINK but the error is different and I don't have an unexpected shutdown error in event viewer from that time.

CODE

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {81a50073, 8, 81a50073, 0}

Could not read faulting driver name
Probably caused by : fileinfo.sys ( fileinfo!_NULL_IMPORT_DESCRIPTOR <PERF> (fileinfo+0xf073)+0 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: 81a50073, memory referenced.
Arg2: 00000008, value 0 = read operation, 1 = write operation.
Arg3: 81a50073, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000000, (reserved)

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

Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d11780
81a50073

FAULTING_IP:
fileinfo!_NULL_IMPORT_DESCRIPTOR <PERF> (fileinfo+0xf073)+0
81a50073 3a813a8f3a94    cmp     al,byte ptr [ecx-6BC570C6h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_RC

BUGCHECK_STR:  0x50

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  0

TRAP_FRAME:  96bb38c8 -- (.trap ffffffff96bb38c8)
ErrCode = 00000010
eax=9ba343d0 ebx=99fd3738 ecx=00000000 edx=9ba341f8 esi=99fd36d8 edi=00000884
eip=81a50073 esp=96bb393c ebp=96bb3950 iopl=0         nv up ei ng nz ac po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010293
fileinfo!_NULL_IMPORT_DESCRIPTOR <PERF> (fileinfo+0xf073):
81a50073 3a813a8f3a94    cmp     al,byte ptr [ecx-6BC570C6h] ds:0023:943a8f3a=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 81c8fa74 to 81ca9ef2

STACK_TEXT:
96bb38b0 81c8fa74 00000008 81a50073 00000000 nt!MmAccessFault+0x106
96bb38b0 81a50073 00000008 81a50073 00000000 nt!KiTrap0E+0xdc
96bb3950 81a520b6 99fd36d8 96bb3994 81a5251b fileinfo!_NULL_IMPORT_DESCRIPTOR <PERF> (fileinfo+0xf073)
96bb395c 81a5251b 99fd36d8 00000220 9ba34105 fltmgr!FltpInitializeIrpCtrl+0xb0
96bb3994 81a68a5e 86d8dee8 00000001 9ba341f8 fltmgr!FltpAllocateIrpCtrl+0x17d
96bb39e8 81c27ecf 86d8dee8 86d8da78 9ba3c1e4 fltmgr!FltpCreate+0x26e
96bb3a00 81d96f5c 96bb81f8 86e72b9c 86240650 nt!IofCallDriver+0x63
96bb3ab8 81deef0d 86240668 00000000 86e72af8 nt!IopParseDevice+0xcff
96bb3b48 81dec6b9 00000000 96bb3ba0 00000040 nt!ObpLookupObjectName+0x615
96bb3ba8 81d8c5db 0025ca9c 00000000 99e5e901 nt!ObOpenObjectByName+0x13c
96bb3d54 81c8c96a 0025ca9c 0025ca74 0025cacc nt!NtQueryAttributesFile+0x125
96bb3d54 777e0f34 0025ca9c 0025ca74 0025cacc nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0025cacc 00000000 00000000 00000000 00000000 0x777e0f34

STACK_COMMAND:  kb

FOLLOWUP_IP:
fileinfo!_NULL_IMPORT_DESCRIPTOR <PERF> (fileinfo+0xf073)+0
81a50073 3a813a8f3a94    cmp     al,byte ptr [ecx-6BC570C6h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  fileinfo!_NULL_IMPORT_DESCRIPTOR <PERF> (fileinfo+0xf073)+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fileinfo

IMAGE_NAME:  fileinfo.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4549ae1f

FAILURE_BUCKET_ID:  0x50_W_fileinfo!_NULL_IMPORT_DESCRIPTOR__PERF__(fileinfo+0xf073)+0

BUCKET_ID:  0x50_W_fileinfo!_NULL_IMPORT_DESCRIPTOR__PERF__(fileinfo+0xf073)+0

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

Rabid Ferrets of DOOM!!!

Jun 5 2007, 01:30 PM

This is the last one I have. It's from about 1.5-2 hours after the most recent BSOD. Maybe it is USBPORT.sys...?

CODE

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffff70, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8a90ee9e, address which referenced memory

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

READ_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d11780
ffffff70

CURRENT_IRQL:  2

FAULTING_IP:
USBPORT!USBPORT_Core_iGetEpHwPendingTransferCount+101
8a90ee9e ff7018          push    dword ptr [eax+18h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_RC

BUGCHECK_STR:  0xD1

PROCESS_NAME:  WinSAT.exe

TRAP_FRAME:  82834e9c -- (.trap ffffffff82834e9c)
ErrCode = 00000000
eax=ffffff58 ebx=87ec6988 ecx=8795d580 edx=8779b0e8 esi=00000000 edi=81c91df4
eip=8a90ee9e esp=82834f10 ebp=82834f28 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
USBPORT!USBPORT_Core_iGetEpHwPendingTransferCount+0x101:
8a90ee9e ff7018          push    dword ptr [eax+18h]  ds:0023:ffffff70=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8a90ee9e to 81c8fc44

STACK_TEXT:
82834e9c 8a90ee9e badb0d00 8779b0e8 81fa98e5 nt!KiTrap0E+0x2ac
82834f28 8a90740f 8779b028 31636865 81c91df4 USBPORT!USBPORT_Core_iGetEpHwPendingTransferCount+0x101
82834f60 8a9055b9 8779b028 8779bac0 8779b002 USBPORT!USBPORT_Core_UsbMapDpc_Worker+0x239
82834f88 81ca93ae 8779bacc 34776478 00000000 USBPORT!USBPORT_Xdpc_Worker+0x273
82834ff4 81c90d8d c5edad10 00000000 00000000 nt!KiRetireDpcList+0x147
82834ff8 c5edad10 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x3d
WARNING: Frame IP not in any known module. Following frames may be wrong.
81c90d8d 00000000 0000001a 00c1850f bb830000 0xc5edad10

STACK_COMMAND:  kb

FOLLOWUP_IP:
USBPORT!USBPORT_Core_iGetEpHwPendingTransferCount+101
8a90ee9e ff7018          push    dword ptr [eax+18h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  USBPORT!USBPORT_Core_iGetEpHwPendingTransferCount+101

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4549b26d

FAILURE_BUCKET_ID:  0xD1_USBPORT!USBPORT_Core_iGetEpHwPendingTransferCount+101

BUCKET_ID:  0xD1_USBPORT!USBPORT_Core_iGetEpHwPendingTransferCount+101

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

Rabid Ferrets of DOOM!!!

Jun 5 2007, 01:39 PM

Ok. So looking at the two USBPORT errors... How do I fix it? The only USB device I have plugged in (Except for the second one I put) is my Razer Diamondback mouse. Should I reinstall the driver for it? The second one I put is actually the first of the three BSODs I have dmps for and it's the third one that I got. The first two I can't see a dump for.

So... In the fileinfo.sys... The instruction address and the memorry addressed are the same... So I think it's bogus but I don't get into this stuff often so I wouldn't know. That one happened right after I had gotten my drivers working (for the most part) on the bus enumerators and one of my ethernet ports.

Oh, also, about the beeps, it was continuous not just once. And it fixed itself after 2 mins so I don't think it applies I think it's just an aftershock of the BSOD. I only booted into a BSOD once (I think I mentioned it but just in case...) It said I had a corrupt dll and I needed to do a repair install. But it restarted and went a way. Actually... I don't remember if it was a blue screen or not I think it was black and white actually. XD

stevealmighty

Jun 5 2007, 01:42 PM

Try updating your DirectX version 9.0c (download and install the latest version HERE-even though you might already have it, it comes out with new updates but doesn't change the "9.0c" part).

I'm not familiar with Vista at all, but is there an option that allows you to change your page file size? If so, max it out.

Check to see if there are any BIOS updates for your mobo-if so, try updating your BIOS.

Also, download and install the latest drivers for your gfx card.

I've done some reading online and found where these things have helped to cure BSODs with issues similar to yours. Let us know if it helps or not!

If not, then we'll look more into your IRQ stuff (which is not one of my strong points!).

Rabid Ferrets of DOOM!!!

Jun 5 2007, 01:46 PM

Alright. BIOS is up to date. I can change my page file but won't it bog me down to max it? I reinstalled my gfx drivers when I got the new board, but I'll do that again since my bus and ethernet drivers got wiped maybet that one's corrupted. Getting directx now. The thing that confuses me is if the problem was usbport.sys why would these fix it?

Also were these probs on the same board? I tried reading up on other probs and a lot of them were with A8N board or other nForce 4s. From what I can tell nForce 5 is much MUCH different from 4 driver-wise and the nForce 4 drivers are bugged to hell.

Grinler

Jun 5 2007, 02:13 PM

You can rule out memory errors by download and burning memtest to a cd and booting off of it. Run some of the tests. If there are problem with the memory, or how the mobo is interacting with the memory, the test should show that. Reading more, I see you used the Vista memory diagnostics tool. If its freezing, that is not good. Could be a bad memory or problem with the board interacting with it. Try with memtest as well.

QUOTE

I also know for sure that gaming has something to do with the BSODs.

If it is the memory, this would make sense. As games use a lot of memory and are constantly writing to and from it, if there was a problem that was memory related it would show up during these intensive tasks.

QUOTE

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

More info here:

http://support.microsoft.com/kb/293077/en-us

http://support.microsoft.com/kb/810093/en-us

Could be a driver or a memory issue. I suggest downgrading your video driver and seeing it that makes a difference.

Also they reference the page file being corrupt. You can zero out the page file, reboot, and then allow windows to manage it again. See if that fixes it.

Any idea the power rating of your PSU?

Rabid Ferrets of DOOM!!!

Jun 5 2007, 02:24 PM

...
...
...
...
No.
All I know about it is that I bought it after my first mobo upgrade I had to buy a new power supply because my old mobo had a 24 pin connecter and this one had a 26...? Or whatever the numbers are. XD

Grinler

Jun 5 2007, 02:26 PM

You probably had a 20 pin and the new mobo has the 24 pin. I would try my recommendations and go from there.

Rabid Ferrets of DOOM!!!

Jun 5 2007, 02:33 PM

Yeah I'm about to leave so I'll probably run that while I'm gone.

Rabid Ferrets of DOOM!!!

Jun 5 2007, 10:56 PM

Ok... I don't have any blank DVDs. So I ran the windows built in while I was gone. When I got home my monitor was in its little power save mode and I had to hard reset. Dunno if that's just what it does when it finishes testing? The other thing I noticed was that when I started it up the BIOS post said "Memory testing 210620 OK (210942 installed)" those aren't the exact numbers but the difference was somewhere in that area.

Rabid Ferrets of DOOM!!!

Jun 6 2007, 01:12 AM

Well, I think it's fixed. Played CS:S for 2.5-3 hours no BSOD. Thanks for all your help.

Grinler

Jun 6 2007, 10:57 AM

It fixed itself on its own?

Sneakycyber

Jun 6 2007, 11:22 AM

Gremlin run out of food?

Rabid Ferrets of DOOM!!!

Jun 6 2007, 11:46 AM

Rofl. No the different things you guys suggested fixed it I think. Might be the RAM voltage being a 1.95 V, might be updating the gfx drivers, might be that the ethernet controller with the driver that wasn't working got disabled by me, or maybe the gremlin ran out of food. XD

Actually there's still a problem here I think... I haven't gotten BSOD yet but I'm still getting the "BIOS Does not have IRQ for PCI device 10-15." errors. (Those devices are my PCI bridge devices.)

Rabid Ferrets of DOOM!!!

Jun 6 2007, 02:43 PM

NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO BSOD!!!
So yeah it is not fixed.

I've got dumps debugging now I'll post the results when I've got them.

I didn't try maxing out my page file so I guess that'll be the first thing I try.

Rabid Ferrets of DOOM!!!

Jun 6 2007, 02:46 PM

CODE

*******************************************************************************
*                                                                             *
*                        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: 0092ab34, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 827a4dae, address which referenced memory

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

WRITE_ADDRESS:  0092ab34

CURRENT_IRQL:  2

FAULTING_IP:
hal!KeAcquireSpinLockRaiseToSynch+e
827a4dae f00fba2900      lock bts dword ptr [ecx],0

DEFAULT_BUCKET_ID:  VISTA_RC

BUGCHECK_STR:  0xA

PROCESS_NAME:  Idle

TRAP_FRAME:  824f1bb8 -- (.trap ffffffff824f1bb8)
ErrCode = 00000002
eax=00000002 ebx=8c079a83 ecx=0092ab34 edx=000006e4 esi=8646a2a8 edi=0092ab34
eip=827a4dae esp=824f1c2c ebp=824f1c3c iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
hal!KeAcquireSpinLockRaiseToSynch+0xe:
827a4dae f00fba2900      lock bts dword ptr [ecx],0   ds:0023:0092ab34=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 827a4dae to 8248fc44

STACK_TEXT:
824f1bb8 827a4dae badb0d00 000006e4 00000001 nt!KiTrap0E+0x2ac
824f1c28 8c02db2d 8692aa28 00000000 00000200 hal!KeAcquireSpinLockRaiseToSynch+0xe
824f1c3c 8c07a30a 8646a2a8 8c079a83 8646a2a8 ks!KsReleaseIrpOnCancelableQueue+0x22
824f1c58 8c07a8a2 8646a2a8 00000000 864d9e18 portcls!CIrpStream::ReleaseMappingIrp+0x112
824f1c70 8c07f85b 8692aa28 00000200 00000000 portcls!CIrpStream::ReleaseLockedRegion+0x94
824f1c90 8c07faa9 824f1c01 00000200 824f1cc4 portcls!CPortPinWaveCyclic::Copy+0x6f
824f1cd0 8c07bc07 00001240 824f4820 88946ac8 portcls!CPortPinWaveCyclic::RequestService+0x230
824f1ce8 824a93ae 88946ac8 88946ab8 00000000 portcls!CServiceGroup::ServiceDpc+0x2a
824f1d50 824912ae 00000000 0000000e 00000000 nt!KiRetireDpcList+0x147
824f1d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x46

STACK_COMMAND:  kb

FOLLOWUP_IP:
ks!KsReleaseIrpOnCancelableQueue+22
8c02db2d 8d4e38          lea     ecx,[esi+38h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  ks!KsReleaseIrpOnCancelableQueue+22

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ks

IMAGE_NAME:  ks.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4549b186

FAILURE_BUCKET_ID:  0xA_W_ks!KsReleaseIrpOnCancelableQueue+22

BUCKET_ID:  0xA_W_ks!KsReleaseIrpOnCancelableQueue+22

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

0: kd> lmvm ks
start    end        module name
8c028000 8c052000   ks         (pdb symbols)          c:\symbols\ks.pdb\EE6514B68A014C86B26078041F0647062\ks.pdb
    Loaded symbol image file: ks.sys
    Image path: \SystemRoot\system32\drivers\ks.sys
    Image name: ks.sys
    Timestamp:        Thu Nov 02 02:51:18 2006 (4549B186)
    CheckSum:         000285FF
    ImageSize:        0002A000
    File version:     6.0.6000.16386
    Product version:  6.0.6000.16386
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.0 Driver
    File date:        00000000.00000000
    Translations:     0000.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ks.sys
    OriginalFilename: ks.sys
    ProductVersion:   6.0.6000.16386
    FileVersion:      6.0.6000.16386 (vista_rtm.061101-2205)
    FileDescription:  Kernel CSA Library
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Here's the minidump for it as well.

Pretty sure they're exactly the same, but... Ah well. XD

CODE

*******************************************************************************
*                                                                             *
*                        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: 0092ab34, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 827a4dae, address which referenced memory

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

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 825315ac
Unable to read MiSystemVaType memory at 82511780
0092ab34

CURRENT_IRQL:  2

FAULTING_IP:
hal!KeAcquireSpinLockRaiseToSynch+e
827a4dae f00fba2900      lock bts dword ptr [ecx],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_RC

BUGCHECK_STR:  0xA

PROCESS_NAME:  Idle

TRAP_FRAME:  824f1bb8 -- (.trap ffffffff824f1bb8)
ErrCode = 00000002
eax=00000002 ebx=8c079a83 ecx=0092ab34 edx=000006e4 esi=8646a2a8 edi=0092ab34
eip=827a4dae esp=824f1c2c ebp=824f1c3c iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
hal!KeAcquireSpinLockRaiseToSynch+0xe:
827a4dae f00fba2900      lock bts dword ptr [ecx],0   ds:0023:0092ab34=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 827a4dae to 8248fc44

STACK_TEXT:
824f1bb8 827a4dae badb0d00 000006e4 00000001 nt!KiTrap0E+0x2ac
824f1c28 8c02db2d 8692aa28 00000000 00000200 hal!KeAcquireSpinLockRaiseToSynch+0xe
824f1c3c 8c07a30a 8646a2a8 8c079a83 8646a2a8 ks!KsReleaseIrpOnCancelableQueue+0x22
824f1c58 8c07a8a2 8646a2a8 00000000 864d9e18 portcls!CIrpStream::ReleaseMappingIrp+0x112
824f1c70 8c07f85b 8692aa28 00000200 00000000 portcls!CIrpStream::ReleaseLockedRegion+0x94
824f1c90 8c07faa9 824f1c01 00000200 824f1cc4 portcls!CPortPinWaveCyclic::Copy+0x6f
824f1cd0 8c07bc07 00001240 824f4820 88946ac8 portcls!CPortPinWaveCyclic::RequestService+0x230
824f1ce8 824a93ae 88946ac8 88946ab8 00000000 portcls!CServiceGroup::ServiceDpc+0x2a
824f1d50 824912ae 00000000 0000000e 00000000 nt!KiRetireDpcList+0x147
824f1d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x46

STACK_COMMAND:  kb

FOLLOWUP_IP:
ks!KsReleaseIrpOnCancelableQueue+22
8c02db2d 8d4e38          lea     ecx,[esi+38h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  ks!KsReleaseIrpOnCancelableQueue+22

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ks

IMAGE_NAME:  ks.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4549b186

FAILURE_BUCKET_ID:  0xA_W_ks!KsReleaseIrpOnCancelableQueue+22

BUCKET_ID:  0xA_W_ks!KsReleaseIrpOnCancelableQueue+22

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

Rabid Ferrets of DOOM!!!

Jun 6 2007, 07:04 PM

I was looking on new egg to see something about the RAM I bought and I noticed something - In the reviews people say you have to manually go into the BIOS and set the timing to 4-4-4-15 (what it's rated at or default or whatever the hell you call it for the timing.....) so could that be causing it? I didn't see the timing for my memory when I poked around the BIOS to change the voltage (which is back at its auto setting I reset the cmos defaults after the BSOD.) so if that's something to try how do I go about it?

Also I changed my pagefile size from 2048 to 3067. If the blue screen is being caused by something trying to access a memory address that's too high, then this *should* fix it, right?

Man I thought I was pretty adept at computer usage but this whole thing has shown me I don't know jack. XD

Rabid Ferrets of DOOM!!!

Jun 6 2007, 07:33 PM

Alright. Everything was on auto before but now my memory is forced on DDR800, 4-4-4-4-15. I left T1/T2 on auto but it chose T2. One other thing occured to me. I couldn't find it in my bios but I'm pretty sure at one point I saw it saying my graphics card was using 128 megs of shared RAM. If that's true perhaps that's causing the problem?

garmanma

Jun 6 2007, 07:55 PM

QUOTE(Rabid Ferrets of DOOM!!& @ Jun 6 2007, 08:33 PM)

According to Asus's site, that is what the motherboard supports, DDR800. I just did a quick look at the board, does this board also come with onboard graphics? Is it disabled?
Mark

Rabid Ferrets of DOOM!!!

Jun 6 2007, 08:13 PM

No onboard gfx.

Rabid Ferrets of DOOM!!!

Jun 6 2007, 08:16 PM

The only real lead I have at this point on what might be causing it is the repeating error in my event viewer -

"IRQARB: ACPI BIOS does not contain an IRQ for the device in PCI slot 15, function 0. Please contact your system vendor for technical assistance." I get that for slot 15, 14, 10, 11, 12, 13 in that order over and over again. Those are my 6 pci to pci bridge devices. In my bios IRQ resources is set to auto. Should I switch to manual and have it set to PCI for all of those? Or should I set it to reserved?

A buddy of mine from work gave me his copy of memtest so if I can't find a solution tonight I'll run it overnight.

Rabid Ferrets of DOOM!!!

Jun 6 2007, 09:14 PM

In case it helps here's a link to the new parts on newegg.

http://www.newegg.com/Product/Product.aspx...N82E16819103759
http://www.newegg.com/Product/Product.aspx...N82E16820227169
http://www.newegg.com/Product/Product.aspx...N82E16813131013

Also I checked the manual this ram is not on the qualified vendors list. But my systems have been like that more often than not never had a problem with it before.

Rabid Ferrets of DOOM!!!

Jun 6 2007, 09:19 PM

"[this board] Reads memory at 1.8V as default, suspect that memory that requires a voltage of 2V may not work in this board unless a lower voltage memory is used to get POST." My RAM is rated for 1.9V to 2.1V. The most recent BSOD was different from the others and I was at 1.95V. I do not know what it was at the first time though everything was on auto. Should I bump it up to 2 or 2.1? Not going to do something like that without hearing from you guys. XD

Rabid Ferrets of DOOM!!!

Jun 6 2007, 09:49 PM

Ok. Sometimes my games start crashing before a BSOD. Dunno if this'll help but here's the crash report from WoW's error reporter program thingy. XD

CODE

==============================================================================
World of WarCraft (build 6739)

Exe:      C:\Program Files\World of Warcraft\WoW.exe
Time:     Jun  6, 2007  8:43:34.750 PM
User:     Ferret
Computer: FERRET-PC
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal Exception
Program:    C:\Program Files\World of Warcraft\WoW.exe
Exception:    0xC0000005 (ACCESS_VIOLATION) at 001B:005513D4

The instruction at "0x005513D4" referenced memory at "0x00000000".
The memory could not be "written".

WoWBuild: 6739
------------------------------------------------------------------------------

----------------------------------------
    x86 Registers
----------------------------------------

EAX=1E8F23AC  EBX=00000000  ECX=00C75AE4  EDX=1F97304C  ESI=1E000000
EDI=1E8F22D8  EBP=0012FA88  ESP=0012FA7C  EIP=005513D4  FLG=00010246
CS =001B      DS =0023      ES =0023      SS =0023      FS =003B      GS =0000

----------------------------------------
    Stack Trace (Manual)
----------------------------------------

Address  Frame    Logical addr  Module

005513D4 0012FA88 0001:001503D4 C:\Program Files\World of Warcraft\WoW.exe
00631C79 0012FA98 0001:00230C79 C:\Program Files\World of Warcraft\WoW.exe
00652D77 0012FAEC 0001:00251D77 C:\Program Files\World of Warcraft\WoW.exe
00663BD1 0012FB00 0001:00262BD1 C:\Program Files\World of Warcraft\WoW.exe
00654399 0012FB28 0001:00253399 C:\Program Files\World of Warcraft\WoW.exe
00654C23 0012FB40 0001:00253C23 C:\Program Files\World of Warcraft\WoW.exe
00624635 0012FB6C 0001:00223635 C:\Program Files\World of Warcraft\WoW.exe
00497BFB 0012FC30 0001:00096BFB C:\Program Files\World of Warcraft\WoW.exe
00498166 0012FCBC 0001:00097166 C:\Program Files\World of Warcraft\WoW.exe
00423402 0012FD44 0001:00022402 C:\Program Files\World of Warcraft\WoW.exe
0042A0E7 0012FD60 0001:000290E7 C:\Program Files\World of Warcraft\WoW.exe
0042A5FC 0012FD7C 0001:000295FC C:\Program Files\World of Warcraft\WoW.exe
00438E0A 0012FE48 0001:00037E0A C:\Program Files\World of Warcraft\WoW.exe
0041EA0B 0012FE78 0001:0001DA0B C:\Program Files\World of Warcraft\WoW.exe
0041BEF9 0012FEEC 0001:0001AEF9 C:\Program Files\World of Warcraft\WoW.exe
0041D351 0012FF04 0001:0001C351 C:\Program Files\World of Warcraft\WoW.exe
0040569E 0012FFA0 0001:0000469E C:\Program Files\World of Warcraft\WoW.exe
761C3833 0012FFAC 0001:00042833 C:\Windows\system32\kernel32.dll
7765A9BD 0012FFEC 0001:000399BD C:\Windows\system32\ntdll.dll

----------------------------------------
    Stack Trace (Using DBGHELP.DLL)
----------------------------------------

005513D4 WoW.exe      <unknown symbol>+0 (0x1E8F22D8,0x41632A86,0x0012FAEC,0x00652D77)

----------------------------------------
    Loaded Modules
----------------------------------------

0x00160000 - 0x001C9000  C:\Program Files\World of Warcraft\DivxDecoder.dll
0x00400000 - 0x00CEB000  C:\Program Files\World of Warcraft\WoW.exe
0x04300000 - 0x047AA000  C:\Windows\system32\nvd3dum.dll
0x10000000 - 0x10090000  C:\Program Files\World of Warcraft\fmod.dll
0x11490000 - 0x115A8000  C:\Program Files\World of Warcraft\dbghelp.dll
0x16080000 - 0x16099000  C:\Program Files\Bonjour\mdnsNSP.dll
0x6C1B0000 - 0x6C27B000  C:\Windows\system32\OPENGL32.dll
0x6D350000 - 0x6D381000  C:\Windows\system32\TAPI32.dll
0x6D3E0000 - 0x6D427000  C:\Windows\system32\RASAPI32.dll
0x6EA10000 - 0x6EA72000  C:\Windows\system32\mscms.dll
0x6EE80000 - 0x6EEF1000  C:\Windows\system32\dsound.dll
0x6EF00000 - 0x6EFE6000  C:\Windows\system32\DDRAW.dll
0x6F140000 - 0x6F154000  C:\Windows\system32\rasman.dll
0x6F1B0000 - 0x6F1B6000  C:\Windows\system32\DCIMAN32.dll
0x6F740000 - 0x6F950000  C:\Windows\AppPatch\AcGenral.DLL
0x70D40000 - 0x70DC7000  C:\Windows\AppPatch\AcLayers.DLL
0x71070000 - 0x7108E000  C:\Windows\system32\ShimEng.dll
0x71670000 - 0x7182A000  C:\Windows\system32\d3d9.dll
0x71A20000 - 0x71A94000  C:\Windows\AppPatch\AcSpecfc.DLL
0x71C70000 - 0x71C76000  C:\Windows\system32\d3d8thk.dll
0x71CE0000 - 0x71D21000  C:\Windows\system32\WINSPOOL.DRV
0x71D90000 - 0x71D9C000  C:\Windows\system32\dwmapi.dll
0x722A0000 - 0x722B2000  C:\Windows\system32\pnrpnsp.dll
0x722E0000 - 0x722EF000  C:\Windows\system32\napinsp.dll
0x72510000 - 0x72518000  C:\Windows\System32\winrnr.dll
0x72540000 - 0x72546000  C:\Windows\system32\rasadhlp.dll
0x739E0000 - 0x739E7000  C:\Windows\system32\WSOCK32.dll
0x73B00000 - 0x73B86000  C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.6000.16386_none_87e0cb09378714f1\COMCTL32.dll
0x74340000 - 0x74347000  C:\Windows\system32\midimap.dll
0x74350000 - 0x743B6000  C:\Windows\System32\audioeng.dll
0x74450000 - 0x74471000  C:\Windows\System32\audioses.dll
0x74480000 - 0x74495000  C:\Windows\system32\MSACM32.dll
0x744B0000 - 0x744E0000  C:\Windows\system32\wdmaud.drv
0x748E0000 - 0x748E9000  C:\Windows\system32\msacm32.drv
0x748F0000 - 0x748FF000  C:\Windows\system32\NLAapi.dll
0x74930000 - 0x74957000  C:\Windows\system32\MMDevAPI.DLL
0x749A0000 - 0x749A4000  C:\Windows\system32\ksuser.dll
0x749C0000 - 0x749F8000  C:\Windows\system32\OLEACC.dll
0x74A00000 - 0x74A33000  C:\Windows\system32\WINMM.dll
0x74A40000 - 0x74A4C000  C:\Windows\system32\rtutils.dll
0x74C80000 - 0x74E14000  C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6000.16386_none_5d07289e07e1d100\comctl32.dll
0x74E30000 - 0x74E36000  C:\Windows\system32\sensapi.dll
0x74E80000 - 0x74EA3000  C:\Windows\system32\GLU32.dll
0x74F30000 - 0x74F3D000  C:\Windows\system32\sfc_os.dll
0x74F40000 - 0x74F45000  C:\Windows\system32\sfc.dll
0x74F80000 - 0x74FBF000  C:\Windows\system32\UxTheme.dll
0x75080000 - 0x750AD000  C:\Windows\system32\WINTRUST.dll
0x75140000 - 0x75147000  C:\Windows\system32\AVRT.dll
0x75210000 - 0x75216000  C:\Windows\System32\wshtcpip.dll
0x75230000 - 0x7524A000  C:\Windows\system32\POWRPROF.dll
0x75250000 - 0x75271000  C:\Windows\system32\NTMARTA.DLL
0x75300000 - 0x75338000  C:\Windows\system32\rsaenh.dll
0x75370000 - 0x753B5000  C:\Windows\system32\schannel.dll
0x75570000 - 0x755AB000  C:\Windows\system32\mswsock.dll
0x755D0000 - 0x755D6000  C:\Windows\System32\wship6.dll
0x755E0000 - 0x755E8000  C:\Windows\system32\VERSION.dll
0x75670000 - 0x75677000  C:\Windows\system32\credssp.dll
0x75730000 - 0x75750000  C:\Windows\system32\dhcpcsvc6.DLL
0x75750000 - 0x75757000  C:\Windows\system32\WINNSI.DLL
0x75760000 - 0x75795000  C:\Windows\system32\dhcpcsvc.DLL
0x757A0000 - 0x757B9000  C:\Windows\system32\IPHLPAPI.DLL
0x75840000 - 0x75931000  C:\Windows\system32\CRYPT32.dll
0x75940000 - 0x75954000  C:\Windows\system32\MPR.dll
0x75990000 - 0x759A2000  C:\Windows\system32\MSASN1.dll
0x759B0000 - 0x759C1000  C:\Windows\system32\SAMLIB.dll
0x759D0000 - 0x759FB000  C:\Windows\system32\DNSAPI.dll
0x75BE0000 - 0x75C4A000  C:\Windows\system32\NETAPI32.dll
0x75D10000 - 0x75D3C000  C:\Windows\system32\apphelp.dll
0x75D70000 - 0x75D84000  C:\Windows\system32\Secur32.dll
0x75D90000 - 0x75DAE000  C:\Windows\system32\USERENV.dll
0x75ED0000 - 0x75ED7000  C:\Windows\system32\PSAPI.DLL
0x75EE0000 - 0x76004000  C:\Windows\system32\urlmon.dll
0x76010000 - 0x7605B000  C:\Windows\system32\GDI32.dll
0x76060000 - 0x76063000  C:\Windows\system32\Normaliz.dll
0x76070000 - 0x760ED000  C:\Windows\system32\USP10.dll
0x760F0000 - 0x76174000  C:\Windows\system32\CLBCatQ.DLL
0x76180000 - 0x76258000  C:\Windows\system32\kernel32.dll
0x76260000 - 0x7628D000  C:\Windows\system32\WS2_32.dll
0x76290000 - 0x76418000  C:\Windows\system32\SETUPAPI.dll
0x76420000 - 0x764BE000  C:\Windows\system32\USER32.dll
0x764C0000 - 0x76515000  C:\Windows\system32\SHLWAPI.dll
0x76520000 - 0x7653E000  C:\Windows\system32\IMM32.dll
0x76540000 - 0x765CC000  C:\Windows\system32\OLEAUT32.dll
0x765D0000 - 0x76619000  C:\Windows\system32\WLDAP32.dll
0x76620000 - 0x766E3000  C:\Windows\system32\RPCRT4.dll
0x766F0000 - 0x7679A000  C:\Windows\system32\msvcrt.dll
0x767A0000 - 0x76867000  C:\Windows\system32\MSCTF.dll
0x76870000 - 0x768B5000  C:\Windows\system32\iertutil.dll
0x768C0000 - 0x7697F000  C:\Windows\system32\ADVAPI32.dll
0x76980000 - 0x769F4000  C:\Windows\system32\COMDLG32.dll
0x76A00000 - 0x76B44000  C:\Windows\system32\ole32.dll
0x76B50000 - 0x7761E000  C:\Windows\system32\SHELL32.dll
0x77620000 - 0x7773E000  C:\Windows\system32\ntdll.dll
0x77740000 - 0x77746000  C:\Windows\system32\NSI.dll
0x77750000 - 0x77779000  C:\Windows\system32\imagehlp.dll
0x77780000 - 0x77789000  C:\Windows\system32\LPK.DLL
0x77790000 - 0x7785F000  C:\Windows\system32\WININET.dll

----------------------------------------
    Memory Dump
----------------------------------------

Code: 16 bytes starting at (EIP = 005513D4)

005513D4: 89 33 8B 10  8B 70 04 89  72 04 C7 00  00 00 00 00  .3...p..r.......

Stack: 1024 bytes starting at (ESP = 0012FA7C)

* = addr                                         **                       *
0012FA70: 00 00 00 00  00 00 00 00  00 00 00 00  00 24 8F 1E  .............$..
0012FA80: 00 00 00 00  D8 22 8F 1E  98 FA 12 00  79 1C 63 00  ....."......y.c.
0012FA90: D8 22 8F 1E  86 2A 63 41  EC FA 12 00  77 2D 65 00  ."...*cA....w-e.
0012FAA0: D8 22 8F 1E  0E 00 00 00  64 E1 72 16  D8 22 8F 1E  ."......d.r.."..
0012FAB0: CC 54 42 20  00 55 85 C2  00 A0 A5 45  6B DD 92 41  .TB .U.....Ek..A
0012FAC0: 00 56 05 C2  AA AA A6 45  6B DD 92 41  00 00 48 C2  .V.....Ek..A..H.
0012FAD0: 55 25 A6 45  6B DD 92 41  80 55 69 C3  55 35 9B 45  U%.Ek..A.Ui.U5.E
0012FAE0: D9 5E 49 42  F0 23 8F 1E  13 C4 6B 43  00 FB 12 00  .^IB.#....kC....
0012FAF0: D1 3B 66 00  14 00 00 00  64 E1 72 16  68 26 64 1B  .;f.....d.r.h&d.
0012FB00: 28 FB 12 00  99 43 65 00  01 00 00 00  7A 01 00 00  (....Ce.....z...
0012FB10: 01 00 00 00  08 80 B1 16  1F 00 00 00  7A 01 00 00  ............z...
0012FB20: 22 00 00 00  17 00 00 00  40 FB 12 00  23 4C 65 00  ".......@...#Le.
0012FB30: 01 00 00 00  14 FC 12 00  CE CC 4C 3F  CE CC 4C 3F  ..........L?..L?
0012FB40: 6C FB 12 00  35 46 62 00  01 00 00 00  CC 00 00 00  l...5Fb.........
0012FB50: 14 FC 12 00  B5 AE 5C 3F  E1 F8 A6 C5  08 80 2A 0E  ......\?......*.
0012FB60: F0 FB 12 00  D7 32 5B 00  58 9C BB C4  30 FC 12 00  .....2[.X...0...
0012FB70: FB 7B 49 00  14 FC 12 00  D8 FB 12 00  E4 FB 12 00  .{I.............
0012FB80: 00 00 00 00  08 80 2A 0E  08 FF BD 10  D9 50 32 C4  ......*......P2.
0012FB90: FD 78 A6 45  6D D2 B0 41  2F 92 45 E3  A4 FC 12 00  .x.Em..A/.E.....
0012FBA0: 38 FD 12 00  08 C0 AB 02  24 76 60 02  00 00 00 00  8.......$v`.....
0012FBB0: 00 00 00 00  98 FB 12 00  90 FF 12 00  02 00 00 00  ................
0012FBC0: B0 0F FB 23  DC FB 12 00  08 6D 67 71  02 00 00 00  ...#.....mgq....
0012FBD0: B8 FC 12 00  20 76 60 02  D5 94 32 C4  42 9A A6 45  .... v`...2.B..E
0012FBE0: 77 78 CD 41  D9 50 32 C4  FD 78 A6 45  6D D2 B0 41  wx.A.P2..x.Em..A
0012FBF0: 1D 6E 7D 3E  33 09 78 BF  00 00 00 00  1D 6E FD 3E  .n}>3.x......n.>
0012FC00: 33 09 F8 BF  00 00 00 00  87 70 32 C4  7E 88 A6 45  3........p2.~..E
0012FC10: C1 8D CF 41  8A A3 32 C4  74 A1 A6 45  06 71 D0 41  ...A..2.t..E.q.A
0012FC20: 6D D2 B0 41  08 80 B1 16  96 43 8B 3C  A0 DA 75 40  m..A.....C.<..u@
0012FC30: BC FC 12 00  66 81 49 00  24 3A 1B 0E  00 00 80 3F  ....f.I.$:.....?
0012FC40: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0012FC50: 00 00 80 3F  00 00 00 00  00 00 00 00  00 00 00 00  ...?............
0012FC60: 00 00 00 00  00 00 80 3F  00 00 00 00  05 E7 C7 BE  .......?........
0012FC70: 04 EC 9F BE  00 00 00 00  00 00 80 3F  84 EB 23 40  ...........?..#@
0012FC80: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0012FC90: 64 E6 4C 40  00 00 00 00  00 00 00 00  00 00 00 80  d.L@............
0012FCA0: 00 00 00 80  6F 12 03 BB  00 00 00 00  04 EC 9F B9  ....o...........
0012FCB0: 04 EC 9F 39  00 00 00 80  00 00 80 3F  44 FD 12 00  ...9.......?D...
0012FCC0: 02 34 42 00  08 80 2A 0E  00 00 00 00  08 3A 1B 0E  .4B...*......:..
0012FCD0: 24 3A 1B 0E  00 00 00 00  00 00 00 00  00 00 00 00  $:..............
0012FCE0: 00 00 80 3F  00 00 00 00  05 E7 C7 BE  04 EC 9F BE  ...?............
0012FCF0: 00 00 00 00  00 00 80 3F  84 EB 23 40  00 00 00 00  .......?..#@....
0012FD00: 00 00 00 00  00 00 00 00  00 00 00 00  64 E6 4C 40  ............d.L@
0012FD10: 00 00 00 00  00 00 00 00  00 00 00 80  00 00 00 80  ................
0012FD20: 6F 12 03 BB  00 00 00 00  04 EC 9F B9  04 EC 9F 39  o..............9
0012FD30: 00 00 00 80  00 00 80 3F  04 EC 9F BE  00 00 00 00  .......?........
0012FD40: 68 D9 83 E6  60 FD 12 00  E7 A0 42 00  24 3A 1B 0E  h...`.....B.$:..
0012FD50: E8 2C 19 0E  09 00 00 00  08 20 19 0E  E8 83 A7 10  .,....... ......
0012FD60: 7C FD 12 00  FC A5 42 00  88 6A 03 03  20 76 A7 10  |.....B..j.. v..
0012FD70: 08 76 A7 10  00 00 00 00  00 00 00 00  48 FE 12 00  .v..........H...
0012FD80: 0A 8E 43 00  00 00 00 00  10 76 A7 10  20 76 A7 10  ..C......v.. v..
0012FD90: 96 43 8B 3C  30 8D A6 02  08 8C A6 02  E8 90 A6 02  .C.<0...........
0012FDA0: FF 03 99 3E  00 00 00 80  00 00 80 3F  A0 8C A6 02  ...>.......?....
0012FDB0: C8 BE 20 0C  08 8C A6 02  10 FE 12 00  A0 24 01 10  .. ..........$..
0012FDC0: D8 BB 20 0C  E0 DC 00 10  D8 BB 20 0C  40 00 00 00  .. ....... .@...
0012FDD0: 42 88 A6 C5  C1 8D CF 41  1A 77 32 C4  00 00 00 00  B......A.w2.....
0012FDE0: 00 00 00 00  00 00 00 00  D6 4C 74 3F  00 00 00 00  .........Lt?....
0012FDF0: FF 03 99 3E  00 00 00 80  00 00 80 3F  00 00 00 00  ...>.......?....
0012FE00: 00 00 80 3F  00 00 80 40  00 00 80 3F  A0 8C A6 02  ...?...@...?....
0012FE10: 34 FE 12 00  34 FE 12 00  F5 9F 6E 00  1A 77 32 C4  4...4.....n..w2.
0012FE20: 00 00 00 00  00 00 00 00  00 00 80 3F  00 00 80 3F  ...........?...?
0012FE30: 00 00 00 00  00 00 80 3F  00 00 00 00  00 00 80 3F  .......?.......?
0012FE40: 00 00 00 00  00 00 80 3F  78 FE 12 00  0B EA 41 00  .......?x.....A.
0012FE50: 00 00 00 00  00 00 00 00  08 8C A6 02  00 00 00 00  ................
0012FE60: E8 90 A6 02  35 8D A6 02  18 8C A6 02  00 00 00 00  ....5...........
0012FE70: 08 8C A6 02  01 00 00 00  EC FE 12 00  F9 BE 41 00  ..............A.

------------------------------------------------------------------------------

======================================================================
Hardware/Driver Information:
Processor:              0x0
Page Size:              4096
Min App Address:        0x10000
Max App Address:        0x7ffeffff
Processor Mask:         0x3
Number of Processors:   2
Processor Type:         586
Allocation Granularity: 65536
Processor Level:        15
Processor Revision:     17154

Percent memory used:    59
Total physical memory:  2145255424
Free Memory:            868548608
Page file:              -1
Total virtual memory:   2147352576

Rabid Ferrets of DOOM!!!

Jun 6 2007, 10:17 PM

Aaaaaand BSOD. But hey guess what. THIS TIME I BOOTED INTO ONE, TOO! I don't have a dmp for the first one but it was a DRIVER_IRQL_NOT_LESS_OR_EQUAL code 0xd1 problem from USBPORT.SYS. Here's the dmp for the one I booted into.

CODE

......Unable to enumerate user-mode unloaded modules, NTSTATUS 0xC0000147
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {deadc0d6, 2, 0, 8c10eb6e}

Cant get more than that out of it.

CODE

Unable to verify checksum for fmod.dll
Symbol file not found. Defaulted to export symbols for fmod.dll

The program freezes if I try to go to symbol path.

Rabid Ferrets of DOOM!!!

Jun 6 2007, 10:27 PM

If I get another BSOD I'm putting my RAM voltage a 2.05. Just curious, though, when I switch my jumperfree config to manual, it has CPU frequency at 2.00 should I be changing that to 2.6? I'm not sure if that's different than the CPUs rated frequency when I order it or not? When I manually put my RAM frequency at 1.95 my computer did seem to run awefully slow. I think if I change the voltage manually I'm going to put it at 2.6 unless I hear differently. In the mean time the only change I have made is switched the RAM to force T2 I'm sure it's there anyway but I read the board won't boot at T1 so can't hurt.

I'm also going to run Memtest over night tonight. I think I already said that though. XD

Rabid Ferrets of DOOM!!!

Jun 6 2007, 10:29 PM

Here we go got a bit more info.

God the last like 10 posts have been me anybody out there?

CODE

Rabid Ferrets of DOOM!!!

Jun 6 2007, 10:32 PM

Ok. I am currently installing this update from microsoft. Looks like it may fix it.
http://support.microsoft.com/kb/925528

Rabid Ferrets of DOOM!!!

Jun 6 2007, 10:44 PM

Ok. This is going to sound crazy, but I honestly think it's fixed. Here's why. I've mentioned a few times about the graphical glitches on my screen both 2d and 3d (which now that I think about it I don't think I got them or at least not very many of them until I upgraded to vista on my old parts.) Since I got these new parts, I have gotten no 3d glitches and the only time I was getting the spots and lines 2d was just before a BSOD if I remember correctly. However, there was one place I always got them. 2 random dots when it showed the mobo logo. I didn't get them this time. So as crazy as it may sound, I think it's a sign that it has been fixed. (Or I should say it was fixed because I SOOOOOO just jinxed the hell out of it.)

Rabid Ferrets of DOOM!!!

Jun 6 2007, 11:35 PM

Ok. It wasn't nessecarily a bsod, but it locked up. I was expecting a bsod but after about 30 secs I just hard reset. I'll see if it happens again.

Rabid Ferrets of DOOM!!!

Jun 7 2007, 01:50 AM

Didn't get any BSODs tonight after the windows patch. I'll run memtest tonight and I'll be gaming all day tomorrow.

DaChew

Jun 7 2007, 04:09 AM

sounds like a marginal power supply, possible overheating and probably a bad load of the OS and drivers

Rabid Ferrets of DOOM!!!

Jun 7 2007, 10:45 AM

No it's not a heat problem - if it was heating then it'd just turn right off not BSOD. Have you read all of the other posts because nothing you said is really all that helpful.

GRINLER! SNEAKY! STEVE! GARMANMA! SOMEONE COME BACK TO ME!!!!!

DaChew

Jun 7 2007, 11:09 AM

QUOTE(Rabid Ferrets of DOOM!!& @ Jun 7 2007, 11:45 AM)

No it's not a heat problem - if it was heating then it'd just turn right off not BSOD. Have you read all of the other posts because nothing you said is really all that helpful.

GRINLER! SNEAKY! STEVE! GARMANMA! SOMEONE COME BACK TO ME!!!!!

I spent quite a while on all three pages of this, actually more time than the others combined(probably)

no name power supply

you supplied no evidence of temps

you are all over the board with your fixes

little knowledge of bios settings

wonder why they haven't come back, probably same reason I won't

Rabid Ferrets of DOOM!!!

Jun 7 2007, 11:34 AM

Sorry I'm cranky in the morning. XD Thanks for your suggestion. What do you mean by marginal power supply? I know my temps are fine I already checked that. Can you be more specific about what you mean by bad load of OS and Drivers?

jwinathome

Jun 7 2007, 11:37 AM

Could you compile your problem into one summarized post?

Rabid Ferrets of DOOM!!!

Jun 7 2007, 12:06 PM

My problem is I am getting BSODs when I am gaming. (This might be fixed it's difficult to test so I'm still looking for suggestions because my computer is acting suspicious.) The error is DRIVER_IRQL_NOT_LESS_OR_EQUAL. 0xD1. I've gotten a different error once or twice but it's basically a different type of the same error. The stop error says it's caused by USBPORT.SYS. Once after a bsod, my bus enumerators and my network controllers had no drivers on them. Only one of the network controllers is currently working. In addition, if I look in the event log, I get the following error "IRQARB: ACPI BIOS does not contain an IRQ for the device in PCI slot 15, function 0. Please contact your system vendor for technical assistance." for slots 10-15 every couple of hours. In device manager devices 10-15 are all PCI-to-PCI bridge devices.

DaChew

Jun 7 2007, 12:10 PM

did you use the mobo cd drivers when you first installed or the newest ones at the web site?

jwinathome

Jun 7 2007, 12:13 PM

What kind of video card do you have, and what driver are you using for it?

Also, I think you can avoid this problem with a BIOS update. What kind of motherboard do you have?

Rabid Ferrets of DOOM!!!

Jun 7 2007, 12:19 PM

I used the vista driver CD first so I could connect to the internet and then I downloaded the new ones from nVidia.

Also I ran memtest all night no errors there.

Rabid Ferrets of DOOM!!!

Jun 7 2007, 12:23 PM

Oh, I don't know if this is of any signifigance, but my comp randomly shut off (not because of heat I double checked that.) I think it's just because the power cable is somewhat loose and I didn't have it in the way I normally do to keep it from shutting off that way. Just figured I'd let you know in case it does matter.

Rabid Ferrets of DOOM!!!

Jun 7 2007, 12:24 PM

MSI nVidia geForce 7900 GT. Don't remember the driver version it's the most recent one from nVidia, though. My mobo is M2N-SLI Deluxe that's the first thing I thought of but my BIOS are up to date as well.

Rabid Ferrets of DOOM!!!

Jun 7 2007, 12:51 PM

Have I been given up on?

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.