![]() |
![]() |
![]() |
|||||
![]() |
![]() |
![]() |
![]() |
![]() |
|||
| Welcome
to Tech Support Forum home to more then 136,000 problems solved. Issues
have included: Spyware, Malware, Virus Issues, Windows, Microsoft,
Linux, Networking, Security, Hardware, and Gaming Getting your
problem solved is as easy as: 1. Registering for a free account 2. Asking your question 3. Receiving an answer Registered members: * See fewer ads. * And much more..
|
|
| Want to know how to post a question? click here | Having problems with spyware and pop-ups? First Steps |
|
|||||||
![]() |
|
|
LinkBack | Thread Tools |
|
|
#1 (permalink) |
|
Registered User
Join Date: Sep 2008
Posts: 5
OS: Vista 86x
|
[SOLVED] Daily BSOD's
Over the past month or so I've been frequently getting BSOD's. So I formated, driver installs were in this order, nVidia 178.13 Vista 86x, then nVidia nForce 15.23 Vista 86x. Then SP1, then ran windows update, and installed all updates. I was heasetant about installing the WU raid driver, because some one said some where that it might cause conflicts with the nForce ones or some crap. Possible programs installed that could cause f'ups are, diskeeper, eset AV, .NET framework 1.1, visual c++ 2005?, superanti spyware, adaware, and a vista codec package. Used ccleaner to see these. In event viewer, main problems are: Alot of "Service Control Manager Eventlog Provider, Event ID 7000, Level: Error", A great lot of "IRQARB: ACPI BIOS does not contain an IRQ for the device in PCI slot (1 through to 20some thing)" And a heap of these... "Event 4385, Servicing. (Windows Servicing failed to complete the process of changing update 950125-8_neutral_PACKAGE from package KB950125(Update) into Staged(Staged) state) But there are a heap of different ones, are those windows update failures?.
Ive googled my problems big time to no avail, tried driver verifyer. It has to be drivers problems, but which ones! video and nforce should be fine...all signs point to windows updates including sp1... This was from my last BSOD: Problem signature: Problem Event Name: BlueScreen OS Version: 6.0.6001.2.1.0.256.1 Locale ID: 3081 Additional information about the problem: BCCode: 1000007e BCP1: C0000005 BCP2: 96DD0F83 BCP3: 80399904 BCP4: 80399600 OS Version: 6_0_6001 Service Pack: 1_0 Product: 256_1 Googled that and one person said some thing about ESET being a root cause. But no verification on this. So many people are having really similar problems. Also, alot of people are claiming its hard disk problems. Any ideas? Running: Vista Ultimate 86x ASUS Striker Extreme QX6700 Quadcore XFX 9800gtx+ 3x 1024mb OCZ PC2 8500 SLI Ready WD 150gb raptor WD 300gb WD 500gb Hitachi 500gb DS OCZ 1040watt i think. Pretty much it, do have a xfi fatality, but I took that out months ago, every time I had drivers for it installed, pc would BSOD... onboard sound works fine, I guesed it was a fault in the card, but now Im thinking it might be fine! Please be able to help some one... this sucks ***. Also, one possible solution I found was disabling some ACPI thingy in device manager in safemode. Disable was greyed out, So i uninstalled it, was said it was a known problem that is with asus or some thing. |
|
|
|
| Important Information |
|
Join the #1 Tech Support Forum Today - It's Totally Free!
TechSupportForum.com is a leading support website for your computer needs. We offer free, friendly and personalized computer support. Why pay to have your computer fixed when you can do it for free. Join TechSupportforum.com Today - Click Here |
|
|
#2 (permalink) |
|
Moderator, Microsoft Support Microsoft MVP
Join Date: Sep 2007
Location: BSOD CENTRAL Southern New Jersey, USA
Posts: 12,631
OS: Windows 7, Vista Ultimate
|
Re: Daily BSOD's
Hi. . .
The information youo posted on the BCC (CugCheck Code) is the STOP error code found on a BSOD. Your bugcheck here is 0x1000007e, 0xc00000005, 0x96DD0F83, 0x80399904, 0x80399600). No probable cause is listed. A bugcheck of 0x1000007e = 0x0000007e = 0x7e = SYSTEM_THREAD_EXCEPTION_NOT_HANDLED and indicates that a system thread generated an exception that the error handler did not catch. The NT STATUS exception here is the first parm inside the parentheses - 0xc0000005 - a memory access violation. The only way that ESET NOD32 would be the problem here is if you had an old version installed - the current version is v3.0. I run it (anti-virus only) and have never had a problem. HERE is the site for ESET NOD32. I'd like to obtain some system info from you and get all of the mini kernel dumps that you have. Please download the attached zip file and extract the batch and exe file to your desktop. Go to your desktop, right-click on the batch file and select run as administrator. You will see the black "DOS" screen appear and scroll, the green status bar screen then the AutoRuns viewer screen - let it scan (look on bottom-left for status - "scanning..."). When AutoRuns is finished, the screen will close. The batch job will take several minutes to run. It will dump the app and system logs, run AutoRuns, msinfo32, dxdiag, driver listings, etc... The output will be in a new folder found within your documents folder named TSF_Vista_Support. Zip the contents of the new folder up and attach to your next post. It is imperative that you run the batch job via right-click/admin level, otherwise it will not have the necessary permission to obtain the dump files nor the dump files. Any ? - please let me know. Regards. . . jcgriff2 . Last edited by jcgriff2; 09-29-2008 at 09:36 PM. |
|
|
|
|
|
#3 (permalink) |
|
Moderator, Microsoft Support Microsoft MVP
Join Date: Sep 2007
Location: BSOD CENTRAL Southern New Jersey, USA
Posts: 12,631
OS: Windows 7, Vista Ultimate
|
Re: Daily BSOD's
One more item after you run the batch file from my last post -
Run the driver verifier. Bring up an Elevated command prompt - START | type cmd.exe | right-click on cmd.exe uptop under programs | Run as Administrator | type verifier & hit enter - the Verifier screen will appear | do the following: Code:
1. Select 2nd option - Create custom settings (for code developers) 2. Select 2nd option - Select individual settings from a full list. 3. Check the boxes• Special Pool • Pool Tracking • Force IRQL checking4. Select last option - Select driver names from a list 5. Click on the Provider heading - sorts list by Provider 6. Check ALL boxes where Microsoft is not the Provider 7. Click on Finish 8. Re-boot I will then need the new dump files created by this BSOD - you can find them in c:\windows\minidump - zip it up and attach. Regards. . . jcgriff2 . |
|
|
|
|
|
#4 (permalink) |
|
Registered User
Join Date: Sep 2008
Posts: 5
OS: Vista 86x
|
Re: Daily BSOD's
Hey mate, thank you so much for your fast reply. I had looked at one of your previous posts about the driver verifier, and I followed those steps to the line. During the reboot, i got a BSOD, with 0x0000007E (0xC0000005, 0x8E73FF83, 0x80399904, 0x803996000) Ive uploaded the info u asked for. I so hope we can fix this, its really depressing...
|
|
|
|
|
|
#5 (permalink) |
|
Registered User
Join Date: Sep 2008
Posts: 5
OS: Vista 86x
|
Re: Daily BSOD's
Sigh, computer froze over night, some times i get no blue screen, its just locked up. and have to reboot. Most of the time it just Winows has shut down unexpectedly. and this again...
Extra information about the problem BCCode: 1000007e BCP1: C0000005 BCP2: 8E73FF83 BCP3: 80399904 BCP4: 80399600 OS Version: 6_0_6001 Service Pack: 1_0 Product: 256_1 sigh, please help.. |
|
|
|
|
|
#6 (permalink) |
|
Moderator, Microsoft Support Microsoft MVP
Join Date: Sep 2007
Location: BSOD CENTRAL Southern New Jersey, USA
Posts: 12,631
OS: Windows 7, Vista Ultimate
|
Re: Daily BSOD's
Hi. . .
I picked up of the files and will process the dumps. Are the two BSODs contained in your last two posts from the same crash? I ask as the error codes are identical right down to the memory addresses listed... rare. Regards. . . JC . |
|
|
|
|
|
#7 (permalink) |
|
Moderator, Microsoft Support Microsoft MVP
Join Date: Sep 2007
Location: BSOD CENTRAL Southern New Jersey, USA
Posts: 12,631
OS: Windows 7, Vista Ultimate
|
Re: Daily BSOD's
Hi. . .
The verifier-enabled dumps did in fact flag a driver. The bugcheck on the verifier dumps was 0x1000007e (0xc0000005, 0x8e73ff83, 0x80399904, 0x80399600), with the probable cause listed as saskutil.sys - a driver belonging to SuperAntiSpyware. I know we already discussed ESET - and I find it to be a fine product. But I suggest that you use the anti-virus only. One that I don't recall if was mentioned or not is Ad-Aware 2007. I found it listed among the loaded modules. Both Superantispyware and Lavasoft Ad-Aware must go. You've got three products involved in a turf war. Please un-install the two post haste. Be sure to re-boot in between each un-install. Now reset the Windows Firewall to its default settings - START | type FirewallSettings.exe into the start search box | click on FirewallSettings.exe above | select the Advanced Tab | click on "Restore Defaults" | Click Apply (if hi-lighted) | Click OK The other 2 dump files were not driver verifier enabled and listed the Vista NT Kernel module ntkrpamp.exe as the probable cause. I have attached the dbug output to this post. I would appreciate it if you would let me know how things turn out. Regards. . . jcgriff2 |
|
|
|
|
|
#8 (permalink) |
|
Registered User
Join Date: Sep 2008
Posts: 5
OS: Vista 86x
|
Re: Daily BSOD's
Hey mate, I got fed up with it, sorry I've taken so long to reply, I got fed up and formated again, I did an extremely careful install. Started with all windows updates, besides video driver. then rebooted, ran update again, found more, did this process multiple times, until it found sp1, until now ive installed sp1 through an exe. After sp1 installed, ran update again, and found a couple more updates. I then installed the latest nforce driver, rebooted, then video driver. Software I have installed now is ccleaner, diskeeper, eset AV only, and some other stuff. So far, no BSOD! Its been running since yesterday, only errors I'm recieving are ACPI ***** quite frequently.... but no BSOD! so I dont really care, and besides ACPI shouldnt be no biggy yeah? its just this:
IRQARB: ACPI BIOS does not contain an IRQ for the device in PCI slot 1 through to 20 some thing, function 0. Please contact your system vendor for technical assistance. I also looked into the whole bug checker thing I took a look my self, It was saying the BSOD's were superanti spyware! So, the only problem I have now, is what spyware software should I now use, Id really like one in conjunction with the windows one. Thanks, Aiden. |
|
|
|
|
|
#9 (permalink) |
|
Moderator, Microsoft Support Microsoft MVP
Join Date: Sep 2007
Location: BSOD CENTRAL Southern New Jersey, USA
Posts: 12,631
OS: Windows 7, Vista Ultimate
|
Re: Daily BSOD's
Windows Defender should be adequate along with Windows Firewall. Your choice as to a/v program.
Glad this is solved. SuperAntiSpyware was flagged by the verifier and was most certainly a problem within your system. Good Luck to you. Regards. . . jcgriff2 . |
|
|
|
![]() |
| Thread Tools | |
|
|