BSOD (most probably because of skype)

[tetlika]

BSOD is happening when skype is running (4th or 5th version - does not matter), the SF tools diagnostic data is attached

 

[tetlika]

can anyone help? please

 

[koolkat77]

You need to wait for someone to see the dumps at least.
Please stop bumping the thread.

 

[koolkat77]

STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR BSOD Index

Usual causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack

One of the dump shows:

DISK_HARDWARE_ERROR: There was error with disk hardware

* To make sure your hard drive is in good condition run:
:ar: http://www.sevenforums.com/tutorials/433-disk-check.html

* Hard drive test both short and long with
:ar: SeaTools for Windows

Please uninstall AVG antivirus.

* Download and install MSE. Run a full scan when updated.
:ar: Microsoft Security Essentials - Free Antivirus for Windows

* For additional security, recommend Malware bytes. (Also run full scan once installed)
:ar: Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer

* System file checker for repairing any damaged files within windows
:ar: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

* Also look for an update on your BIOS version.

BIOS Version/Date	TOSHIBA Version 1.70, 03.03.2010

Post back results

 

[tetlika]

1)checked disk - no errors , disk is ok
2)upgraded bios to latest version
3)checked for viruses - none were found
4) scannow informed that all is ok

but as soon as skype is running and i'm using it - the system crashes after 10-30 minutes

if skype is not running everything's ok

also reinstalled skype, and tryed the 4th version - the same

attached the lattest smalldump

P.S.

in logs found next entry:

Log Name: Application
Source: Windows Error Reporting
Date: 21.09.2012 12:15:01
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: zweb-PC
Description:
Fault bucket X64_0xF4_c0000005_IMAGE_wininit.exe_Win7, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\092112-11232-01.dmp
C:\Users\zweb\AppData\Local\Temp\WER-30357-0.sysdata.xml
C:\Users\zweb\AppData\Local\Temp\WERC2C1.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_06acdc3a

Analysis symbol: X64_0xF4_c0000005_IMAGE_wininit.exe_Win7
Rechecking for solution: 0
Report Id: 092112-11232-01
Report Status: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-09-21T09:15:01.000000000Z" />
<EventRecordID>3523</EventRecordID>
<Channel>Application</Channel>
<Computer>zweb-PC</Computer>
<Security />
</System>
<EventData>
<Data>X64_0xF4_c0000005_IMAGE_wininit.exe_Win7</Data>
<Data>0</Data>
<Data>BlueScreen</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
C:\Windows\Minidump\092112-11232-01.dmp
C:\Users\zweb\AppData\Local\Temp\WER-30357-0.sysdata.xml
C:\Users\zweb\AppData\Local\Temp\WERC2C1.tmp.WERInternalMetadata.xml</Data>
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_06acdc3a</Data>
<Data>X64_0xF4_c0000005_IMAGE_wininit.exe_Win7</Data>
<Data>0</Data>
<Data>092112-11232-01</Data>
<Data>0</Data>
</EventData>
</Event>

 

[koolkat77]

Lets enable driver verifier to rule out buggy drivers.

Driver Verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in verifier and press Enter
- Select Create custom settings (for code developers) and click Next
- Select Select individual settings from a full list and click Next
- Select everything EXCEPT FOR Low Resource Simulation and click Next
- Select Select driver names from a list and click Next
Then select all drivers NOT provided by Microsoft and click Next
- Select Finish on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

 

[tetlika]

have runned verifier for few hours - all ok

have installed a skype beta - so far so good (14 hours no BSOD)

 

[koolkat77]

Okay
Let us know if and when you get a bsod

 

[tetlika]

have BSOD even with beta, without skype running - everything's great

 

[koolkat77]

Alright

Download and install Revo Uninstaller. Uninstall Skype in Advanced mode
remove its registry entries.
:ar: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Download and install a fresh copy of Skype from the link below
:ar: Download Skype 5.10.0.116 - FileHippo.com

 

[tetlika]

hi!

have installed windows 8 x64 , no BSODS for latest 24 hours with skype running

 

[koolkat77]

Okay, I just noticed. You have windows 7 enterprise version. Where did you get it from?

 

[tetlika]

It's my working laptop, and my organization officially purchased the windows
P.S.

why are you asking that?

 

[karlsnooks]

Let you organization get official MS support.
They have an enterprise license.
We do not work on enterprise computers.
Go to your organization's IT department and have them fix your problem on an Enterprise system computer.

 

[tetlika]

It's a long story man. I got staff working on my windows8 preview edition (and it's awesome I must say - much better than windows 7), it will be working for almost 4 months stil. Till that time I'll get new laptop . So for me the problems looks solved for now.

 

[koolkat77]

That's okay.

Will you be installing windows 7 again?

 

[tetlika]

in case of emergency - yes

 

[koolkat77]

Hmm alright.
Let us know if you have the BSoD problems on the fresh install

 

[tetlika]

okay