BSOD playing skyrim and webcamming

[jayman123]

this is the stop code that pops up when my computer crashes while on webcam

0x00000101
(0x0000000000000031,
0x0000000000000000,
0xFFFFF88002FD3180,
0x0000000000000003)

I have no idea what any of that means....and this is what I get when playing skyrim

I get an 0x124 stop code but I haven't gotten that in awhile

I don't know of any fixes so if someone knows of a fix I would be grateful....

 

[JMH]

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP


We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.


You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

​

 

[zigzag3143]

Both 101 and 124 are hardware complaints. We need the dmp files to find out the details.

 

[jayman123]

Debug session time: Fri Apr 20 23:32:52.663 2012 (UTC - 5:00)
System Uptime: 0 days 2:08:50.458
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88002fd3180, 3}

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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002fd3180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.

Debugging Details:
------------------


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: FacebookVideoC

CURRENT_IRQL: d

STACK_TEXT:
fffff880`0a0daa58 fffff800`02f28a3a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02fd3180 : nt!KeBugCheckEx
fffff880`0a0daa60 fffff800`02edb7f7 : fffff800`00000000 fffff800`00000003 00000000`00002710 00001247`ecd632e1 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`0a0daaf0 fffff800`02e16895 : fffff800`02e3c460 fffff880`0a0daca0 fffff800`02e3c460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0a0dabf0 fffff800`02ece1d3 : 00000000`00000246 fffff880`0a0dac01 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0a0dac20 00000000`74df2cfa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
00000000`0a48fe64 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74df2cfa


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_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *

 

[jayman123]

dump files

Debug session time: Fri Apr 20 23:32:52.663 2012 (UTC - 5:00)
System Uptime: 0 days 2:08:50.458
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88002fd3180, 3}

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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002fd3180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.

Debugging Details:
------------------


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: FacebookVideoC

CURRENT_IRQL: d

STACK_TEXT:
fffff880`0a0daa58 fffff800`02f28a3a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02fd3180 : nt!KeBugCheckEx
fffff880`0a0daa60 fffff800`02edb7f7 : fffff800`00000000 fffff800`00000003 00000000`00002710 00001247`ecd632e1 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`0a0daaf0 fffff800`02e16895 : fffff800`02e3c460 fffff880`0a0daca0 fffff800`02e3c460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0a0dabf0 fffff800`02ece1d3 : 00000000`00000246 fffff880`0a0dac01 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0a0dac20 00000000`74df2cfa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
00000000`0a48fe64 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74df2cfa


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_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *

 

[jayman123]

oops sorry posted twice

 

[zigzag3143]

oops sorry posted twice

Thanks but we need the actual DMP files not the analysis, as we can manipulate the data in them

 

[jayman123]

heres my system info

 

[jayman123]

and I believe this is my mini dump

 

[jayman123]

I followed the steps so if this is wrong let me know

 

[zigzag3143]

I followed the steps so if this is wrong let me know

Two issues

1-asacpi.sys. Yours is from 2005

Asacpi.sys

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (not before).

2-Other old drivers really needing updating

ASACPI.sys    3/27/2005 10:30:36 PM        fffff880`02d49000    fffff880`02d51000    0x00008000    0x42476c4c                        
copperhd.sys    5/23/2006 11:51:13 PM        fffff880`06a00000    fffff880`06a03600    0x00003600    0x4473d831                        
Lycosa.sys    1/18/2008 4:51:42 AM        fffff880`0581f000    fffff880`05823980    0x00004980    0x4790689e                        
RimSerial_AMD64.sys    11/24/2008 1:01:01 PM        fffff880`048d9000    fffff880`048e0c00    0x00007c00    0x492addcd

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[jayman123]

I think it worked!!! I'm on webcam now and it hasnt crashed!!!!

 

[zigzag3143]

I think it worked!!! I'm on webcam now and it hasnt crashed!!!!

Good job and good luck

 

[JMH]

Very good!

 

[jayman123]

so I had another BSOD just now....and when I went to compress the .dmp file it says I don't have permission or no reading rights....so i'd post it but I don't know what to do

 

[jayman123]

nvm found it

 

[jayman123]

system info

heres my updated info, please get back to me as soon as you can

 

[JMH]

Your crash was a STOP 0x101 error.
Please refer to the link below for more information.

http://www.sevenforums.com/crash-lo..._watchdog_timeout-troubleshtg.html#post567135

 

[jayman123]

dang I don't know what to do....thank you anyways

 

[jayman123]

I just ran a stress test and got a new kind of dump file, my computer shut off, wouldnt turn back on for about 5 mins, and then when it did it didnt boot windows then after waiting 10 mins it worked