BSOD - No_More_IRP_Stack_Locations

Hi G,
You can burn the SATA drivers to CD and have them available from there.

You may also want to try uninstalling or upgrading the drivers for your front side USB ports.
If you uninstall them, they should re-install at boot up.

Good Luck,
Vic

Cheers Vic

Unfortunately, unistalling the USB drivers in Device Manager and then letting XP reinstall them at boot up doesn't seem to work as I tried that 3 times last night.

G

Rats - so much for that.
Let me do some looking for similiar problems.
Vic

I found this here on E-E.
Look at both the 'accepted answer' and the post by LeeTutor.
Lee is the editor here and the site he posts has been a great help to me with other problems.

https://www.experts-exchange.com/questions/21535745/BSOD-No-More-IRP-Stack-Locations.html?query=No_More_IRP_Stack_Locations&clearTAFilter=true

Vic

Cheers again Vic

I had a shufty through the link you provided and unfortunately doesn't seem to fit with my issue as the PC will boot - it only BSODs when inserting a pen drive or memory card into the card reader/front USB ports. If I disable the USBdrivers in Windows then this means that the BSOD wont occur as Windows wont register the plugged in device.

I shall try burning the SATA drivers to a CD, but that means swapping the CD's over after XP has loaded the blue installation screens as this PC only has one CD drive. Will that cause any problems?

I did see a MS Knowledge Base page that referred to increasing the IRP stack number in the Registry, but I'm not sure if that will work for XP.

G

G,
This really appears to be a driver conflict of some kind.
Do you know if any drivers (Video?) have been installed or updated lately?
If the machine has on-board video plus a separate Video card, have you tried removing the video card and just using the on-board?


If you go here: http://aumha.org/win5/kbestop.htm
and search for the words: IRP_STACK
It appears to address what you are talking about.

Thanks Vic

I can't see it being a RAM issue as I've just installed 512MB of brand new Crucial Technology RAM, bought using their mobo selector. Also, the link through to the MSDN article seems to suggest that it is an issue with newly installed drivers for new hardware for Win2000. Not sure if that means it is a similar issue with XP, although both OS's are based around NT.

I think I might try the IRP stack registry fix I spotted elsewhere on the MS Knowledge base, but I wont hold my breath.

Why MS feels it is necessary to write such god awful and totally unhelpful error codes is beyond me. It would be so much nicer if it just said "STOP: There is a driver error/conflcit and your PC cannot function" - at least I'd know where to bloody well start.

I shall report back once I've got home and had the chance to tinker.

G

G,
There are some smart guys around here who can actually read the 'Dump' files that are created on a BSOD. Maybe one of them will check in.

Have you looked at your 'Event Viewer' in System and Application for any "Event ID" codes?

If you have any 'Error' or 'Warning' events, I can help you with that.

Vic

Vic

No - I didn't look at the Event Viewer or Event ID codes. I'll take a shufty tonight and post on here what I find.

Cheers

G

My guess is that the bent pins in the card reader caused a short which damaged the USB controller on the motherboard.
Usually there are multiple USB controllers (or channels) on a motherboard. For example, on my PC here the 2 USB ports on the front are from one USB Controller 4, and one the six on the back 2 are controller 1, 2 are 2, and 2 are 3. So basically if this were my computer, I would assume that USB Controller 4 got shorted out by the bent pins and is now damaged. Do any USB devices work on the front ports?

This is a tough problem as bugcheck code 35 is very rare. The crash may be caused by faulty ram or device driver error (ie video, sound card, modem and etc). The system event log and the minidump has the most useful diagnostic information. When Windows crashes with blue screen, it writes a system event 1001 or 1003 and a minidump to the folder \windows\minidump. Check system event 1001 and 1003 and it has the detail of the blue screen.

Event ID: 1001
Source: Save Dump
Description:
The computer has rebooted from a bugcheck.The bugcheck was : 0xc000000a (0xe1270188, 0x00000002, 0x00000000, 0x804032100).
Microsoft Windows..... A dump was saved in: .......

Event Source: System Error
Event Category: (102)
Event ID: 1003
Description:
Error code 1000007f, parameter1 0000000d, parameter2 00000000, parameter3 00000000, parameter4 00000000

Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Event 1001/1003. Copy the content and paste it back here

