BSOD - Windows 7 x86

[Jordyi]

Have tried multiple things with this BSOD and have already had some advice on how to resolve the issue which has proved null and void unfortunatly as I am still recieving persistant BSODs of all different varietys.

Had this issue for quite some time now rendering my pc somewhat useless. Sometimes the BSOD starts before I even get the chance to log on, some times I can use the computer for a good 15 minutes before it BSODs. Also, numerous numbers of different BSODs happening. The information I know are as follows:

· OS - Windows 7 x86 (32-bit)
· Windows Vista x86 (32-Bit)
· Full retail version
· System Age: About 2 years
· Recently installed Windows 7 about a week ago but had issues with BSODs before installation.
· Processor: Intel Quad Core Processor 4 x 2.2GHz
· Video Card: Nvidea 8800GT

Most recent minidumps including Performance monitor report can be found attached.

Thanks in advance.

 

[CarlTR6]

Hi Jordyi; I am sorry you are having problems. I will take a look.

I looked at six of your dumps and all but one are Driver Verifier Enabled dumps. For the time being, turn off Driver Verifier. Most of the dumps are pointing to Windows system drivers or hardware. One points to nvlddmkm.sys. Two dumps implicate nvstor32.sys.

The error code of the non Driver Verifier enabled dump is D1, DRIVER_IRQL_NOT_LESS_OR_EQUAL - usually caused by a device driver.

Kernel base = 0x8224f000 PsLoadedModuleList = 0x82397810
Debug session time: Tue Sep  7 18:05:28.508 2010 (GMT-4)
System Uptime: 0 days 0:11:28.008
Loading Kernel Symbols
...............................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {854afb, 2, 0, 8d897b81}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_ProcessScatterGatherList+25f )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 00854afb, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8d897b81, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 823b7718
Unable to read MiSystemVaType memory at 82397160
 00854afb 

CURRENT_IRQL:  2

