[fielkun]

I've been having the same problem as well. Everytime I boot up my computer, it would take several minutes before it crashes into a blue screen saying that thing "DRIVER IRQL NOT LESS OR EQUAL" and after I restarted my pc, a message would appear saying my pc has recovered from serious error. Then after that, I can use my pc for longer hours but with random freezing every now and then.

Stop: 0x0000000A (0xB0C38008, 0x00000006, 0x00000001, 0x8074649A)

My OS is Microsoft Win XP Professional 32 bit

I also attached my minidump

and one more thing though, I am using this program called DRIVER MAX, and it says I have 13 updates available. I already updated 4 drivers. Just waiting for the rest. Driver Max free version only allows 2 downloads per day.





Hope you could help me with my problems.
Thanks!

Attached File(s)

•  Minidump.zip (403.24K)
  Number of downloads: 93

[Macboatmaster]

fielkun

Welcome to Geeks to Go

You also posted this in the topic on stop codes
http://www.geekstogo...ath-stop-codes/

For your future information please always start your own topic on a matter on which you require advice, as you have here and please post the problem ONLY once.

The reason for that is that if you post twice, you can have two people helping, unaware that they are duplicating each others work. That of course is confusing for you, continually jumping between thw two topics, and of course a waste of time for the people helping.
Thanks


Now to the issue in hand - was everything OK before you decided to update drivers with DriverMax.
OR was Driver MAX used in the attempt to solve the problem.

Please download and run this clicking on the analyse tab
The free WHO CRASHED
http://www.resplendence.com/downloads

Then please copy and paste the results of the analysis

You only need to copy the actual results from the line
X crash dumps have been found
to the line
We suggest etc.


You do not need to copy all the Intro and all the blurb about Who Crashed

Please send that as an actual paste on here not as a file which I have to open
Thanks

[rshaffer61]

The meaning of the stop code below.

Quote

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online MSDN article.)
Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)

If using DriverMax update the video driver first to see if that resolves the issue. Please follow Macboatmaster first as he is the lead on this topic. I am simply adding to the topic.

[fielkun]

Thanks a lot for your response Macboatmaster and Rshaffer