Zip 5 to 6 minidumps to a zip file and attach it at any webspace. I will study the dump and find out the culprit. If you can't provide the minidumps, run memtest to stress test the ram. Make sure that your windows is not infected with spyware, adware adn chkdsk /r.
http://www.memtest86.com/.

Get public webspace
Use a free service like rapidshare to attach the minidumps and post the url of the mimidumps at this thread.
http://www.rapidshare.de/

Cheers cpc2004

Thanks for the advice - I didn't get chance to try anything over the weekend as I felt really grotty, ut as I've had this guy's PC over a week now without any resolution in sight, I'd better knuckle down and take a shufty.

My biggest frustration is that the USB ports at the back of the mobo do not seem to produce the same BSOD when used. I can't therefore understand why the USB header pins on the mobo would cause a BSOD when there's a card reader/front USB port plugged into it.

As for Kennaniah's suggestion that the header pins may have shorted, I appreciate the time talken to comment, but I don't think it's that as I tried both USB sets of headers on the mobo and both triggered a BSOD. In fact, even when it was plugged into a USB PCI card I got the BSOD, so I'm assuming that it's a driver conflict but if that's the case, why aren't the rear ports causing a BSOD too - they must run from the same driver in XP.

I'm thinking I may try a reinstall of Windows with the card reader and front USB ports already connected, but I need to get the SATA drivers onto a CD as his PC doesn't have a floppy drive (altho I suppose I could try mounting one for the sake of getting it done).

If anyone has any good ideas let me know, otherwise I'll try posting the Event Log & minidump tonight.

Cheers

G

G,
All of the USB ports MAY not be using the same drivers.
Several motherboards have both USB 1.1 and 2.0 connectors on the same board.

Are there any manufacturer updates available for your motherboard?

Just a thought.

Vic

Hi Vic

I checked the ASRock website and the only USB drivers they have are the ones for Windows 98!!!! I assume that means that the generic drivers that come with ME & XP are sufficient for the mobo's needs.

For cpc2004, I've just signed up to RapidShare and here's the link to the 6 minidump files (in WinRAR) - I hope you can make any sense out of them:

http://rapidshare.de/files/35262614/Minidump.rar

I'll post the Event Viewer logs in a second as I'm using my PC at the moment and need to switch on the PC I'm trying to fix to post them.

G

Ok cpc2004, here's the Event Viewer info, but there doesn't seem to be anything recent and there's a variety of sources. What I'm about to paste here is from a System Error on 27 March 2006:

Event Type:      Error
Event Source:      System Error
Event Category:      (102)
Event ID:      1003
Date:            27/03/2006
Time:            17:57:32
User:            N/A
Computer:      DEV-H8MFL6VVUEX
Description:
Error code 00000035, parameter1 81e3a568, parameter2 00000000, parameter3 00000000, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45   System E
0008: 72 72 6f 72 20 20 45 72   rror  Er
0010: 72 6f 72 20 63 6f 64 65   ror code
0018: 20 30 30 30 30 30 30 33    0000003
0020: 35 20 20 50 61 72 61 6d   5  Param
0028: 65 74 65 72 73 20 38 31   eters 81
0030: 65 33 61 35 36 38 2c 20   e3a568,
0038: 30 30 30 30 30 30 30 30   00000000
0040: 2c 20 30 30 30 30 30 30   , 000000
0048: 30 30 2c 20 30 30 30 30   00, 0000
0050: 30 30 30 30               0000    

~~~~~~~~

Event Type:      Warning
Event Source:      Dhcp
Event Category:      None
Event ID:      1003
Date:            27/03/2006
Time:            04:43:27
User:            N/A
Computer:      DEV-H8MFL6VVUEX
Description:
Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 000B6AA43865.  The following error occurred:
The operation was canceled by the user. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: c7 04 00 00               Ç...    


~~~~~~~~

