BSOD A device driver attempting to corrupt the system has been caught.

[ScrumpyDorito]

Windows 7 64
6GB Ram
Nvidia 460 SE
1TB Samsung HDD


I had a blue screen that said " A device driver attempting to corrupt the system has been caught. The faulty driver currently on the kernel stack must be replaced"

I had a look at a bluescreen viewer as well and it says:


"ntoskrnl.exe ntoskrnl.exe+5063dc fffff800`02c67000 fffff800`03250000 0x005e9000 0x4e02aaa3 23/06/2011 02:53:23 Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17640 (win7sp1_gdr.110622-1506) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe"

This is what its saying is causing the BSODS

New dump file for the most recent blue screen after being verified attached as well.

 

[writhziden]

You should remove/update your ideazon drivers: Alpham164.sys and Alpham264.sys; they are a bit old and should be removed/updated. For testing purposes, I would recommend removing them. You can install the latest updates after testing.

After doing the above, run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

You also had a couple BSOD related to memory corruption. Run http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html paying close attention to Parts 2 and 3 of the tutorial.

Then run Driver Verifier. To run Driver Verifier, do the following:
1. http://www.sevenforums.com/tutorials/615-backup-user-system-files.html?filter
2. http://www.sevenforums.com/tutorials/697-system-restore-point-create.html
3. if you do not have a Windows 7 DVD, http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html
4. run http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, use the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.


Edit: Post any BSODs you receive after doing the above, and let us know how Memtest86+ fared.

Also, what antivirus are you running?

Edit2: Do you have mismatched memory modules, i.e. memory modules from two different manufacturers or newer memory modules installed with older memory modules? If so, I would skip the system file check and start with Memtest86+

 

[ScrumpyDorito]

Edit2: Do you have mismatched memory modules, i.e. memory modules from two different manufacturers or newer memory modules installed with older memory modules? If so, I would skip the system file check and start with Memtest86+

I 2gb of ram that was giving to me by a friend. They are the same brand and same Hz, but I will remove them.

Also If errors do come up on the memtest I am going to try out each stick. So it might be a few days.

 

[writhziden]

I 2gb of ram that was giving to me by a friend. They are the same brand and same Hz, but I will remove them.

Also If errors do come up on the memtest I am going to try out each stick. So it might be a few days.

That's fine. Let us know if you need further assistance at any time.

 

[ScrumpyDorito]

I have done a memtest overnight and it came up with 1 error, going to do it again tonight with one stick and see if it fails.

Edit:Forgot to mention that I use Eset Smart Security as an antivirus.

 

[ScrumpyDorito]

I did a memtest and I removed the RAM that was causing the errors. I had another bluescreen mid game telling me SYSTEM_SERVICE_EXCEPTION. Dump files are attached

 

[writhziden]

I did a memtest and I removed the RAM that was causing the errors. I had another bluescreen mid game telling me SYSTEM_SERVICE_EXCEPTION. Dump files are attached

You should try updating your nVidia System Utility Driver. It is a couple years old, and pre Win7.

Also, is it the same game that it always crashes with? Once you have updated the above driver, if the problem persists with the game or any game, run the tests done in post #2 of this linked thread. See if the problem is game related or graphics related.

The blue screens are still memory corruption related, but those can be due to underlying driver issues.

 

[ScrumpyDorito]

I did a memtest and I removed the RAM that was causing the errors. I had another bluescreen mid game telling me SYSTEM_SERVICE_EXCEPTION. Dump files are attached

You should try updating your nVidia System Utility Driver. It is a couple years old, and pre Win7.

Also, is it the same game that it always crashes with? Once you have updated the above driver, if the problem persists with the game or any game, run the tests done in post #2 of this linked thread. See if the problem is game related or graphics related.

The blue screens are still memory corruption related, but those can be due to underlying driver issues.

It BSOD pretty randomly, sometime I can go 2 days without one, but some days I cant boot up because it does it automatically.

Edit: I uninstalled Nvidia system Utility Driver, as well as the 3D Nvision Controller and Drivers.

Edit2: Is there a program I can download that will let me update all my drivers? Preferable a free one, its just so I dont have to google them individually.

 

[zigzag3143]

The majority of these (and driver verified) were Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd

I would remove it

 

[ScrumpyDorito]

The majority of these (and driver verified) were Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd

I would remove it

How do I find this file? Because I uninstalled Daemon Tool lite a while back.

 

[zigzag3143]

The majority of these (and driver verified) were Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd

I would remove it

How do I find this file? Because I uninstalled Daemon Tool lite a while back.

Try searching for it.

It should be in C:\windows\system32\...

 

[ScrumpyDorito]

The majority of these (and driver verified) were Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd

I would remove it

How do I find this file? Because I uninstalled Daemon Tool lite a while back.

Try searching for it.

It should be in C:\windows\system32\...

Edit: I did a search on the registry for any leftover daemon tools, I found dtsoftbus01.sys but it wont let me delete it

I dont see anything in the system32 files pertaining to dtsoftbus01.sys

 

[zigzag3143]

How do I find this file? Because I uninstalled Daemon Tool lite a while back.

Try searching for it.

It should be in C:\windows\system32\...

Edit: I did a search on the registry for any leftover daemon tools, I found dtsoftbus01.sys but it wont let me delete it

