The BSOD which is really not helpful, please help!

bluetech

bluetech

bluetech

Associate
Joined
27 Aug 2006
Posts
435
OK, three PC's in one household are all doing the same thing. Once every 2 weeks or so, a BSOD says hello. I am not of the faint hearted to BSOD's. I have seen and resolved many in my time (mainly a faulty HDD or new driver issue). But this on is different.

I think the main part is 0x0000001A. And it occasionally relates to DrvFltIp being the issue, the other day I got a BSOD when installing XP drives to vista for saitek joystick, the BSOD related to the saitek drivers so its obvious this was the problem in this case).

Now I have no idea what it is that it is relating to. I would like to read the .dmp files but have never had to do this and don't have a clue how. I have downloaded the Microsoft debugging tool kit, entered the correct info (i think) to the symbol part of the program and still I get the message relating to cant find symbols (symbol files have been downloaded however to c:\symbols.

The annoying part of this BSOD is that it occurs out of the blue for no reason whatsoever, unlike the mentioned Saitek issue. There is no pattern, just a trail of .dmp files I have to follow. This is not a vista issue as 2 of the pc's have XP and my PC have Vista / XP duel boot. The usual BSOD has only been seen in XP, the only BSOD I have seen in Vista is the Saitek one which was partially expected and hasn't occurred again since the Saitek XP drivers were uninstalled.

Thanks Guy's. Your help will be appreciated as allways!
 
Drvfltip.sys is apparently a file belonging to Ashampoo firewall. Try uninstalling it (assuming that is what you're using).
 
try updating the firewall if the above works (i.e. it is the firewall causing the problem) it may be that an update is needed. mcafee was giving my friend a BSOD and it just needed an update.
 
hohum said:
Drvfltip.sys is apparently a file belonging to Ashampoo firewall. Try uninstalling it (assuming that is what you're using).
Click to expand...

Ahha! I suspected as much. I removed this on one of the PC's a while back and the error message still appears (same error code but not stating "drvflip". Thanks for clearing that one up though... one step closer!

Can anyone help me to interoperate the .dmp files. From what IS readable the file suspected always changes. I have updated the following drivers:

Graphics Card (8800)
Chipset (Intel 965P)
Sound (Realtek)

Any other divers I might need to give a go updating? (using a GA 965P DS3 Gigabye motherboard on two of the PC's)

Thanks for your help guy's. This has been bugging me for about two months now. Hopefully with your help I can resolve this issue!
 
Last edited:
OK, so the 3rd PC has recently had XP re-installed so no .dmp files to go by on that one. But from what information I can get from the .dmp files (ignoring the symbol issue, if anybody can give help here... please advise) here is a list of suspected issues in the .dmp files:

PC1 (XP)

Probably caused by : DrvFltIp ( DrvFltIp+4d5a )
Probably caused by : DrvFltIp ( DrvFltIp+4d5a )
Probably caused by : RtkHDAud.sys ( RtkHDAud+41947b )
Probably caused by : DrvFltIp ( DrvFltIp+4d5a )
Probably caused by : ntoskrnl.exe ( nt+22c37 )
Probably caused by : ntoskrnl.exe ( nt+22c37 )
Probably caused by : ntoskrnl.exe ( nt+22c37 )

PC1 (Vista)

Probably caused by : SaiIFFB5.sys ( SaiIFFB5+955 )
Probably caused by : SaiIFFB5.sys ( SaiIFFB5+955 )


PC2 (XP)

Probably caused by : DrvFltIp ( DrvFltIp+4d22 )
Probably caused by : DrvFltIp ( DrvFltIp+4d3f )
Probably caused by : DrvFltIp ( DrvFltIp+4d5a )
Probably caused by : DrvFltIp ( DrvFltIp+4d3f )
Probably caused by : DrvFltIp ( DrvFltIp+5160 )


So PC2 really needs ashampoo's personal firewall to be removed from the looks of it, thanks to "hohum" for that one. I may follow your advice daven1986 if all goes well on that PC for atleast a month with it removed.

As for PC1, can anyone shed any light? The realtek issue arose when installing an updated driver. Uninstalled / Reinstalled with no issues the next time.

So PC1 (my PC) is having issues in XP with ntoskrnl.exe, from my understanding this is a required system files so obviously I cannot uninstall it.

I am going to try and run sfc.exe over c:\ of winXP os on PC1, see if it picks up ntoskrnl.exe. Good idea? Or not?

Please advise with whatever you feel unnecessary, plus I would really like some help on reading those .dmp files properly.

Thanks guys!
 
Last edited:
OK, gaveup with sfc.exe rather quickly. It asked for an XP PRO SP2 disc (unusuall as I am running xp) so I ignored and poped in Home disc... nope still wants pro. So I have an XP PRO SP2 disc, pop it in and "The CD you have put in is not the same as the product on the PC"... really? Oh well blow me down!

So I gave up and manually copied the reqired file (ntoskrnl.exe) to c:\, expanded it and put it in sys32. XP loads fine and dandy as per normal. We shall have to wait and see with the BSOD's. But this system (PC1) runs both XP and Vista (bootloader). And I use Vista a lot more then I used to now.

Would you say that the above was a good way to repair?

Thanks guy's!
 
You have run memtest on these PCs I assume? Try the windows based one from http://hcidesign.com/memtest/, as it picked up a problem with my RAM a while back that memtest86+ never found. Nothing worse than wasting a load of time configuring software only to find your hardware was to blame the whole time.
 
You must log in or register to reply here.
Back
Top Bottom