Event Type:      Information
Event Source:      Save Dump
Event Category:      None
Event ID:      1001
Date:            27/03/2006
Time:            17:59:04
User:            N/A
Computer:      DEV-H8MFL6VVUEX
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000035 (0x82375270, 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini032706-02.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


~~~~~~~~~

Event Type:      Information
Event Source:      Save Dump
Event Category:      None
Event ID:      1001
Date:            27/03/2006
Time:            17:56:22
User:            N/A
Computer:      DEV-H8MFL6VVUEX
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000035 (0x81e3a568, 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini032706-01.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


I have no idea if this means anything to anyone, but these are the only 1001/1003 Event ID's shown in the Event Viewer.

Cheers

G

Hi G,

Suggestion
1. I believe the problem is related to faulty ram as the last two minidumps are crashed due to memory access error and the bugcheck code EA may be related to faulty ram as well. Run memtest to stress test the ram
2. Your nVidia Display Card is at Aug 04 15:57:11 2004 and it is two years behind. You had better upgrade the nVidia display card driver to latest level
3. Bugcheck code EA may also related to faulty video memory. Run graphical card test program to stress test your vidoe card (ie utility like 3dmark and etc)


Summary of your minidumps
Mini032305-01.dmp BugCheck 100000EA, {822dc020, 825715b8, f8a98cb4, 1}
Owning Process            822fa020       Image:         csrss.exe
Probably caused by : nv4_disp.dll ( nv4_disp+21179 )

Mini032305-02.dmp BugCheck 100000EA, {823f32c0, 82432168, f8a9ccb4, 1}
Owning Process            823d86a0       Image:         csrss.exe
Probably caused by : nv4_disp.dll ( nv4_disp+2122a )

Mini032305-03.dmp BugCheck 100000EA, {823e63a0, 823075f0, f8aa0cb4, 1}
Owning Process            823e85a0       Image:         csrss.exe
Probably caused by : nv4_disp.dll ( nv4_disp+21179 )

Mini032305-04.dmp BugCheck 100000EA, {823fc7b8, 82315ea0, f8a94cb4, 1}
Owning Process            823d3c08       Image:         csrss.exe
Probably caused by : nv4_disp.dll ( nv4_disp+21179 )

Mini032305-05.dmp BugCheck 7A, {e1a8f8f8, c000000e, bf916327, 1a55c860}
Memory access error was found at the stack trace and this is the sign of faulty RAM
Owning Process            82146288       Image:         csrss.exe
Probably caused by : win32k.sys ( win32k!FreeDesktop+46 )

Mini032706-01.dmp BugCheck 35, {81e3a568, 0, 0, 0}
Mini032706-01.dmp DEFAULT_BUCKET_ID:  DRIVER_FAULT
Memory access error was found at the stack trace and this is the sign of faulty RAM
Owning Process            81ed9b98       Image:         explorer.exe
Probably caused by : aliperf.sys ( aliperf+765 )

Hi cpc2004

Thanks for your help in deciphering the minidumps.

I've just installed a new stick of 512MB Crucial RAM, but one of the old 256MB sticks is still inside. I might try it with only the new RAM installed as the fault may lie with the old RAM.

I'll download new nVidia drivers tonight.

I tried doing a repair installation of XP Pro Retail lst night to see if that would overwrite any corrupted drivers, but it keeps telling me that the License Key is not valid, despite it being on one of those MS stickers stuck to the side of the case. I've checked it countless times and I've not mistyped it or mistaken a B for an 8 - so I'm kinda stumped as to why that is happening.

G

Hi G,
When we talked about RAM problems way up top, you mentioned that you had installed a new stick - but not that you had left the old one in.
The old rule of 'last thing in is first thing out' would seem to apply here.
Take out the new RAM, make sure the old RAM is in its original slot and re-test.
IF that works, then try to REPLACE the old RAM in the same slot with the new.

I've had tons of problems with mixing and matching RAM.

Good Luck,
Vic

Cheers Vic

Sorry - I kinda forgot to mention that I'd left an old stick of RAM in. Originally the mobo had 2 sticks of 256MB RAM, so I removed one of these and put in the new 512MB stick, leaving one of the old ones still in there. I shall try removing the old one and using the new on it's own.

Quick question - does anyone know if System Restore will take me back to before I attempted to repair Windows. The only reaon I ask is that since trying to repair Windows, it says I have to activate it before it allows me into any of the accounts. However, this is where I get the screen telling me that the License Key isn't valid (even though it's an official MS one stuck to the case). I've tried speaking with Microsoft, but the activation people can't help me and as I'm at work I can't call MS Tech Services. So I was wondering that if I used System Restore from Safe Mode (which I can get into) would I be able to revert back to the stage before I attempted the Repair installation.

Cheers

G

G,
Your various System Restore points should have a date associated with them.
If the dates coincide with a 'pre-repair' date, you should be good to go.

As a side note, I have found the MS folks to be real helpful when I explain the details of any authentication problem I have.

Keep working on that side of things while you think about the Restore.

Vic

Ok guys (and gals in case any are reading this!), here's an update.

I've tried using a USB pen drive in the front ports with only the new 512MB RAM installed, but I still get the "No_More_IRP_Stacks_Available" BSOD.

I've updated the nVidia graphics driver to the most recent ones available (which are August 2006) and I still get the BSOD.

I can't use System Restore to go back before the Windows repair I tried as it tells me that there are no Restore Points to use. So I tried using a different version of XP Pro and whenever I try inserting the License Key it tells me that the key isn't valid, despite the license key being on an MS Sticker on the case. So I've used an old license key (which Windows is now reporting as being a fraudulent one) but at least I can get into Windows again, but I still get the BSODs.

I'm now totally stumped as I've tried everything that's been suggested by you good people. If I post the latest minidumps can someone just check them for me pls.

Cheers

G

oops - helps if I include the rapidshare link to the minidump file!!!

http://rapidshare.de/files/35387089/Minidump.rar

Cheers

G

Have you tried it with JUST the old RAM stick in there?
(Grasping at straws here).
Vic

Hi Vic - yep tried that (not many straws to grasp now is there!!)

An update on the situation - the rear USB ports are now causing a BSOD as well which means that trying a Windows repair has in fact made the problem worse, not better. I've resolved the activation issue btw.

However, if I boot into Safe Mode I can use any USB port I like and it doesn't cause it to BSOD. So (can you guess what my next question's gonna be?) how do I figure out which drivers aren't loaded in Safe Mode to try and determine which one is causing the BSOD?

