J JoeBloggs Active member Joined Jun 30, 2012 Posts 37 Jun 30, 2012 #1 Hi, I have a BSOD that keeps coming up on my machine, I also find that I cannot update SuperAntispyware. I have been helped by the guys over on Help2go but they suggested that I post my problem here. The thread on help2go can be found here. Here is a 'Whocrashed' log if it helps System Information (local) computer name: BLACKDELL windows version: Windows XP Service Pack 3, 5.1, build: 2600 windows dir: C:\WINDOWS CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz Intel586, level: 6 2 logical processors, active mask: 3 RAM: 2136055808 total VM: 2147352576, free: 2021253120 [FONT=Segoe UI, Arial]Crash Dump Analysis [/FONT] [FONT=Segoe UI, Arial]Crash dump directory: C:\WINDOWS\Minidump[/FONT] [FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]Crash dumps are enabled on your computer. [/FONT][/FONT] [FONT=Segoe UI, Arial]On Mon 21/05/2012 09:57:38 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\Mini052112-01.dmp This was probably caused by the following module: [FONT=Segoe UI, Arial]atapi.sys[/FONT] (atapi+0xD50C) Bugcheck code: 0x7A (0xFFFFFFFFC05CF830, 0xFFFFFFFFC000000E, 0xFFFFFFFFB9F0650C, 0x1A945860) Error: [FONT=Segoe UI, Arial]KERNEL_DATA_INPAGE_ERROR[/FONT] file path: C:\WINDOWS\system32\drivers\atapi.sys product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT] company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT] description: IDE/ATAPI Port Driver Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. [/FONT] [FONT=Segoe UI, Arial]Conclusion [/FONT] [FONT=Segoe UI, Arial]1 crash dumps have been found and analyzed. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. [/FONT] Can somebody help please?