@Macboatmaster:
I decided to you use DriverMax in attempt to solve this problem. (and I'm sorry if I double posted the other day, I was just really desperate seeking for some help.)

Alrighty, here's what WhoCrashed says after analyzing my system:

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Sat 4/14/2012 12:00:29 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041412-01.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Fri 4/13/2012 11:01:17 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041312-02.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Fri 4/13/2012 10:44:01 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041312-01.dmp
This was probably caused by the following module: sf.sys (sf+0x957)
Bugcheck code: 0xE7 (0x2, 0xFFFFFFFF81375930, 0xFFFFFFFFF87C9E20, 0x0)
Error: INVALID_FLOATING_POINT_STATE
file path: C:\WINDOWS\system32\drivers\sf.sys
product: Sonic Focus DSP service driver
company: Sonic Focus, Inc
description: DSP service driver 08-28-2004 build for SF 1.X
Bug check description: This indicates that a thread's saved floating-point state is invalid.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: sf.sys (DSP service driver 08-28-2004 build for SF 1.X, Sonic Focus, Inc).
Google query: sf.sys Sonic Focus, Inc INVALID_FLOATING_POINT_STATE




On Thu 4/12/2012 1:15:44 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041212-03.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Thu 4/12/2012 7:41:55 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041212-02.dmp
This was probably caused by the following module: hal.dll (hal+0x8A9A)
Bugcheck code: 0x1000000A (0xFFFFFFFFB0C38008, 0x5, 0x1, 0xFFFFFFFF80746A9A)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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.


On Thu 4/12/2012 1:08:03 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041212-01.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Wed 4/11/2012 2:55:57 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041112-04.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Wed 4/11/2012 11:38:56 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041112-03.dmp
This was probably caused by the following module: hal.dll (hal+0x8A9A)
Bugcheck code: 0x1000000A (0xFFFFFFFFFB0E2B28, 0x5, 0x1, 0xFFFFFFFF80746A9A)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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.


On Wed 4/11/2012 8:34:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041112-02.dmp
This was probably caused by the following module: sf.sys (sf+0x957)
Bugcheck code: 0xE7 (0x0, 0x0, 0x0, 0x0)
Error: INVALID_FLOATING_POINT_STATE
file path: C:\WINDOWS\system32\drivers\sf.sys
product: Sonic Focus DSP service driver
company: Sonic Focus, Inc
description: DSP service driver 08-28-2004 build for SF 1.X
Bug check description: This indicates that a thread's saved floating-point state is invalid.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: sf.sys (DSP service driver 08-28-2004 build for SF 1.X, Sonic Focus, Inc).
Google query: sf.sys Sonic Focus, Inc INVALID_FLOATING_POINT_STATE




On Wed 4/11/2012 12:07:46 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041112-01.dmp
This was probably caused by the following module: hal.dll (hal+0x8A9A)
Bugcheck code: 0x1000000A (0xFFFFFFFFFB4AC008, 0x5, 0x1, 0xFFFFFFFF80746A9A)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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.


On Tue 4/10/2012 2:01:03 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041012-03.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Tue 4/10/2012 12:19:08 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041012-02.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Tue 4/10/2012 8:13:54 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041012-01.dmp
This was probably caused by the following module: atapi.sys (atapi+0x1D7F)
Bugcheck code: 0x100000D1 (0xFFFFFFFF84380101, 0x5, 0x1, 0xFFFFFFFFF847BD7F)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Sat 4/7/2012 12:01:00 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040712-01.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Fri 4/6/2012 12:15:48 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040612-01.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

20 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

sf.sys (DSP service driver 08-28-2004 build for SF 1.X, Sonic Focus, Inc)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

[rshaffer61]

It looks ot be caused mainly by two drivers.
Atapi.sys and sf which is part of the Sonic software.
My suggestions would be to uninstall Sonic for now and see what happens.

[fielkun]

rshaffer61, on 13 April 2012 - 08:05 PM, said:

It looks ot be caused mainly by two drivers.
Atapi.sys and sf which is part of the Sonic software.
My suggestions would be to uninstall Sonic for now and see what happens.

Thanks, but how do I uninstall the Sonic Software? I can't find it at the Add/Remove Program panel.

[rshaffer61]

Download and install Revo Uninstaller

• Double click the Revo Uninstaller icon on your desktop to start the program
  
• Scroll through the listed programs and Right Click on the program you wish to uninstall (Sonic)
  
• From the pop out menu choose Uninstall
  
• Click Yes to the confirmation dialogue
  
• In the next window select the Advanced mode
  
• Click Next to start uninstalling the program
  
• Answer Yes to confirm the uninstall
  
• When the program has completed the four steps, click Next to allow the program to search for leftovers
  
• Once complete, click Next, then Finish
  
• Repeat the above steps for any other programs you wish to remove.

http://www.revouninstaller.com/

[fielkun]

Thanks, I already installed Revo Uninstaller but still, I can't find that "Sonic Software" on the program list.

[edit]

Ooh, I believe it's part of the SoundMax soundcard and I also noticed in DriverMax that I still need to update this driver called "SoundMax Integrated Digital Audio" thing. But I have already used my two downloads today, so I guess I'll have to wait for tomorrow and see what's gonna happen.

But I'm still looking for some possible solutions for this one

[rshaffer61]

Quote

Ooh, I believe it's part of the SoundMax soundcard and I also noticed in DriverMax that I still need to update this driver called "SoundMax Integrated Digital Audio" thing. But I have already used my two downloads today, so I guess I'll have to wait for tomorrow and see what's gonna happen.

Once you get the sound card driver updated hopefully that will take care of that issue. The Sonic we can check to see if it is running else where too.



Download Autoruns from the link in my signature below:

1: Extract the Autoruns Zip file contents to a folder.
2: Double-click the "Autoruns.exe".
3: Click on the "Everything" tab
4: Remove any entries that mention "File Not Found" by right-clicking the entry and select Delete.
5: Go to File then to Export As or Save in some versions.
6: Save AutoRuns.txt file to known location like your Desktop.
7: Attach to your next reply.

[fielkun]

Alrighty, I already attached the AutoRuns file.

Attached File(s)

•  autoruns.txt (55.19K)
  Number of downloads: 52

[rshaffer61]

Nothing in Autoruns for Sonic. Try this below and let me know.




Lets see what you have in your startup

Please click on
Start and then to Run
Type in msconfig and press Enter
Now click on Startups
Then uncheck everything that says Sonic and restart.
IMPORTANT! In case of laptop, make sure, you do NOT disable any keyboard, or touchpad entries.
If system boots correctly and is running smoothly and faster then we have a startup problem
Try going back into msconfig and check one item and reboot
Keep doing that till you have found the problem or all are finally checked.
Post back with the results

[fielkun]

The result is negative. I didn't saw any "Sonic" on the StartUp.

But, I unchecked this weird blank space (as you can see on my screenshot above)

[rshaffer61]

Any more BSOD's?

[fielkun]

rshaffer61, on 15 April 2012 - 06:53 AM, said:

Any more BSOD's?

I'm almost done in updating my drivers with DriverMax and yeah, I'm still experiencing this DRIVER IRQL NOT LESS OR EQUAL BSOD

-----
Here's a latest report of WhoCrashed:


Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Mon 4/16/2012 5:03:35 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041612-01.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Sun 4/15/2012 12:59:47 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041512-04.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Sun 4/15/2012 10:39:33 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041512-03.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Sun 4/15/2012 6:00:01 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041512-02.dmp
This was probably caused by the following module: atapi.sys (atapi+0x5D23)
Bugcheck code: 0x100000D1 (0xFFFFFFFFDA8F13D2, 0x5, 0x0, 0xFFFFFFFFF847FD23)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Sun 4/15/2012 1:08:14 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041512-01.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Sat 4/14/2012 2:37:56 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041412-02.dmp
This was probably caused by the following module: atapi.sys (atapi+0x5D26)
Bugcheck code: 0x100000D1 (0x10, 0x5, 0x0, 0xFFFFFFFFF847FD26)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Sat 4/14/2012 12:00:29 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041412-01.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Fri 4/13/2012 11:01:17 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041312-02.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Fri 4/13/2012 10:44:01 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041312-01.dmp
This was probably caused by the following module: sf.sys (sf+0x957)
Bugcheck code: 0xE7 (0x2, 0xFFFFFFFF81375930, 0xFFFFFFFFF87C9E20, 0x0)
Error: INVALID_FLOATING_POINT_STATE
file path: C:\WINDOWS\system32\drivers\sf.sys
product: Sonic Focus DSP service driver
company: Sonic Focus, Inc
description: DSP service driver 08-28-2004 build for SF 1.X
Bug check description: This indicates that a thread's saved floating-point state is invalid.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: sf.sys (DSP service driver 08-28-2004 build for SF 1.X, Sonic Focus, Inc).
Google query: sf.sys Sonic Focus, Inc INVALID_FLOATING_POINT_STATE




On Thu 4/12/2012 1:15:44 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041212-03.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Thu 4/12/2012 7:41:55 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041212-02.dmp
This was probably caused by the following module: hal.dll (hal+0x8A9A)
Bugcheck code: 0x1000000A (0xFFFFFFFFB0C38008, 0x5, 0x1, 0xFFFFFFFF80746A9A)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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.


On Thu 4/12/2012 1:08:03 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041212-01.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Wed 4/11/2012 2:55:57 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041112-04.dmp
This was probably caused by the following module: atapi.sys (atapi+0x85F7)
Bugcheck code: 0x100000D1 (0xC, 0x5, 0x1, 0xFFFFFFFFF84825F7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.


On Wed 4/11/2012 11:38:56 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041112-03.dmp
This was probably caused by the following module: hal.dll (hal+0x8A9A)
Bugcheck code: 0x1000000A (0xFFFFFFFFFB0E2B28, 0x5, 0x1, 0xFFFFFFFF80746A9A)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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.


On Wed 4/11/2012 8:34:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041112-02.dmp
This was probably caused by the following module: sf.sys (sf+0x957)
Bugcheck code: 0xE7 (0x0, 0x0, 0x0, 0x0)
Error: INVALID_FLOATING_POINT_STATE
file path: C:\WINDOWS\system32\drivers\sf.sys
product: Sonic Focus DSP service driver
company: Sonic Focus, Inc
description: DSP service driver 08-28-2004 build for SF 1.X
Bug check description: This indicates that a thread's saved floating-point state is invalid.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: sf.sys (DSP service driver 08-28-2004 build for SF 1.X, Sonic Focus, Inc).
Google query: sf.sys Sonic Focus, Inc INVALID_FLOATING_POINT_STATE





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

26 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

sf.sys (DSP service driver 08-28-2004 build for SF 1.X, Sonic Focus, Inc)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

[rshaffer61]

OK then it's time to take this head on.



Go Start and then to Run ("Start Search" in Vista),
Type in: sfc /scannow
Click OK (Enter in Vista).
Have Windows CD/DVD handy.
If System File Checker (sfc) finds any errors, it may ask you for the CD/DVD.
If sfc does not find any errors in Windows XP, it will simply quit, without any message.
In Vista you will receive the following message: "Windows resource protection did not find any integrity violations".

For Vista users ONLY: Navigate to C:\Windows\Logs\CBS folder. You'll see CBS.log file.
Usually, it's pretty big file, so upload it to Flyupload, and post download link.


If you don't have Windows CD....
This applies mostly to Windows XP, since Vista rarely requires use of its DVD while running "sfc"
Note This method will not necessarily work as well, as when using Windows CD, because not always ALL system files are backed up on your hard drive. Also, backed up files may be corrupted as well.

Go Start and then Run
type in regedit and click OK


Navigate to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup

You will see various entries Values on the right hand side.

The one we want is called: SourcePath

It probably has an entry pointing to your CD-ROM drive, usually D and that is why it is asking for the XP CD.
All we need to do is change it to: C:
Now, double click the SourcePatch setting and a new box will pop up.
Change the drive letter from your CD drive to your root drive, usually C:
Close Registry Editor.

Now restart your computer and try sfc /scannow again!


Thanks to Broni for the instructions


This hopefully will replace the corrupted Atapi.sys file to stop the main BSOD creator.