G

G,
When we have to call in Level III techs (for warranty support), it is only after we have tried every 'keystroke' trick we can think of, plus all drivers, updates, etc.

When they show up, the always bring 3 items
1. MotherBoard
2. RAM
3. PSU

In their words "you guys have tried everything else, so it has to be one of these three".

I don't know if you're at the point where you have tried EVERYTHING else, but you're getting close.
It may be about time to try #1 & 3.

Vic

Vic

The idea of 1 crossed my mind as it must have something with the USB headers on the mobo or the drivers. Unfortunately, without spending some cash to buy a new mobo I can't test this theory and although I could buy a new mobo, if that didn't cure the problem, then I'd be stuck with a mobo i didn't need.

G

G,
Don't know if it was a typo, but I just reviewed all of the posts.

You said that originally, you had 2 sticks or RAM -- when you tested recently (3-4 posts ago) did you put in both sticks of old RAM for the test?

Some MB & RAM require matching RAM sticks.


Also, at the rate your customer is burning up your labor hours, it might be cheaper for him to have a new motherboard.   :)


Vic

Vic

When I was originally given the PC to repair, there were two matching sticks of Elixir 256MB of RAM. I took one of these out and stuck in the 512MB of Crucial RAM (chosen by using the mobo matching system Crucial have on their website). However, the BSODing continued. So, at your suggestion, I took out the 256MB stick, leaving just the 512MB stick in on it's own. However, this didn't stop the BSODing either.

I do have a mobo here, but it's a P4 socket 478 with a 2.8GHZ Northwood processor. However, this PC has a AMD 64 CPU and compatible ASRock mobo. If I was to swap them over to try your suggestion, it would mean a fair bit of work.

G

G,
OK - got it.
Have you tried putting both matching sticks of Elixir 256MB of RAM back in and running it that way -- or is that the original problem?
I can find a link to 'memtest' that will run extensive tests on the RAM to make sure it is still fully functional.

Vic

The latest mimidumps are not crashed by the video card display driver.

Mini100306-01.dmp BugCheck 35, {82acb2c8, 0, 0, 0}
Probably caused by : USBSTOR.SYS ( USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+9c )

Mini100306-02.dmp BugCheck 35, {82f74648, 0, 0, 0}
Probably caused by : disk.sys ( disk!DiskFlushDispatch+b8 )

Mini100306-03.dmp BugCheck 35, {82f60a30, 0, 0, 0}
Probably caused by : disk.sys ( disk!DiskFlushDispatch+b8 )

Mini100306-04.dmp BugCheck 35, {81f45c90, 0, 0, 0}
Probably caused by : USBSTOR.SYS ( USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+9c )

