BSOD playing skyrim and webcamming

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

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.

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

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

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

oops sorry posted twice

jayman123 said:

oops sorry posted twice

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

heres my system info

and I believe this is my mini dump

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