BSOD problem


Joined
Jan 25, 2012
Messages
2
Reaction score
0
Hello,
last two days my system crashed a few times. When I go to shut down Windows (click Shutdown) appears to me BlueScreen and writes the following:
***
Signature of the problem:
Event name that describes the problem: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
ID of regional settings: 1050

Additional information about the problem:
BCCode: 101
BCP1: 0000000000000021
BCP2: 0000000000000000
BCP3: FFFFF88003288180
BCP4: 0000000000000005
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C: \ Windows \ Minidump \ 012512-19531-01.dmp
C: \ Users \ Boris \ AppData \ Local \ Temp \ WER-47 096-0.sysdata.xml

Our privacy statement read on the internet:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x041a

If a privacy notice is available on the Internet, read offline:
C: \ Windows \ system32 \ en \ erofflps.txt

****
Any sugesstion?
Help, please!
 

Attachments

Ace

Microsoft MVP
Joined
Jul 7, 2011
Messages
314
Reaction score
61
Summary:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {21, 0, fffff88003288180, 5}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000021, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003288180, The PRCB address of the hung processor.
Arg4: 0000000000000005, 0.
Debugging Details:
------------------
 
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_6_PROC
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  d
STACK_TEXT:  
fffff800`00b9ca28 fffff800`02f298c9 : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`03288180 : nt!KeBugCheckEx
fffff800`00b9ca30 fffff800`02edc497 : 00000000`00000000 fffff800`00000005 00000000`00026160 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff800`00b9cac0 fffff800`02e16895 : fffff800`02e3c460 fffff800`00b9cc70 fffff800`02e3c460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`00b9cbc0 fffff800`02ece173 : fffffa80`08891000 00000000`00000001 fffff800`0304bde0 00000000`00000003 : hal!HalpHpetClockInterrupt+0x8d
fffff800`00b9cbf0 fffff800`02ec9942 : fffff800`03047e80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x32
 
STACK_COMMAND:  kb
SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME:  Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
BugCheck CLOCK_WATCHDOG_TIMEOUT 0x101

This one could be difficult to resolve as we may be dealing with a deadlock with your processor on this one.

Code:
AMD Phenom(tm) II X6 1090T Processor
Firstly, make sure that you're computer is clean of any dust though.

Possible causes here may include:
- BIOS inconfiguration
- driver causing processor deadlock
- hardware fault (temp, voltage, dust, RFI, etc...)
- *Possible CPU fault

Code:
[BIOS Information (Type 0) - Length 24 - Handle 0000h]
  Vendor                        American Megatrends Inc.
  BIOS Version                  P1.10
  BIOS Starting Address Segment f000
  BIOS Release Date             08/31/2011
  BIOS ROM Size                 100000
  BIOS Characteristics
       07: - PCI Supported
       11: - Upgradeable FLASH BIOS
       12: - BIOS Shadowing Supported
       15: - CD-Boot Supported
       16: - Selectable Boot Supported
       17: - BIOS ROM Socketed
       19: - EDD Supported
       23: - 1.2MB Floppy Supported
       24: - 720KB Floppy Supported
       25: - 2.88MB Floppy Supported
       26: - Print Screen Device Supported
       27: - Keyboard Services Supported
       28: - Serial Services Supported
       29: - Printer Services Supported
       30: - CGA/Mono Services Supported
       32: - BIOS Vendor Reserved
  BIOS Characteristic Extensions
       00: - ACPI Supported
       01: - USB Legacy Supported
       04: - LS120-Boot Supported
       05: - ATAPI ZIP-Boot Supported
       08: - BIOS Boot Specification Supported
       09: - Fn-Key NET-Boot Supported
       10: - Specification Reserved
  BIOS Major Revision           8
  BIOS Minor Revision           15
  EC Firmware Major Revision    255
  EC Firmware Minor Revision    255