From the stack trace of two minidumps, I find the footprint of aliidex.sys and pxfsf.sys.  One of them maybe the culprit. Upgrade the allidex.sys and pxfsf.sys may resolve the problem.


f799fb60 f7371bac 82f74648 00000000 00000001 aliidex+0x33f
f799fbac 804eddf9 82fd25c0 82f74700 f799fc38 pxfsf+0x3cbac

Stack trace
f4601740 804edde0 00000035 82acb2c8 00000000 nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo])
f4601758 f78b470c 82a44aa7 82b5a928 82b5a806 nt!IopfCallDriver+0x18 (FPO: [0,0,0])
f460176c f78b565f 82a448d0 82acb2c8 82b84cb4 USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+0x9c (FPO: [Non-Fpo])
f46017a4 f78b6061 82a448d0 82acb2c8 82a448d0 USBSTOR!USBSTOR_CbwTransfer+0x79 (FPO: [Non-Fpo])
f46017cc 804eee19 82a448d0 00acb2c8 826eebb0 USBSTOR!USBSTOR_StartIo+0x13b (FPO: [Non-Fpo])
f46017ec f78b4aee 82a448d0 82acb2c8 82b5a914 nt!IoStartPacket+0x7d (FPO: [Non-Fpo])
f4601810 804eddf9 826eeaf8 82acb2c8 82b5a8e8 USBSTOR!USBSTOR_Scsi+0x108 (FPO: [Non-Fpo])
f4601820 f75d1614 82b5a928 82b5a8e8 82acb2c8 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
f4601838 f75d06ce 82d4f9a0 82b5a8e8 82acb2c8 CLASSPNP!ClassSendSrbAsynchronous+0x111 (FPO: [Non-Fpo])
f46018d4 f75bd402 82d4f9a0 82acb2c8 82acb2c8 CLASSPNP!ClassDeviceControl+0x731 (FPO: [Non-Fpo])
f4601968 f75cd47f 82d4f9a0 82acb2c8 82acb380 disk!DiskDeviceControl+0xdcc (FPO: [Non-Fpo])
f4601984 804eddf9 82d4f9a0 82acb2c8 82acb2c8 CLASSPNP!ClassDeviceControlDispatch+0x48 (FPO: [Non-Fpo])
f4601994 f77e6667 82acb378 83165918 82acb2c8 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
f46019c0 804eddf9 82a4d608 82acb2c8 82acb39c PartMgr!PmDeviceControl+0x8c (FPO: [Non-Fpo])
f46019d0 f75cec3a 0007c0d0 826bdc20 82acb2c8 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
f4601a54 f75bd402 826bdb68 82acb2c8 82acb2c8 CLASSPNP!ClassDeviceControl+0x87e (FPO: [Non-Fpo])
f4601ae8 f75cd47f 826bdb68 82acb2c8 00000000 disk!DiskDeviceControl+0xdcc (FPO: [Non-Fpo])
f4601b04 804eddf9 826bdb68 82acb2c8 82acb380 CLASSPNP!ClassDeviceControlDispatch+0x48 (FPO: [Non-Fpo])
f4601b14 f2650e5d 82e469e8 82acb2c8 82acb200 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
f4601b48 f26504a9 82cf15d0 82d0bab0 82e469e8 Fastfat!FatCommonDeviceControl+0xe8 (FPO: [Non-Fpo])
f4601b8c 804eddf9 82d0b9b8 82acb2c8 83142f38 Fastfat!FatFsdDeviceControl+0x3e (FPO: [Non-Fpo])
f4601b9c f7a6433f 804eddf9 82e46b88 82acb2c8 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
WARNING: Stack unwind information not available. Following frames may be wrong.
f4601be8 f7371bac 82acb2c8 00000000 00000001 aliidex+0x33f
f4601c34 804eddf9 82e46930 82acb380 806d02d0 pxfsf+0x3cbac
f4601c44 80573b42 82acb380 826d2028 82acb2c8 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
f4601c58 805749d1 82e46930 82acb2c8 826d2028 nt!IopSynchronousServiceTail+0x60 (FPO: [Non-Fpo])
f4601d00 8056d33c 00000d44 00000000 00000000 nt!IopXxxControlFile+0x5e7 (FPO: [Non-Fpo])
f4601d34 8053c808 00000d44 00000000 00000000 nt!NtDeviceIoControlFile+0x2a (FPO: [Non-Fpo])
f4601d34 7c90eb94 00000d44 00000000 00000000 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ f4601d64)
008efd48 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_TEXT:  
f799f920 804edde0 00000035 82f74648 00000000 nt!KeBugCheckEx+0x1b
f799f938 f75c02e6 00000000 8296ff40 82f74648 nt!IopfCallDriver+0x18
f799f950 f75c049a 8296fab8 8296ff40 8296fab8 disk!DiskFlushDispatch+0xb8
f799f974 f75cd3a2 8296fab8 8296ff98 82f746d4 disk!DiskShutdownFlush+0x14a
f799f990 804eddf9 8296fab8 82f74648 83185400 CLASSPNP!ClassShutdownFlush+0x5d
f799f9a0 f77e44ca 804eddf9 824ba6e8 82f74648 nt!IopfCallDriver+0x31
f799f9a4 804eddf9 824ba6e8 82f74648 82f746f8 PartMgr!PmPassThrough+0x1b
f799f9b4 f75c05a5 82651c68 82f74648 82651d20 nt!IopfCallDriver+0x31
f799f9d0 f75cd3a2 824ba6e8 82f74648 82f74700 disk!DiskShutdownFlush+0x255
f799f9ec 804eddf9 82651c68 82f74648 00000000 CLASSPNP!ClassShutdownFlush+0x5d
f799f9fc b748b3e1 829b16f8 830cf4e0 00000001 nt!IopfCallDriver+0x31
f799fa20 b7471e3f 829b16f8 82f74648 82651c68 Fastfat!FatHijackIrpAndFlushDevice+0x52
f799fa40 b748de47 829b16f8 82f74648 830cf4e0 Fastfat!FatFlushAndCleanVolume+0x36
f799faa0 b748e1b9 829b16f8 82f74648 830cf4e0 Fastfat!FatPnpQueryRemove+0x74
f799fabc b748e22c 829b16f8 82f74648 82fd2678 Fastfat!FatCommonPnp+0x81
f799fb04 804eddf9 830cf3e8 82f74648 8317fc10 Fastfat!FatFsdPnp+0x51
f799fb14 f7a6433f 804eddf9 82e5ad70 82f74648 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
f799fb60 f7371bac 82f74648 00000000 00000001 aliidex+0x33f
f799fbac 804eddf9 82fd25c0 82f74700 f799fc38 pxfsf+0x3cbac
f799fbbc 80586d67 830cf3e8 82651c68 00000001 nt!IopfCallDriver+0x31
f799fbe8 80586e8b 82fd25c0 f799fc14 00000000 nt!IopSynchronousCall+0xb7
f799fc3c 80587b73 82651c68 00000001 00000000 nt!IopRemoveDevice+0x93
f799fc54 805889b6 8294c638 f799fd18 f799fce0 nt!IopQueryRemoveLockedDeviceNode+0x33
f799fc6c 80588a03 8294c638 00000000 e363f760 nt!IopDeleteLockedDeviceNode+0x4e
f799fca0 8058e49f 82a62720 0263f760 00000000 nt!IopDeleteLockedDeviceNodes+0x3f
f799fd34 8058e936 f799fd70 806d0778 e293e428 nt!PiProcessQueryRemoveAndEject+0x597
f799fd50 8058ea8f f799fd70 825fcc50 8055a1fc nt!PiProcessTargetDeviceEvent+0x2a
f799fd74 80533dd0 825fcc50 00000000 831c6da8 nt!PiWalkDeviceList+0xfd
f799fdac 805c4a28 825fcc50 00000000 00000000 nt!ExpWorkerThread+0x100
f799fddc 80540fa2 80533cd0 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

