Back to back to back BSOD crashes

For the past week my laptop has been getting a BSOD. About once a day, sometimes 2 or 3 times. With little variation the message has been IRQL_NOT_EQUAL_OR_LESS. It also says something about usbport.sys. Except the only thing that I have plugged into my USB is a mouse reciever.

Just now, I got 5 back to back BSOD crashes with either the IRQL message or "BAD_POOL_CALLER" or "BUG_CODE_USB". I think once or twice I got a different kind of message.

This has been happening for about a week or so and I didn't install any new drivers or anything around that time. It, for the most part, just came out of the blue.

Please please help.

I have a Sager NP2090 running a 32 bit Vista. T7300 processor and an 8600M GT video card. I just updated the driver for the video card. IIRC it was driver 180.84.

EDIT:

Something I forgot to add. My CPU temperature has been ok. Nothing too high but definitely not cool. Idle at around 50-55C and load at 65C. I know it's a bit high but could it really cause that many problems? I heard that CPUs should be stable up to 90C

 

Try these links

http://www.experts-exchange.com/Hardware/Q_20837201.html
http://www.ntcompatible.com/DRIVER_IRQL_NOT_LESS_OR_EQUAL_t32503.html
http://reviews.cnet.com/5208-6127-0.html?forumID=9&threadID=49375&messageID=587560
http://forums.techguy.org/t383258.html

 

Run a memory test.

 

Oh, well, there you go. If the memory tests out ok, put the old driver back.

EDIT: Oh I get it, you updated after you started getting crashes, right?

ok, then see if there's a newer BIOS for your machine. Also make sure your OS is up-to-date.

Also: See this thread for an example of how to debug BSODs: http://forum.notebookreview.com/showthread.php?t=256724
You can post debugger output here for review.

Another thing to try is going to Device Manager and disabling unused devices (modem, firewire, smartcard, etc.) You can easily re-enable a device if you ever actually need it.

 

Can you clarify what you mean by memory test?

And yeah, I updated the video card after all the crashes started happening. They still happened though.

Ok, here's the last minidump I got.

EDIT 2:

I think I got it. Again, this is from the last crash.

Code:

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


Loading Dump File [C:\Windows\Minidump\Mini123108-06.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x82400000 PsLoadedModuleList = 0x8250d930
Debug session time: Wed Dec 31 20:43:22.110 2008 (GMT-8)
System Uptime: 0 days 0:01:28.062
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, 8873e7ec}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_DereferenceDeviceHandle+a1 )

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

Is that right? Because the minidump of the guy that posted on that forum is a lot longer than mine.

 

Ok just crashed again. This time while I was syncing my ipod. It crashed twice actually.

Code:

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


Loading Dump File [C:\Windows\Minidump\Mini010109-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x82418000 PsLoadedModuleList = 0x82525930
Debug session time: Thu Jan  1 01:11:59.748 2009 (GMT-8)
System Uptime: 0 days 0:03:30.720
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {6, 887470ca, 48766544, 0}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_AssertSig+20 )

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

 

you see what windows thinks is the problem ?

the chipset drivers contain the installation fro the usb ports. maybe you wanna try updating to a newer chipset driver.

 

Even if you have the latest chipset drivers, you would be well advised to completely uninstall the drivers and then reinstall them. Also, you should note which USB port you have your iPod or your wireless mouse transceiver plugged into, because devices such as those can occasionally draw more current than the USB protocol allows, and because of the "lazy" way almost every OEM/ODM wires the hot lead to the USB ports (i.e., they link them serially instead of providing each one with a separate hot lead), if a device like that is plugged into any USB port other than the one that is directly connected to the hot lead, it may trigger a shut-down on the USB port itself, which can cause the system to crash. Lastly, do not leave the iPod plugged in when you boot the system up, because that greatly increases the chance of a crash during the boot process.

 

I'll try that, the reinstalling the drivers thing. Which device is this again?

I haven't had a crash today yet. So that's nice.

How do I find out which USB port is the one that is connected to the hot lead? And yeah, i don't leave my ipod in it. That last crash was actually the first one that happened with my ipod plugged in.