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.

Photo

New Parts - New Bsods


  • Please log in to reply
96 replies to this topic

#1 Rabid Ferrets of DOOM!!!

Rabid Ferrets of DOOM!!!

  • Members
  • 74 posts
  • OFFLINE
  •  
  • Local time:01:26 PM

Posted 05 June 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!

Edited by Rabid Ferrets of DOOM!!!, 05 June 2007 - 12:15 PM.


BC AdBot (Login to Remove)

 


#2 Rabid Ferrets of DOOM!!!

Rabid Ferrets of DOOM!!!
  • Topic Starter

  • Members
  • 74 posts
  • OFFLINE
  •  
  • Local time:01:26 PM

Posted 05 June 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:
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:
Encrypted volume check: Volume information on J: cannot be read.

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

10000:
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:
Windows Servicing failed to complete the process of changing update 936824-5_RTM_PACKAGE from package KB936824(Update) into Staging(Staging) state
And:
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:
Windows Servicing failed to complete the process of setting package KB936824 (Update) into Staging(Staging) state

And then another set of:
Windows Servicing failed to complete the process of changing update 929685-1_RTM_GDR from package KB929685(Update) into Staging(Staging) state
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:
Windows Servicing failed to complete the process of setting package KB929685 (Update) into Staging(Staging) state

Now 10:
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...
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

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.

Edited by Rabid Ferrets of DOOM!!!, 05 June 2007 - 12:55 PM.


#3 stevealmighty

stevealmighty

    Bleepin' WormBreath


  • Members
  • 2,629 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Upstate NY
  • Local time:02:26 PM

Posted 05 June 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)?
War produces veterans, wounded both physically and mentally. They have sacrificed for us.....and it is now our job to help these veterans, as they have already helped us in ways we will never know, in ways that we cannot fathom, and in ways that we take granted every day.
Posted Image

#4 Rabid Ferrets of DOOM!!!

Rabid Ferrets of DOOM!!!
  • Topic Starter

  • Members
  • 74 posts
  • OFFLINE
  •  
  • Local time:01:26 PM

Posted 05 June 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.

#5 Rabid Ferrets of DOOM!!!

Rabid Ferrets of DOOM!!!
  • Topic Starter

  • Members
  • 74 posts
  • OFFLINE
  •  
  • Local time:01:26 PM

Posted 05 June 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

#6 Rabid Ferrets of DOOM!!!

Rabid Ferrets of DOOM!!!
  • Topic Starter

  • Members
  • 74 posts
  • OFFLINE
  •  
  • Local time:01:26 PM

Posted 05 June 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.

#7 Rabid Ferrets of DOOM!!!

Rabid Ferrets of DOOM!!!
  • Topic Starter

  • Members
  • 74 posts
  • OFFLINE
  •  
  • Local time:01:26 PM

Posted 05 June 2007 - 01:23 PM

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

*******************************************************************************
*																			 *
*						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
---------


#8 Rabid Ferrets of DOOM!!!

Rabid Ferrets of DOOM!!!
  • Topic Starter

  • Members
  • 74 posts
  • OFFLINE
  •  
  • Local time:01:26 PM

Posted 05 June 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.
*******************************************************************************
*																			 *
*						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
---------

Edited by Rabid Ferrets of DOOM!!!, 05 June 2007 - 01:28 PM.


#9 Rabid Ferrets of DOOM!!!

Rabid Ferrets of DOOM!!!
  • Topic Starter

  • Members
  • 74 posts
  • OFFLINE
  •  
  • Local time:01:26 PM

Posted 05 June 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...?

*******************************************************************************
*																			 *
*						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
---------


#10 Rabid Ferrets of DOOM!!!

Rabid Ferrets of DOOM!!!
  • Topic Starter

  • Members
  • 74 posts
  • OFFLINE
  •  
  • Local time:01:26 PM

Posted 05 June 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

Edited by Rabid Ferrets of DOOM!!!, 05 June 2007 - 01:42 PM.


#11 stevealmighty

stevealmighty

    Bleepin' WormBreath


  • Members
  • 2,629 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Upstate NY
  • Local time:02:26 PM

Posted 05 June 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! :thumbsup: If not, then we'll look more into your IRQ stuff (which is not one of my strong points!).
War produces veterans, wounded both physically and mentally. They have sacrificed for us.....and it is now our job to help these veterans, as they have already helped us in ways we will never know, in ways that we cannot fathom, and in ways that we take granted every day.
Posted Image

#12 Rabid Ferrets of DOOM!!!

Rabid Ferrets of DOOM!!!
  • Topic Starter

  • Members
  • 74 posts
  • OFFLINE
  •  
  • Local time:01:26 PM

Posted 05 June 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.

Edited by Rabid Ferrets of DOOM!!!, 05 June 2007 - 01:47 PM.


#13 Grinler

Grinler

    Lawrence Abrams


  • Admin
  • 43,665 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:02:26 PM

Posted 05 June 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.

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.


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?

#14 Rabid Ferrets of DOOM!!!

Rabid Ferrets of DOOM!!!
  • Topic Starter

  • Members
  • 74 posts
  • OFFLINE
  •  
  • Local time:01:26 PM

Posted 05 June 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

#15 Grinler

Grinler

    Lawrence Abrams


  • Admin
  • 43,665 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:02:26 PM

Posted 05 June 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.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users