[xnay]

Hi there!

I am having serious problems with the BS. Recently I have installed and used the Uniblue speed up program. Now my computer (although he is old) has his own brain. I will attach my minidump and hope someone has the solution for my problem. The last thing I want to do is to make a new copy of the OS. Anyone?

Thanx in advance.

[Advertisements]

Does the system boot into windows now?
I see in the other topic MacBoatMaster explained the dangers of the Registry Cleaners which unfortunately you are experiencing now.
If you can boot into windows please do the following.
Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program

[rshaffer61]

Does the system boot into windows now?
I see in the other topic MacBoatMaster explained the dangers of the Registry Cleaners which unfortunately you are experiencing now.
If you can boot into windows please do the following.
Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program

[Macboatmaster]

Thank you for such in-depth reply. I assumed it would be something with that c*rap. So i think the most reasonable thing to do would it be to reinstall OS (and not to use those "programs"):/

I owe you one!
Cheers

From the other thread, which I have now "marked" in respect of your post that you have started this one. The answer to your question as you will have gathered from the reply here by "rshaffer61" is NOT YET - as to reinstall

Edited by Macboatmaster, 03 January 2011 - 03:10 PM.

[xnay]

rshaffer61: here you go



==================================================
Dump File : Mini010311-01.dmp
Crash Time : 1/3/2011 3:18:37 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0xeeacd448
Parameter 3 : 0xf426ab04
Parameter 4 : 0xf426a800
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+3448
File Description : TCP/IP Protocol Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5508 (xpsp.080320-0409)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini010311-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
Dump File Size : 102,400
==================================================

==================================================
Dump File : Mini122710-01.dmp
Crash Time : 12/27/2010 11:57:13 AM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0x804ee900
Parameter 3 : 0xf244aac0
Parameter 4 : 0xf244a7bc
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+109ee
File Description : TCP/IP Protocol Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5508 (xpsp.080320-0409)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini122710-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
Dump File Size : 102,400
==================================================

==================================================
Dump File : Mini121610-01.dmp
Crash Time : 12/16/2010 5:54:17 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0xee3c770c
Parameter 3 : 0xf25c8afc
Parameter 4 : 0xf25c87f8
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+570c
File Description : TCP/IP Protocol Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5508 (xpsp.080320-0409)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini121610-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
Dump File Size : 102,400
==================================================

==================================================
Dump File : Mini052710-01.dmp
Crash Time : 5/27/2010 4:21:25 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf8124ee
Parameter 3 : 0xf03d333c
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+124ee
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5508 (xpsp.080320-1622)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini052710-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
Dump File Size : 102,400
==================================================

[rshaffer61]

Yep we'll see if we can undo the damage first. All of us here at GTG use a format and fresh install as the last resort and very rarely does it come to that.

[xnay]

Yep we'll see if we can undo the damage first. All of us here at GTG use a format and fresh install as the last resort and very rarely does it come to that.

i hope so

[rshaffer61]

Your errors indicate the following:

0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
(Click to consult the online MSDN article.)
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information.

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
(Click to consult the online MSDN article.)
A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

Common factor in both is a DRIVER

If you can boot into windows please do the following:

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 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

[xnay]

So i checked event viewer in very time of last BSOD:
System:

Several "Informations": 2x eventlog and 7sec after --> Save Dump: The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e (0xc0000005, 0xeeacd448, 0xf426ab04, 0xf426a800). A dump was saved in: C:\WINDOWS\Minidump\Mini010311-01.dmp.

For more information, see Help and Support Center at http://go.microsoft....ink/events.asp.


Application: nothing was happening before BSOD.

PS: My system runs ok, maybe a little slower than before the use of "uniblue" when using several Mozilla(standard increase -> 100-200 of RAM usage when i am surfing the internet for longer period) tabs and some Word.


I will try with msconfig right away.

[rshaffer61]

It's defiantly a driver issue. We just have to run it down now.

[xnay]

In starup menu I have following:
ctfmon (only one checked)
AdobeARM
avgtray
NMBgMonitor
ctfmon
DTProAgent
DivXUpdate
GoogleUpdate
GrooveMonitor
dumprep 0 -k
LWS
YahooMessenger
Application Launcher
msmsgs
msnmsgr
NVMixerTray
PCSuite
justshed
GoogleToolbarNotifier
realsched
RegistryBooster
Logitech . Product
OneNote 2007 Screen clipper and Launcher

These all are now unchecked. Half of them were already unchecked.

EDIT:
PS: As the BSOD is not so frequent, is there any other way to analyze the problem with driver than checking the boxes in System Configuration Utility?

Edited by xnay, 03 January 2011 - 07:07 PM.

[rshaffer61]

Did you reboot after unchecking them and if so does the issue still happen?

[xnay]

Yes I have rebooted the system. We must wait for the longer time period for the BSOD. It happens randomly

[rshaffer61]

OK no problem I have time.

[xnay]

I will leave my computer turned on. Now i am going to sleep here is 2.40am
Thanx for your help!

C ya tomorrow

[rshaffer61]

Are you still having problems with your issue?
It has been 4 days since your last response and I was wondering if the issue has been resolved?
If so can you explain how it was resolved so others may be able to fix it if they have the same issue.
If not please let us know and we can continue with helping you to resolve the issue.