Sign in with
Sign up | Sign in
Your question

re blue screen every 15 minutes and computer freezing?

Last response: in Windows Vista
Share
October 9, 2013 4:51:21 PM

Hello I am geting a bluescreen every 15 minutes on my Sony Vaio VGN-NR38M.
I am using Vista 32 SP2 2GB Ram.

The following bluescreen code appearered after a shutdown bccode 1a BCP1: 00000030 BCP2: 88629D90 BCP3: 87897000 BCP4: BDF55A6C.,

I have CHDSK several times it delete some stuff sys files restores the sys files then the machine restarts then it runs for a bit then either the everything stops the cursor doesn’t move and light for the hard drive doesn’t flash at all or I blue screen with the above message.

The last big things I did were
1. Updated AVG 2013 to AVG 2014 .
2. I ran the Fix performance option for AVG 2014 to fix registry it did minor work to the registry.
3. Also disabled Superfetch as I found svchost.exe was using over 500k of memory increasing incrementally so the screen went blue and I got a kernel stack error. I Googled the Svchost.exe problem and found it was Superfetch, so I stopped it and memory usage went down.

Any help appreciated.


Yours

Farhan
October 9, 2013 5:03:55 PM

take power off your pc. take the battery out.check that the ram is seated. run memtest from a boot disk and test your ram. run hd tune look for bad hard drive.
m
0
l
October 10, 2013 9:05:12 AM

smorizio said:
take power off your pc. take the battery out.check that the ram is seated. run memtest from a boot disk and test your ram. run hd tune look for bad hard drive.


Hello I did what you said and there were no problems then I found a program called Blue Screen viewer. This software translated Blue screen errors/ minidump to more user-friendly screen making it easier to read. I found out I had Kernel problem and I ran SFC/scannow. This appears to have solved my problem.

Do you think it could something else?

yours

Farhan
m
0
l
Related resources
October 10, 2013 10:09:29 AM

Blue screens are caused by faulty hardware or faulty hardware drivers.



To See if a Fix is Available

