Thank you very much for your help, I have located the Polunnot file and changed it to .bak so hopefully that will work. I have deleted Daemon and Alcohol 120 wasn't on my comp. I was already using MagicDisc.
With regards to the drivers sorry for my ignorance but how do I determine which ones are missing? Is this the ones in your reply like winbondcir.sys etc excluding the Polunnot.sys file?
Again thanks for your help, total newbie to this if I am honest.
Chrs
These were caused by the Polunnot.sys driver, but I cannot find any reference to it in google. that makes me suspicious.
I would find it and rename it to polunnot.bak to prevent it from launching. If it is used in some app that app will complain.
I also noticed you have many old drivers that urgently need to b e updated.
Code:
winbondcir.sys 3/28/2007 01:51:32 AM 0x92fea000 0x92fff000 0x00015000 0x460a0264
lmimirr.sys 4/10/2007 06:32:11 PM 0x92fff000 0x92fffc80 0x00000c80 0x461c106b
int15.sys 7/2/2007 10:03:24 PM 0xaf269000 0xaf270000 0x00007000 0x4689ae6c
acehlp10.sys 7/11/2007 04:20:16 AM 0x91574000 0x915a3900 0x0002f900 0x469492c0
acedrv10.sys 7/24/2007 03:45:08 AM 0xaf213000 0xaf269000 0x00056000 0x46a5ae04
RaInfo.sys 1/4/2008 02:57:12 PM 0xaf270000 0xaf271800 0x00001800 0x477e8188
seehcri.sys 1/9/2008 04:41:37 AM 0x930c1000 0x930c6f00 0x00005f00 0x478488c1
psdfilter.sys 2/18/2008 09:49:54 AM 0x8b675000 0x8b67e000 0x00009000 0x47b98d02
PSDNServ.sys 2/18/2008 09:50:35 AM 0xaf33b000 0xaf344000 0x00009000 0x47b98d2b
PSDVdisk.sys 2/18/2008 09:50:56 AM 0xaf344000 0xaf356000 0x00012000 0x47b98d40
LMIRfsDriver.sys 7/14/2008 12:26:22 PM 0xaf272000 0xaf27c000 0x0000a000 0x487b7e2e
polunnot.sys 9/19/2008 06:27:00 PM 0x8bc4d000 0x8bc5c000 0x0000f000 0x48d42734 polunnot.sys+3958
AGRSM.sys 11/10/2008 10:56:37 AM 0x93a32000 0x93b38000 0x00106000 0x49184ba5
RimSerial.sys 11/24/2008 01:02:13 PM 0x93093000 0x93099a00 0x00006a00 0x492ade15
mcdbus.sys 2/24/2009 06:42:13 AM 0x930a4000 0x930c0800 0x0001c800 0x49a3cf05
DKbFltr.sys 3/25/2009 11:10:12 PM 0x9151b000 0x91525000 0x0000a000 0x49caf214
b57nd60x.sys 4/26/2009 07:15:34 AM 0x914c7000 0x91503000 0x0003c000 0x49f44256
spldr.sys 5/11/2009 12:13:47 PM 0x8bbaf000 0x8bbb7000 0x00008000 0x4a084ebb
jmcr.sys 5/18/2009 02:18:59 AM 0x914a8000 0x914c7000 0x0001f000 0x4a10fdd3
GEARAspiWDM.sys 5/18/2009 08:16:53 AM 0x915a4000 0x915a9280 0x00005280 0x4a1151b5
amdxata.sys 5/19/2009 01:57:35 PM 0x8b627000 0x8b630000 0x00009000 0x4a12f30f
PxHelp20.sys 6/23/2009 07:16:17 PM 0x8b67e000 0x8b687300 0x00009300 0x4a416241
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
Driver Reference
- - Driver manufacturer links are on this page:
Drivers and Downloads
You also have a file that is a huge cause of BSOD's called sptd.sys. Its used in alcohol120 and daemon tools
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.
They use a driver, found in your dmp,sptd.sys, that is notorious for causing BSODs.
Use this SPTD uninstaller
DuplexSecure - Downloads
when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.[/QUOTE]