I dont see anything in the system32 files pertaining to dtsoftbus01.sys

Where is your copy located?


Have you tried removing it in safe mode (F8)?

 

[ScrumpyDorito]

Its located in the registry in HKEY-LOCALMACHINE/SOFTARE/WOW6432NODE/MICROSOFT/windows/currentversion/setup/PNPLOCKDOWNFILES

It isnt actually installed because it doesnt show in the SYS32 files and no recorded documents, it was only in the registry.

Its still in the registry and it wont let me delete it either even though I ran in as ADMIN. Cant seem to change it to full control when I go into regedit properties.

 

[writhziden]

Its located in the registry in HKEY-LOCALMACHINE/SOFTARE/WOW6432NODE/MICROSOFT/windows/currentversion/setup/PNPLOCKDOWNFILES

It isnt actually installed because it doesnt show in the SYS32 files and no recorded documents, it was only in the registry.

Its still in the registry and it wont let me delete it either even though I ran in as ADMIN. Cant seem to change it to full control when I go into regedit properties.

You need to take ownership of that key. To do so:
1. Click on the Start Menu
2. Type regedit into the Search for programs and files box(do not hit enter)
3. Right click regedit.exe and click Run as administrator
4. Find the key you mention above
5. Right click the key in the left pane
6. Click Permissions
7. Click Advanced
8. Click the Owner tab
9. Select your user from the list below Change owner to:...If your user is not listed under Change owner to:, click Other users or groups... and enter your username exactly as it appears in C:\Users, then select your user from the list
10. Tick the box to Replace owner on subcontainers and objects
11. Hit OK.
12. Select your user from the Group or user names. If your user is not listed, click Add and again type in your user name as it appers in C:\Users, then select your user from the list
13. Tick the box under Allow for full control.
14. Hit OK
15. You should now be able to delete the key.

 

[zigzag3143]

its located in the registry in hkey-localmachine/softare/wow6432node/microsoft/windows/currentversion/setup/pnplockdownfiles

it isnt actually installed because it doesnt show in the sys32 files and no recorded documents, it was only in the registry.

Its still in the registry and it wont let me delete it either even though i ran in as admin. Cant seem to change it to full control when i go into regedit properties.

it is installed for it was loaded.


My apologies Writhziden pointed out your newest does NOT have it. I was wrong

 

[ScrumpyDorito]

Its located in the registry in HKEY-LOCALMACHINE/SOFTARE/WOW6432NODE/MICROSOFT/windows/currentversion/setup/PNPLOCKDOWNFILES

It isnt actually installed because it doesnt show in the SYS32 files and no recorded documents, it was only in the registry.

Its still in the registry and it wont let me delete it either even though I ran in as ADMIN. Cant seem to change it to full control when I go into regedit properties.

You need to take ownership of that key. To do so:
1. Click on the Start Menu
2. Type regedit into the Search for programs and files box(do not hit enter)
3. Right click regedit.exe and click Run as administrator
4. Find the key you mention above
5. Right click the key in the left pane
6. Click Permissions
7. Click Advanced
8. Click the Owner tab
9. Select your user from the list below Change owner to:...If your user is not listed under Change owner to:, click Other users or groups... and enter your username exactly as it appears in C:\Users, then select your user from the list
10. Tick the box to Replace owner on subcontainers and objects
11. Hit OK.
12. Select your user from the Group or user names. If your user is not listed, click Add and again type in your user name as it appers in C:\Users, then select your user from the list
13. Tick the box under Allow for full control.
14. Hit OK
15. You should now be able to delete the key.

I have successfuly deleted the key, should I run driver verifier and post the dump files on here to see if it has been sorted?

 

[zigzag3143]

Its located in the registry in HKEY-LOCALMACHINE/SOFTARE/WOW6432NODE/MICROSOFT/windows/currentversion/setup/PNPLOCKDOWNFILES

It isnt actually installed because it doesnt show in the SYS32 files and no recorded documents, it was only in the registry.

Its still in the registry and it wont let me delete it either even though I ran in as ADMIN. Cant seem to change it to full control when I go into regedit properties.

You need to take ownership of that key. To do so:
1. Click on the Start Menu
2. Type regedit into the Search for programs and files box(do not hit enter)
3. Right click regedit.exe and click Run as administrator
4. Find the key you mention above
5. Right click the key in the left pane
6. Click Permissions
7. Click Advanced
8. Click the Owner tab
9. Select your user from the list below Change owner to:...If your user is not listed under Change owner to:, click Other users or groups... and enter your username exactly as it appears in C:\Users, then select your user from the list
10. Tick the box to Replace owner on subcontainers and objects
11. Hit OK.
12. Select your user from the Group or user names. If your user is not listed, click Add and again type in your user name as it appers in C:\Users, then select your user from the list
13. Tick the box under Allow for full control.
14. Hit OK
15. You should now be able to delete the key.

I have successfuly deleted the key, should I run driver verifier and post the dump files on here to see if it has been sorted?

Yes. Sounds good to me

 

[ScrumpyDorito]

Uploaded are the BSOD dump files after running driver verifier

 

[zigzag3143]

Uploaded are the BSOD dump files after running driver verifier

Driver verified and Related to luafv.sys Sterownik filtru wirtualizacji plików LUA from Microsoft Corporation.