Many thanks for that cpc2004 - I don't know how you decipher all that stuff, but I'm impressed.

My next question therefore is how on earth do I update the aliidex.sys and pxfsf.sys files you mention? I'e never heard of either of them, altho the mobo does use the Ali chipset.

I was thinking about this problem on the way into work this morning and I had the following thoughts, which I'd be grateful for your comments on.

When I first attach the header cable from the card reader or front USB ports to the mobo everything seems fine. I plug in a USB pen drive and Windows finds and installs the relevant drivers (you get the notification bubbles in the System Tray saying New Hardware found and installed successfully) and then automatically loads Windows Explorer so that you can see what is on the pen drive. I can then click on the SysTray icon that allows you to safely remove the pen drive and then reinsert the pen drive in a different USB port or the same one and it loads up Windows Explorer again. This is normal behaviour of a working system, I think you'll agree.

However, once you reboot the PC the system becomes unstable, because as soon as you insert a pen drive, you get the BSOD. If you leave the pen drive plugged in and reboot the PC, the PC BSODs as soon as it gets to the Welcome Screen.

My thoughts are therefore that the driver conflict (if that's what it is) is happening after the initial pen drive drivers are installed by Windows and the PC is rebooted.

Now, if you boot into Safe Mode, you can insert and remove a pen drive as often as you like and after as many reboots as you like (provided you boot into Safe Mode every time you boot) and the system never falls over. Therefore, there must be a driver conflict between the Windows XP driver for a pen drive and something that loads in a normal boot, but not in Safe Mode.

Does that make any kind of sense? And if so, how do I go about tracking down which file is causing the conflict?

Your thoughts would be appreciated.

G

Ok - just had a light bulb moment.

When I've tried repairing the Win XP installation, it gets to a stage where it ask for the aliide.sys driver file as it can't find it on the WinXP CD. If I click on the browse button I can find the file in the CD's i386 folder and it happily installs it. If this file is actually on the CD, why doesn't it load it in the first place? also, the filename is uncannily similar to the one cpc2004 pointed out - is there a connection perhaps?

G

Check out these links for both:

http://driveragent.com/results.php?t=4674720&p=0

http://www.file.net/process/aliide.sys.html

Correction.

aliidex.sys is ALi mini IDE Driver.

Aha - PreVx is installed on his PC and I have to say it's bloody annoying. I've been tempted a few times to remove it, but something was stopping me. I may use this as an excuse to remove the software altogether and see if that cures his problem.

Cheers guys - you are doing sterling work in trying to help me resolve this problem and if nothing does work, it wont be for lack of suggestions. Your help is very much appreciated andeven if no clear resolution arrives, the points will be awarded in recognition of your efforts.

I'll report back later on.

G

Ok - I've found the cause.

I uninstalled PreVx and it cured the problem. I was able to insert pen drives and multi-media cards to my hearts content. Even after rebooting the PC several times it remained totally stable if I plugged anything in.

Here comes the but......

But, to give the PC some internet security I installed Zone Alarm Security Suite v6.5.737.00. However, as soon as I installed a pen drive I got a BSOD again with the IRP Stack message. It seems therefore that this problem is caused by a conflict with security software.

I've posted the last minidumps created here

http://rapidshare.de/files/35495493/Minidump20061004.rar

and would be grateful if you cpc2004 would check them for me.

Cheers

Geoff

Well - I'm using Zone Alarm Security Suite on my PC which includes Anti-Virus, Spyware detector, Spam blocker/filter as well as the firewall. I've found it to be much better than Norton and it does the job for me. I also have SpyBot and Ad-Aware running, but I've never had any problems with ZA Sec Suite.

However, in respect of the PC I'm repairing I have now downloaded and installed AVG Free as an Anti-Virus and Comodo (a free firewall) and the system is running very stable at the moment. Whatever it didn't like about PreVx and ZA obviously isn't a problme for Comodo.

As I said before, I think you guys have been brilliant and I could not have got thi sPC up and running again without you. I can't say I'm any the wiser as to why it happened, but through a process of elimination the cause was found and removed.

As for the points, the majority of them will go to cpc2004 as it was he who suggested the PreVx file. However, I believe that Vic deserves something for his perseverance in putting forward suggestions, even when it looked like there was no others to give. I hope that's ok.

Cheers again guys

G

G,
What really counts is that the dad-gummed confuser is back up and running.

Thank you for the points, and real glad you're good to go on that thing.

Take care,
Vic

Hi G,

From your latest minidump, your windows install Panda (outpost) Firewall and not ZoneAlarm. Probably the internet security module is confilict with the ALi mini IDE Driver.  You had better contact the software vendor of ALi mini IDE Driver.

Thanks - I will bear that in mind if I ever get the PC back with the same error. At the moment though, I've got AVG and Comodo Firewal (both free) installed and running and the system is stable.

Cheers

G