In Control Panel (and select Classic view in the left hand pane) choose Problem Reports and Solutions (type problem in Start's search box), go to Problem History, right click your error and choose Check For Solution. You may also right click and choose Details for more info. Post those details here.



To See if a Recent System Change Caused It

In Control Panel (and select Classic view in the left hand pane) choose Administrative Tools then choose Reliability and Performance Monitor and choose Monitoring Tools then Reliability Monitor (type Reliability in search on Start) . This list is a chart of software installs, uninstalls, Windows updates, and crashes by date (scroll left to see earlier dates). See if your crashes started happening after you installed or uninstalled something.


Standard Hardware Troubleshooting


First lets test what hardware we can. Hardware faults can appear as many software faults, therefore we need to test hardware first..

Please do the following in order. Memory faults can cause disk corruption, disk faults can cause disk corruption. Disk corruption causes corrupted files (which SFC may be able to fix). If you get an hardware error stop and post back. Do not run chkdsk with faulty memory.


Memory Diagnostic
If you haven't run a memory diagnostic then please do so. Click Start - Control Panel - choose Classic View in left hand pane - choose Administrative Tools - then Memory Diagnostics Tool.

S.M.A.R.T
Start - All Programs - Accessories - Right click Command Prompt and choose Run As Administrator. Type (or copy and paste by right clicking in the Command Prompt window and choosing Paste).

Disk drives in Windows monitor themselves for impending failure. The feature is called S.M.A.R.T. It will detect impending failure 30% of the time. In an elevated command prompt type (it's one line)

wmic /namespace:\\root\wmi PATH MSStorageDriver_FailurePredictStatus get active,predictfailure,reason /format:List

If it's on Active will be true, if not on turn it on in the computer's BIOS.

Predict Failure should be False if everything's ok.

In Vista and later if SMART predicts failure Windows prompts the user to run Backup.

Run Chkdsk
In Computer right click all your drives and choose Properties, then Tools tab, then click Check Now. Tick BOTH checkboxes then Start. Reboot. This will take overnight.


SFC
Check for file corruption by clicking Start - All Programs - Accessories - Right click Command Prompt and choose Run As Administrator. Type (or copy and paste by right clicking in the Command Prompt window and choosing Paste).

sfc /scannow

Heat
Heat can cause problems like this and also sudden reboots without crashing. Ensure your fans are not clogged with dust.

For Memory Diagnostic Results
Click Start - Control Panel (and select Classic view in the left hand pane) choose Administrative Tools then Event Viewer then look at Event Viewer (Local) - Applications and Services - Microsoft - Windows - MemoryDiagnostic-Results for entries.

Look for EventID is 1201 or 1101 and Source is MemoryDiagnostic-Results

Double click the entry for details on that entry.

For Chkdsk Results
Click Start - Control Panel (and select Classic view in the left hand pane) choose Administrative Tools then Event Viewer then look at both the Application and System logs (under Windows Logs) for entries.

Look for EventID is 7 and Source is Disk
Look for EventID is 11 and Source is Disk
Look for EventID is 50 and Source is Disk
Look for EventID is 51 and Source is Disk
Look for EventID is 52 and Source is Disk
Look for EventID is 55 and Source is NTFS
Look for EventID is 130 and Source is NTFS
Look for EventID is 134 and Source is NTFS
Look for EventID is 137 and Source is NTFS
Look for EventID is 1001 and Source is Autochk
Look for EventID is 1001 and Source is Winlogon
Look for EventID is 1001 and Source is WinInit
Look for EventID is 1001 and Source is Chkdsk
Look for EventID is 26212 and Source is Chkdsk

Look for EventID is 26213 and Source is Chkdsk
Look for EventID is 26214 and Source is Chkdsk

Double click the entry for details on that entry.

P.S. 7 and 55 are the auto repair codes where windows repairs disk errors silently on the fly. 52 is the SMART warning.

If the results don't get transferred to the event logs from a boot time chkdsk then the results are probably in the following file c:\Bootex.log. This file gets deleted when the results are moved into the event logs.

For SFC Results
Start - All Programs - Accessories - Right click Command Prompt and choose Run As Administrator. Type (or copy and paste by right clicking in the Command Prompt window and choosing Paste).

findstr /c:"[SR] Cannot" %windir%\logs\cbs\cbs.log|more

This will see which files are corrupted.

To see if it did anything

findstr /c:"[SR] Repairing" %windir%\logs\cbs\cbs.log|more

There are frequent false positives for small text files Windows uses such as desktop.ini and settings.ini. Ignore these.


--------------------------------------------------------------------------------


Dump Files

Dump files are files containing the state of the machine when it crashed. We can analyse the file to identify the driver (or program) causing the crash. See the last section on how to get them analysed by a volunteer.

Analyse Dump Files
If you want to analyse your own dump files.

You need to start Explorer as Administrator to access the files in C:\windows\Minidump. Right click Explorer and choose Run As Administrator.

Download and install Debugging Tools for Windows

http://msdn.microsoft.com/en-us/windows/hardware/hh8523...

Install theWindows SDK but just choose the debugging tools.

Create a folder called Symbols in C:\

Start Windbg. File menu - Symbol File Path and enter

srv*C:\symbols*http://msdl.microsoft.com/download/symbols

Close and reopen WinDbg. File menu - Open Crash Dump

This will analyse the crash dump. You need to close and reopen WinDbg for each dump file analysed. Because you are downloading symbols from the internet WinDbg will appear to be doing nothing. But it's downloading. Be patient.

You are looking for a driver or system library that the crash occurred in at the end of the listing. Find the file, right click then Properties - Details tab. If it shows a driver you'll need to update the driver identified. Most drivers are in c:\windows\system32\drivers.

Search the Drive for a File.
Click Start - All Programs - Accessories - Right click Command Prompt and choose Run As Administrator. Type replacing drivername.sys with the name of the file being searched (or copy and paste by right clicking in the Command Prompt window and choosing Paste).


dir c:\drivername.sys /a /s


If it shows a system file see if you can get a program from analyze -v.

Type in theWinDbg command prompt

!analyze -v

-v stands for Verbose and if the crash was originated by a program, as opposed to hardware or a driver, it will appear in the middle of the listing.

eg

PROCESS_NAME: java.exe
IMAGE_NAME: ntkrnlmp.exe

PROCESS_NAME only appears in the analyze -v output and only if a program originated the call that faulted.


--------------------------------------------------------------------------------


Upload Them for Analysis

Or upload the minidump files to your Public folder on Skydrive and copy the link from the address bar and I'll analyse them.

Skydrive is Microsoft's Windows Live file upload site at https://skydrive.live.com/. Read about it at http://explore.live.com/skydrive.

If you have downloaded any of the Live applications or have a web based Live mail account you already have access to your Skydrive.

Put your event list in the Public folder and copy the link from the address bar.

.
--
m
0
l
October 10, 2013 1:51:04 PM

David Candy said:
Blue screens are caused by faulty hardware or faulty hardware drivers.



To See if a Fix is Available

In Control Panel (and select Classic view in the left hand pane) choose Problem Reports and Solutions (type problem in Start's search box), go to Problem History, right click your error and choose Check For Solution. You may also right click and choose Details for more info. Post those details here.



To See if a Recent System Change Caused It

In Control Panel (and select Classic view in the left hand pane) choose Administrative Tools then choose Reliability and Performance Monitor and choose Monitoring Tools then Reliability Monitor (type Reliability in search on Start) . This list is a chart of software installs, uninstalls, Windows updates, and crashes by date (scroll left to see earlier dates). See if your crashes started happening after you installed or uninstalled something.


Standard Hardware Troubleshooting


First lets test what hardware we can. Hardware faults can appear as many software faults, therefore we need to test hardware first..

Please do the following in order. Memory faults can cause disk corruption, disk faults can cause disk corruption. Disk corruption causes corrupted files (which SFC may be able to fix). If you get an hardware error stop and post back. Do not run chkdsk with faulty memory.


Memory Diagnostic
If you haven't run a memory diagnostic then please do so. Click Start - Control Panel - choose Classic View in left hand pane - choose Administrative Tools - then Memory Diagnostics Tool.

S.M.A.R.T
Start - All Programs - Accessories - Right click Command Prompt and choose Run As Administrator. Type (or copy and paste by right clicking in the Command Prompt window and choosing Paste).

Disk drives in Windows monitor themselves for impending failure. The feature is called S.M.A.R.T. It will detect impending failure 30% of the time. In an elevated command prompt type (it's one line)

wmic /namespace:\\root\wmi PATH MSStorageDriver_FailurePredictStatus get active,predictfailure,reason /format:List

If it's on Active will be true, if not on turn it on in the computer's BIOS.

Predict Failure should be False if everything's ok.

In Vista and later if SMART predicts failure Windows prompts the user to run Backup.

Run Chkdsk
In Computer right click all your drives and choose Properties, then Tools tab, then click Check Now. Tick BOTH checkboxes then Start. Reboot. This will take overnight.


SFC
Check for file corruption by clicking Start - All Programs - Accessories - Right click Command Prompt and choose Run As Administrator. Type (or copy and paste by right clicking in the Command Prompt window and choosing Paste).

sfc /scannow

Heat
Heat can cause problems like this and also sudden reboots without crashing. Ensure your fans are not clogged with dust.

For Memory Diagnostic Results
Click Start - Control Panel (and select Classic view in the left hand pane) choose Administrative Tools then Event Viewer then look at Event Viewer (Local) - Applications and Services - Microsoft - Windows - MemoryDiagnostic-Results for entries.

Look for EventID is 1201 or 1101 and Source is MemoryDiagnostic-Results

Double click the entry for details on that entry.

For Chkdsk Results
Click Start - Control Panel (and select Classic view in the left hand pane) choose Administrative Tools then Event Viewer then look at both the Application and System logs (under Windows Logs) for entries.

Look for EventID is 7 and Source is Disk
Look for EventID is 11 and Source is Disk
Look for EventID is 50 and Source is Disk
Look for EventID is 51 and Source is Disk
Look for EventID is 52 and Source is Disk
Look for EventID is 55 and Source is NTFS
Look for EventID is 130 and Source is NTFS
Look for EventID is 134 and Source is NTFS
Look for EventID is 137 and Source is NTFS
Look for EventID is 1001 and Source is Autochk
Look for EventID is 1001 and Source is Winlogon
Look for EventID is 1001 and Source is WinInit
Look for EventID is 1001 and Source is Chkdsk
Look for EventID is 26212 and Source is Chkdsk

Look for EventID is 26213 and Source is Chkdsk
Look for EventID is 26214 and Source is Chkdsk

Double click the entry for details on that entry.

P.S. 7 and 55 are the auto repair codes where windows repairs disk errors silently on the fly. 52 is the SMART warning.

If the results don't get transferred to the event logs from a boot time chkdsk then the results are probably in the following file c:\Bootex.log. This file gets deleted when the results are moved into the event logs.

For SFC Results
Start - All Programs - Accessories - Right click Command Prompt and choose Run As Administrator. Type (or copy and paste by right clicking in the Command Prompt window and choosing Paste).

findstr /c:"[SR] Cannot" %windir%\logs\cbs\cbs.log|more

This will see which files are corrupted.

To see if it did anything

findstr /c:"[SR] Repairing" %windir%\logs\cbs\cbs.log|more

There are frequent false positives for small text files Windows uses such as desktop.ini and settings.ini. Ignore these.


--------------------------------------------------------------------------------


Dump Files

Dump files are files containing the state of the machine when it crashed. We can analyse the file to identify the driver (or program) causing the crash. See the last section on how to get them analysed by a volunteer.

Analyse Dump Files
If you want to analyse your own dump files.

You need to start Explorer as Administrator to access the files in C:\windows\Minidump. Right click Explorer and choose Run As Administrator.

Download and install Debugging Tools for Windows

http://msdn.microsoft.com/en-us/windows/hardware/hh8523...

Install theWindows SDK but just choose the debugging tools.

Create a folder called Symbols in C:\

Start Windbg. File menu - Symbol File Path and enter

srv*C:\symbols*http://msdl.microsoft.com/download/symbols

Close and reopen WinDbg. File menu - Open Crash Dump

This will analyse the crash dump. You need to close and reopen WinDbg for each dump file analysed. Because you are downloading symbols from the internet WinDbg will appear to be doing nothing. But it's downloading. Be patient.

You are looking for a driver or system library that the crash occurred in at the end of the listing. Find the file, right click then Properties - Details tab. If it shows a driver you'll need to update the driver identified. Most drivers are in c:\windows\system32\drivers.

Search the Drive for a File.
Click Start - All Programs - Accessories - Right click Command Prompt and choose Run As Administrator. Type replacing drivername.sys with the name of the file being searched (or copy and paste by right clicking in the Command Prompt window and choosing Paste).


dir c:\drivername.sys /a /s


If it shows a system file see if you can get a program from analyze -v.

Type in theWinDbg command prompt

!analyze -v

-v stands for Verbose and if the crash was originated by a program, as opposed to hardware or a driver, it will appear in the middle of the listing.

eg

PROCESS_NAME: java.exe
IMAGE_NAME: ntkrnlmp.exe

PROCESS_NAME only appears in the analyze -v output and only if a program originated the call that faulted.


--------------------------------------------------------------------------------


Upload Them for Analysis

Or upload the minidump files to your Public folder on Skydrive and copy the link from the address bar and I'll analyse them.

Skydrive is Microsoft's Windows Live file upload site at https://skydrive.live.com/. Read about it at http://explore.live.com/skydrive.

If you have downloaded any of the Live applications or have a web based Live mail account you already have access to your Skydrive.

Put your event list in the Public folder and copy the link from the address bar.

.
--


Hello Thank you for your help I have a Drop-box account as I use yahoo mail Here are my files.
https://www.dropbox.com/sh/k1txop65cql4a18/8iNIUt2d9-

Any Help appreciated.

yours

Farhan
m
0
l
October 10, 2013 2:05:58 PM

I have just my latest CBS.log file to my dropbox

yours

Farhan
m
0
l
October 10, 2013 2:55:54 PM

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.

KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:

So I analysed 3. Your CBS log is too big. You'll have to do that yourself.

My guess is it's hardware. Make sure you run the hardware testing. Also test the CPU.

www.intel.com/support/processors/sb/CS-031726.htm

m
0
l
October 11, 2013 1:38:10 PM

Hello

I will Run a CHKDSK/F/R tomorrow. That might work.
Also I ran Sony Hardware Diagnostic utility it went 90% as the disk check was taking a longtime. the RAM was ok and Diks was ok n random seek and other stuff but last option was taknig 2 hours.
should I use the VISTA DVD and try to repair my laptop.

yours

Farhan
m
0
l
October 11, 2013 2:57:41 PM

Hello What If i upgrade to Windows 7 would solve the problem?

yours

Farhan
m
0
l
October 11, 2013 3:20:31 PM

David Candy said:
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.

KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:

So I analysed 3. Your CBS log is too big. You'll have to do that yourself.

My guess is it's hardware. Make sure you run the hardware testing. Also test the CPU.

www.intel.com/support/processors/sb/CS-031726.htm



if I do a CHKDKS/F/R would that help also If Upgraded to Windows 7 could that fix the problem. I ran Sony Hardware Diagnostic tool from startup repair the RAM was fine and Hard disk was ok I stopped at 90% as it was going to take 240+ minutes. Also I have noticed that Windows says the battery indicator says it is not charging , but lights on the front of laptop is flashing like when it is Charging. Then Battery software yesterday went from 30% to 100% in 1 second.

I have 2GB RAM but I cannot go more than that I asked sony last week.

If this helps.

yours

Farhan
m
0
l
October 11, 2013 4:00:47 PM

Upgrading to Windows 7 is just as likely to fix or not fix as reinstalling Windows Vista. As we are not sure what is wrong yet it unknowable.

The amount of memory you have does not cause blue screens. Due to the magic of virtual memory the memory available to you is the amount of free disk space (you do have heaps don't you?). Also Vista 32 bit only uses a bit over 1 GB of physical memory for most uses of a computer.

Finish the hardware testing and test the CPU (it's only 5 mins).

My guess is it's hardware. Make sure you run the hardware testing. Do it overnight. Also test the CPU.

www.intel.com/support/processors/sb/CS-031726.htm

In case it's not hardware do the following two things.


Turn on driver checking.
-----------------------


Driver Verifier

Driver Verifier applies checks to drivers. Normally drivers are trusted to work properly for performance reasons. When a driver breaks the rules the computer will blue screen. The dump file can identify the driver.



Start - All Programs - Accessories - Right click Command Prompt and choose Run As Administrator. Type (or copy and paste by right clicking in the Command Prompt window and choosing Paste).



verifier



In the Wizard choose Create Standard Settings then Automatically Select All Drivers Installed On This Computer. Reboot and wait for next blue screen.



If You Can't Restart
With Driver Verifier you just choose Last Known Good Configuration if it crashes on boot. Type Using Last Known Good Configuration in Start - Help and Support to see how. This will be like Driver Verifier was never run.


After the Crash

Rerun verifier to turn off checking. Upload the dump file.

Clean Boot
----------

Each of the three steps turns of programs, services, and drivers in increasing amounts. Thus narrowing down the possible culprits.



Clean Boot
Click Start - All Programs - Accessories - Run and type

msconfig

Then go to the Startup tab. Untick everything. Then go to the Services tab. Tick Hide All Microsoft Services and untick everything that's left.

Reboot. If this solves your problem reenable ½ of the services/startup items until you find which one.

Advanced Clean Boot
If the above doesn't help.



Download Autoruns from http://technet.microsoft.com/en-us/sysinternals/bb96390...



Start the program by right clicking and choosing Run As Administrator and click Options menu - Filter Options and tick Hide Microsoft entries and clear Include Empty Locations. Untick everything left.



Reboot. If this solves your problem reenable ½ of the items until you find which one.



Safe Mode

If the above doesn't help.

Use Safe Mode with Networking if you need internet access.

Click Start - All Programs - Accessories - Run and type

msconfig

Then go to the Boot tab and click Safe Boot (also tick Network if needed). Reboot. Come back here and untick Safe Boot to return to normal mode.

or

If your computer has a single operating system installed, repeatedly press the F8 key as your computer restarts. You need to press F8 before the Windows logo appears. If the Windows logo appears, you will need to try again. [From Start - Help and Support]
.
--
m
0
l
October 11, 2013 6:32:19 PM

David Candy said:
Upgrading to Windows 7 is just as likely to fix or not fix as reinstalling Windows Vista. As we are not sure what is wrong yet it unknowable.

The amount of memory you have does not cause blue screens. Due to the magic of virtual memory the memory available to you is the amount of free disk space (you do have heaps don't you?). Also Vista 32 bit only uses a bit over 1 GB of physical memory for most uses of a computer.

Finish the hardware testing and test the CPU (it's only 5 mins).

My guess is it's hardware. Make sure you run the hardware testing. Do it overnight. Also test the CPU.

www.intel.com/support/processors/sb/CS-031726.htm

In case it's not hardware do the following two things.


Turn on driver checking.
-----------------------


Driver Verifier

Driver Verifier applies checks to drivers. Normally drivers are trusted to work properly for performance reasons. When a driver breaks the rules the computer will blue screen. The dump file can identify the driver.



Start - All Programs - Accessories - Right click Command Prompt and choose Run As Administrator. Type (or copy and paste by right clicking in the Command Prompt window and choosing Paste).



verifier



In the Wizard choose Create Standard Settings then Automatically Select All Drivers Installed On This Computer. Reboot and wait for next blue screen.



If You Can't Restart
With Driver Verifier you just choose Last Known Good Configuration if it crashes on boot. Type Using Last Known Good Configuration in Start - Help and Support to see how. This will be like Driver Verifier was never run.


After the Crash

Rerun verifier to turn off checking. Upload the dump file.

Clean Boot
----------

Each of the three steps turns of programs, services, and drivers in increasing amounts. Thus narrowing down the possible culprits.



Clean Boot
Click Start - All Programs - Accessories - Run and type

msconfig

Then go to the Startup tab. Untick everything. Then go to the Services tab. Tick Hide All Microsoft Services and untick everything that's left.

Reboot. If this solves your problem reenable ½ of the services/startup items until you find which one.

Advanced Clean Boot
If the above doesn't help.



Download Autoruns from http://technet.microsoft.com/en-us/sysinternals/bb96390...



Start the program by right clicking and choosing Run As Administrator and click Options menu - Filter Options and tick Hide Microsoft entries and clear Include Empty Locations. Untick everything left.



Reboot. If this solves your problem reenable ½ of the items until you find which one.



Safe Mode

If the above doesn't help.

Use Safe Mode with Networking if you need internet access.

Click Start - All Programs - Accessories - Run and type

msconfig

Then go to the Boot tab and click Safe Boot (also tick Network if needed). Reboot. Come back here and untick Safe Boot to return to normal mode.

or

If your computer has a single operating system installed, repeatedly press the F8 key as your computer restarts. You need to press F8 before the Windows logo appears. If the Windows logo appears, you will need to try again. [From Start - Help and Support]
.
--


Hello when I use safe mode with networking no problems. What hardware tool should I use?. If it hardware what could it be? the last thing I installed was AVG 2014 free edition.
m
0
l
!