FAULTING_IP: 
USBPORT!USBPORT_Core_ProcessScatterGatherList+25f
8d897b81 8b00            mov     eax,dword ptr [eax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  82375ab8 -- (.trap 0xffffffff82375ab8)
ErrCode = 00000000
eax=00854afb ebx=00000000 ecx=854afb18 edx=00000000 esi=854af870 edi=854afaf0
eip=8d897b81 esp=82375b2c ebp=82375b7d 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_ProcessScatterGatherList+0x25f:
8d897b81 8b00            mov     eax,dword ptr [eax]  ds:0023:00854afb=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8d897b81 to 8229582b

STACK_TEXT:  
82375ab8 8d897b81 badb0d00 00000000 8221dba9 nt!KiTrap0E+0x2cf
82375b7d 288221ca 00849500 08000000 f0858847 USBPORT!USBPORT_Core_ProcessScatterGatherList+0x25f
WARNING: Frame IP not in any known module. Following frames may be wrong.
82375b91 308228f3 70854afb 01854af8 01000000 0x288221ca
00000000 00000000 00000000 00000000 00000000 0x308228f3


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_Core_ProcessScatterGatherList+25f
8d897b81 8b00            mov     eax,dword ptr [eax]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  USBPORT!USBPORT_Core_ProcessScatterGatherList+25f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc871

FAILURE_BUCKET_ID:  0xD1_USBPORT!USBPORT_Core_ProcessScatterGatherList+25f

BUCKET_ID:  0xD1_USBPORT!USBPORT_Core_ProcessScatterGatherList+25f

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

I took a look at your drivers and found this very obsolete driver. Out of date drivers cause conflicts , memory corruption, and crashes. Generally, Win 7 does not like old drivers.

nvstor32.sys Wed Oct 31 15:21:57 2007 - nVidia Storage Driver (nForce chipset driver) Drivers - Download NVIDIA Drivers.

Turn off Driver Verifier, update this driver, reboot and run your system. Let's see how it runs. If you get another BSOD, upload it and we will take the next step. Do let us know when you have updated the driver.

 

[Jordyi]

Thanks for the very quick response in advance.

 

[CarlTR6]

You are welcome. I have finished for now. Refresh your page. I cannot guarantee that 2007 driver was causing the crashes; but I can assure you it is not contributing to the stability of your system. Let's hope the fix is that simple. If not, we will test your RAM. When you get BSOD's during booting or shortly after booting, it is an indication of a hardware/hardware related problem.

 

[Jordyi]

Ah. The person who helped me before also said that I should update this driver and I thought I had done so but it seems that I havn't.

When I go on the Nvidea website I updated the driver for my Nvidea 8800GT video/graphics card. Is there perhaps another item I need to update other than this that is related to this driver?

Edit: Just got a BSOD stating 'Memory_Management' being the cause. Havn't seen this one before. Not sure if that helps you at all but just thought i'd say.

 

[CarlTR6]

Go to the NVidia website and do a search for nvstor32.sys. There is an updated version of this driver. If your computer is a laptop, try the laptop manufacturer's website first since this is a chipset driver.

Obviously, I haven't seen the latest dump; but faulty drivers can cause memory corruption, thus the memory management error. Once you update this driver, if you still get BSOD's, the next step will be to test your RAM.

It will help us help you if you will fill out your system specs. Go to your User CP at the top of the page, look in the left column and click on Edit system specs. Filling in your specs will help us help you.

You can make this easier by downloading Speccy.

 

[Jordyi]

A search for the specific driver isn't showing any results for me on the website. ):

Perhaps your having more luck than myself, or there is another way to obtain this driver?

System Specs attached.

Edit: Ahhh, I see now. My motherboard is an Nvidea chipset. Ahhh. So I need to update the motherboard drivers?

Edit2: Seems as though the file for my chipset also works with my graphics card and wasn't anything new. The driver is still somewhat not updated. ):

 

[CarlTR6]

I will need the name and model of your motherboard and your chipset. See my post above for filling out your specs. I am signing off for the night; but will try to find the driver or a workaround tomorrow. I found several workarounds through Google; but I don't have your hardware information. Don't give up; we will find a solution.

Edited: Yes, you need to update the chipset drivers. Good job!! I noticed that driver is not updated with the graphics card. I will find you a solution tomorrow.

 

[Jordyi]

Alright. Even though I don't own any nforce specific devices, I downloaded and installed an nforce package and updated versions of nvstor32.sys are now on my computer.

They've created a new folder in C:/NVIDEA/... though and not in C:/Windows/Drivers/... where the other nvstor32.sys is. Will this still be okay?

Thanks for all your help so far, and I can wait for a reply don't worry.

 

[Jordyi]

Still getting a few BSODs but luckily not as many varieties as before as of last night.

A few Memory_Management BSODs and one Driver_IRQL_Not_Less_Or_Equal Bsod.

Most recent BSODs are attached to this post.

 

[Jordyi]

I just went a good 2 hours with a fully working no BSODing computer and then one BSOD and about 6 more to follow it. Will upload most recent dump files shortly.

Edit: (5) contains most recent flurry of BSODs after working fine for several hours.

 

[CarlTR6]

That is a whole lot of dumps. I looked at 11 of them. Of that 11, 9 were pointing to memory corruption. Your nvstor32.sys driver is updated. Good job. It still puzzles me why it is being referenced in some of the dumps. You had a variety of error codes which is indicative of hardware problems.

Our next step is to test your RAM. This will not be a fast process. Follow the instructions in the tutorial liked below and post back with the results. Errors will show on your screen in red.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[Jordyi]

Yeah, sorry about the large amount there, haha. Just thought i'd post up what I had so you could check whatever you'd like.

I was actually going to do a memory check today whilst I was waiting but when initilizing the program I got an error message saying something along the lines of it couldn't run and it was perhaps of a faulty installation file. I tried re-installing it twice and got the same message each time. Does the USB which I use this on need to be of a certain size for it to work?

Thanks again for your help.

Edit: Tried again and the exact message is: 'Error decrompressing data! Corrupted Installer?'

Going to try again without formatting the USB (after googling and finding out that the error message is related to formatting and not the program itself) before I go to bed tonight and leave it on overnight. Thanks again for all the help.

 

[CarlTR6]

If you can't run it via USB, try burning it to a CD.

 

[Jordyi]

Ran the Memtest with 8 passes over 10 hours last night and did not recieve any errors, so i'm really not sure what the problem is now. ):

Any idea what it may be?

Thanks.

 

[CarlTR6]

Ran the Memtest with 8 passes over 10 hours last night and did not recieve any errors, so i'm really not sure what the problem is now. ):

Any idea what it may be?

Thanks.

That means you RAM is probably OK which is good news. I would like for you to monitor your temps while you are using your system[FONT=&quot] with [/FONT]Speedfan. Temperatures going too high can cause crashes. Post back with your highest temp readings; you can do a screen snip if you like and upload it. And upload any new dumps you get.

 

[Jordyi]

Thought the issue had somewhat resolved itself after not causing any BSODs at all on a few start-ups. This error seems to come and go whatever it is. I'm currently using my desktop without and issue, but when trying to turn it on around 5 hours ago, the usual series of BSODs again and again stopped me from doing what I was doing, or even logging in.

Speedfan test for resting temprature can be found here: http://img683.imageshack.us/img683/6017/speedfantest.png

Speedfan test once in a high graphiced game and so at higher running temprature can be found here: http://img823.imageshack.us/img823/679/speedfantesthigh.png

This was after leaving the game open for 2 minutes, it is continuing to rise past this level currently though. I will leave it open and see to what extreme it gets to.

Have also attached recent BSODs from today.

Thanks again for the help.

 

[CarlTR6]

Do you know what the maximum temps are for your GFX card and your CPU? You want to make sure you are not above the max. Your GFX temp is about the same as mine. Your CPU temp is about 10 degrees warmer than mine. However, I don't think heat, at this point, is causing the crashes.

Idling temps

View attachment 96967

High temps

View attachment 96968

Crashing during the booting process indicates a hardware/driver problem. I looked at four of your recent dumps; all indicate hardware/hardware related problems.

Error code D1, DRIVER_IRQL_NOT_LESS_OR_EQUAL - usually caused by a device driver.

Error code A, IRQL_NOT_LESS_OR_EQUAL - usual causes are Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Error code 8E (two of these), KERNEL_MODE_EXCEPTION_NOT_HANDLED - Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory

The dumps are still pointing to memory corruption and do give us a specific cause. All of your drivers appear to be up to date.

Let's test your CPU. Monitor your temps during this test. Follow the instructions in Jonathan's excellent tutorial:
http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html. Post back with the results.

Next, test your graphics card using this excellent tutorial, also by Jonathan:
http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html. Post back with the results.

After running these tests, if no problems are found are found, eliminate some of your startup programs. Run MSCONFIG, click on the Startup tab and uncheck the following programs:

Adobe Reader Speed Launcher
CarboniteSetupLite
Google Desktop Search
SmpcSys - Set Up My PC" utility supplied with some Packard Bell computers
SunJavaUpdateSched
tsnpstd3 - tsnpstd3 Microsoft or tsnp2std Microsoft belongs to the software tsnpstd3.exe or tsnp2std by SONIX. This appears to be associated with your webcam; maybe the tray icon?
toolbar_eula_launcher
VirtualCloneDrive

Let's see if this impacts the BSOD's during booting. If it does, you can put one back at a time until you find the one that may be conflicting. None of these appear to be necessary for running Windows. If they are things you don't use frequently, leave them unchecked.

 

[Jordyi]

I can't seem to run furmark for long enough at the moment without another bsod ):

Also, with prime95, does it need to be left running for 12 hours or is that just a guideline?

Edit: Computer decided to stop bsoding for a while and am now running furmark How long should I leave it running?

 

[CarlTR6]

Run it until the temp levels out.

The 12 hours is a guideline; but it needs to be followed. Sometimes problems don't show up for a while.