[System Information (Type 1) - Length 27 - Handle 0001h]
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
  Version                       To Be Filled By O.E.M.
  Serial Number                                       
  UUID                          00000000-0000-0000-0000-000000000000
  Wakeup Type                   Power Switch
  SKUNumber                     To Be Filled By O.E.M.
  Family                        To Be Filled By O.E.M.
[BaseBoard Information (Type 2) - Length 15 - Handle 0002h]
  Manufacturer                  ASRock
  Product                       890GX Extreme4
  Version                                             
  Serial Number                                       
  Asset Tag                                           
  Feature Flags                 09h
       -337676968: - h
       -337677016: - 
  Location                                            
  Chassis Handle                0003h
  Board Type                    0ah - Processor/Memory Module
  Number of Child Handles       0
[System Enclosure (Type 3) - Length 21 - Handle 0003h]
  Manufacturer                  To Be Filled By O.E.M.
  Chassis Type                  Desktop
  Version                       To Be Filled By O.E.M.
  Serial Number                                       
  Asset Tag Number                                    
  Bootup State                  Safe
  Power Supply State            Safe
  Thermal State                 Safe
  Security Status               None
  OEM Defined                   0
  Height                        0U
  Number of Power Cords         1
  Number of Contained Elements  0
  Contained Element Size        0
[Processor Information (Type 4) - Length 42 - Handle 0004h]
  Socket Designation            CPUSocket
  Processor Type                Central Processor
  Processor Family              01h - Other
  Processor Manufacturer        AMD              
  Processor ID                  a00f1000fffb8b17
  Processor Version             AMD Phenom(tm) II X6 1090T Processor                
  Processor Voltage             8fh - 1.5V
  External Clock                200MHz
  Max Speed                     3439MHz
  Current Speed                 3439MHz
  Status                        Enabled Populated
  Processor Upgrade             Socket 940
  L1 Cache Handle               0005h
  L2 Cache Handle               0006h
  L3 Cache Handle               0007h
  Serial Number                                       
  Asset Tag Number                                    
  Part Number                   To Be Filled By O.E.M.
1) Driver Verifier: Note make sure you backup your data first
If you have access to another computer you can contact us through your other working system in case any problems prevent you from getting into Windows. Make a System Restore point as well.

A startup repair disk may assist you in a system restore during boot if you can't get into Windows as well. 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 CD/DVD or the "Repair your computer" option in the F8/Safe mode boot menu

Follow these steps:
- Go to Start and type in "verifier.exe" 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.

Note: If Norton Antivirus is installed, do not enable Driver Verifier's Deadlock Detection

Reboot the system and wait for it to crash to the BSOD. 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 make sure to let it run for at least 48 hours.

Reboot into Windows after the crash once again and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, or by opening a command prompt and typing in: "verifier /reset" without the quotes. If for some reason you can't get into Windows after the crash and reboot, try booting up in Safe Mode, then try these options to disable Driver Verifier from there.

If you can't get into Windows because it crashes too soon, it is recommended to try it in Safe Mode or boot from Last Known Good Configuration.
If you can't get into Safe Mode, try using System Restore from your installation DVD or startup repair menu to set the system back to the previous restore point that you created.

Make sure your minidumps are enabled so Driver Verifier can output one to the location for you, and post it so I can review it.
 
Last edited:
Joined
Jan 25, 2012
Messages
2
Reaction score
0
Ace Thank you,
I managed to solve the problem according to the instructions you have given me.
BSOD caused fneturpx.sys files in C: \ Windows \ System32 \ drivers
Fnet Corporation Company.
Uninstalling the program I was able to solve the problem.
Once again, thank you.
 

Ace

Microsoft MVP
Joined
Jul 7, 2011
Messages
314
Reaction score
61
Ace Thank you,
I managed to solve the problem according to the instructions you have given me.
BSOD caused fneturpx.sys files in C: \ Windows \ System32 \ drivers
Fnet Corporation Company.
Uninstalling the program I was able to solve the problem.
Once again, thank you.
Okay, haha. Cheers then! :)

If you experience any further issues, just post the newer dump files here.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top