F FunkyMaggot Member Joined May 13, 2013 Posts 18 May 13, 2013 #1 Hello everyone :wave: I am hoping someone can help me here. I have been suffering blue screens for a couple of months but have only just had the time to really look into them. After checking a couple of guides on analysing windows dump files for windows I found the error CLOCK_WATCHDOG_TIMEOUT_8_PROC on multiple processes (putty, svchost, system and vmware.a). I haven't looked through all the dumps, but the CLOCK_WATCHDOG_TIMEOUT_8_PROC appears in all the ones i checked. I looked this up and found that this could be a processor issue. EDIT: The frequencies of my crashes vary it can be twice a day to a week. It is worth mentioning that my PC was previously overclocked, although blue screens did not appear, the system would freeze. After a couple of months of trying to make the system stable I returned the settings to stock. My motherboard also seems to be having issues recognizing USBdevices on the back ports. I can overcome this by making sure USB devices are plugged in before the machine is booted. For a while I suspected that the USB devices were the cause of the bluescreens, but after disconnecting all USB device and using legacy hardware it still occurred. I am hoping to nail find out what's causing this finally and get the issue resolved. I would replace the motherboard and processor but I would like to be 100% sure on what is causing the crashes. I have attached request files and am in the process of running the additional scans. Please let me know if I have missed anything or if you need further information. My current attempts of debugging my machine: Upgraded BIOS Upgraded drivers (i still have 1 unknown device in device manager) Memtest: -Tested both memeory sticks, A0 A1 -Tested both sticks individually in A0 Windows memeory diagnostic tests -Tested both memeory sticks, A0 A1 -Tested both sticks individually in A0 Malware bytes full scan -nothing detected Antivirus scan with MSE -nothing detected Questions & Answers OS - Windows 7 x64 What was original installed OS on system? Drive was empty, installed windows 7 - myself Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? -No Age of system - 2 years Age of OS installation - 6 months CPU - Intel Core i7 2600K UNLOCKED Video Card - 1280MB MSI GTX570 TWIN FROZR 2 OC MotherBoard - Asrock Z68 Extreme4 Intel Z68 (Socket 1155) DDR3 Motherboard (Corsair Vengeance 8GB) Power Supply - CORSAIR 850W CMPSU-850TXV2 PSU System Manufacturer - myself Attachments info.zip 1.6 MB · Views: 2 Last edited: May 13, 2013
Hello everyone :wave: I am hoping someone can help me here. I have been suffering blue screens for a couple of months but have only just had the time to really look into them. After checking a couple of guides on analysing windows dump files for windows I found the error CLOCK_WATCHDOG_TIMEOUT_8_PROC on multiple processes (putty, svchost, system and vmware.a). I haven't looked through all the dumps, but the CLOCK_WATCHDOG_TIMEOUT_8_PROC appears in all the ones i checked. I looked this up and found that this could be a processor issue. EDIT: The frequencies of my crashes vary it can be twice a day to a week. It is worth mentioning that my PC was previously overclocked, although blue screens did not appear, the system would freeze. After a couple of months of trying to make the system stable I returned the settings to stock. My motherboard also seems to be having issues recognizing USBdevices on the back ports. I can overcome this by making sure USB devices are plugged in before the machine is booted. For a while I suspected that the USB devices were the cause of the bluescreens, but after disconnecting all USB device and using legacy hardware it still occurred. I am hoping to nail find out what's causing this finally and get the issue resolved. I would replace the motherboard and processor but I would like to be 100% sure on what is causing the crashes. I have attached request files and am in the process of running the additional scans. Please let me know if I have missed anything or if you need further information. My current attempts of debugging my machine: Upgraded BIOS Upgraded drivers (i still have 1 unknown device in device manager) Memtest: -Tested both memeory sticks, A0 A1 -Tested both sticks individually in A0 Windows memeory diagnostic tests -Tested both memeory sticks, A0 A1 -Tested both sticks individually in A0 Malware bytes full scan -nothing detected Antivirus scan with MSE -nothing detected Questions & Answers OS - Windows 7 x64 What was original installed OS on system? Drive was empty, installed windows 7 - myself Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? -No Age of system - 2 years Age of OS installation - 6 months CPU - Intel Core i7 2600K UNLOCKED Video Card - 1280MB MSI GTX570 TWIN FROZR 2 OC MotherBoard - Asrock Z68 Extreme4 Intel Z68 (Socket 1155) DDR3 Motherboard (Corsair Vengeance 8GB) Power Supply - CORSAIR 850W CMPSU-850TXV2 PSU System Manufacturer - myself
M muhahaa Windows Specialist Joined Apr 13, 2013 Posts 30 May 13, 2013 #2 Do you have any full/kernel dumps? Minidumps are useless with bugcheck CLOCK_WATCHDOG_TIMEOUT.
F FunkyMaggot Member Joined May 13, 2013 Posts 18 May 13, 2013 #3 Thanks for the reply. UNfortunatly i'm no so savvy with this sort of computing. I've had a quick google and found C:\Windows\MEMORY.DMP, this gave me similar information as the minidumps. Is there anyway for me to enable a more verbose/useful dump file? MEMORY.DMP analysis: Read More: 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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff880009b3180, The PRCB address of the hung processor. Arg4: 0000000000000004, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: vmware-authd.e CURRENT_IRQL: d STACK_TEXT: fffff880`0b9351d8 fffff800`0372ea3a : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`009b3180 : nt!KeBugCheckEx fffff880`0b9351e0 fffff800`036e16e7 : 00000000`00000000 fffff800`00000004 00000000`00002711 fffff800`0380b30d : nt! ?? ::FNODOBFM::`string'+0x4e3e fffff880`0b935270 fffff800`03623895 : fffff800`03649460 fffff880`0b935420 fffff800`03649460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`0b935370 fffff800`036d4153 : fffff800`03852e80 00000000`00000001 00000000`00000001 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d fffff880`0b9353a0 fffff800`036ac90f : 00000000`00000d82 00000000`000002cb 00000000`001b8039 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163 fffff880`0b935530 fffff800`03995e2f : 00000000`00000000 fffff880`0b935b60 00000000`00000000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x6b fffff880`0b9355a0 fffff800`039e44f6 : 00000000`00563160 fffffa80`00008400 fffff880`0b935730 00000000`00000000 : nt!ExpGetProcessInformation+0x7f fffff880`0b9356f0 fffff800`039e4f4d : 00000000`00563160 00000000`00000004 00000000`00000005 ffffffff`fd050f80 : nt!ExpQuerySystemInformation+0xfb4 fffff880`0b935aa0 fffff800`036d6e93 : fffffa80`0b566b50 00000000`00000340 fffff880`0b935ab8 fffffa80`0b5a7590 : nt!NtQuerySystemInformation+0x4d fffff880`0b935ae0 00000000`7704167a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0251e348 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7704167a 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_8_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwne
Thanks for the reply. UNfortunatly i'm no so savvy with this sort of computing. I've had a quick google and found C:\Windows\MEMORY.DMP, this gave me similar information as the minidumps. Is there anyway for me to enable a more verbose/useful dump file? MEMORY.DMP analysis: Read More: 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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff880009b3180, The PRCB address of the hung processor. Arg4: 0000000000000004, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: vmware-authd.e CURRENT_IRQL: d STACK_TEXT: fffff880`0b9351d8 fffff800`0372ea3a : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`009b3180 : nt!KeBugCheckEx fffff880`0b9351e0 fffff800`036e16e7 : 00000000`00000000 fffff800`00000004 00000000`00002711 fffff800`0380b30d : nt! ?? ::FNODOBFM::`string'+0x4e3e fffff880`0b935270 fffff800`03623895 : fffff800`03649460 fffff880`0b935420 fffff800`03649460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`0b935370 fffff800`036d4153 : fffff800`03852e80 00000000`00000001 00000000`00000001 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d fffff880`0b9353a0 fffff800`036ac90f : 00000000`00000d82 00000000`000002cb 00000000`001b8039 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163 fffff880`0b935530 fffff800`03995e2f : 00000000`00000000 fffff880`0b935b60 00000000`00000000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x6b fffff880`0b9355a0 fffff800`039e44f6 : 00000000`00563160 fffffa80`00008400 fffff880`0b935730 00000000`00000000 : nt!ExpGetProcessInformation+0x7f fffff880`0b9356f0 fffff800`039e4f4d : 00000000`00563160 00000000`00000004 00000000`00000005 ffffffff`fd050f80 : nt!ExpQuerySystemInformation+0xfb4 fffff880`0b935aa0 fffff800`036d6e93 : fffffa80`0b566b50 00000000`00000340 fffff880`0b935ab8 fffffa80`0b5a7590 : nt!NtQuerySystemInformation+0x4d fffff880`0b935ae0 00000000`7704167a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0251e348 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7704167a 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_8_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwne
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,245 Location %systemroot% May 13, 2013 #4 To configure a Kernel Memory Dump to be saved, then please follow these steps: Click Start, or press the Windows Flag key on your keyboard. Right-Click Computer, and then select Properties. In the right pane, select Advanced System Settings. In the Advanced tab, select Settings, under the Startup and Recovery group box. Make sure your settings are configured to the same settings seen in my screenshot:
To configure a Kernel Memory Dump to be saved, then please follow these steps: Click Start, or press the Windows Flag key on your keyboard. Right-Click Computer, and then select Properties. In the right pane, select Advanced System Settings. In the Advanced tab, select Settings, under the Startup and Recovery group box. Make sure your settings are configured to the same settings seen in my screenshot:
F FunkyMaggot Member Joined May 13, 2013 Posts 18 May 13, 2013 #5 Thanks for the guide, but it looks like my settings are identical already. Is there anything else I can do o get some more information?
Thanks for the guide, but it looks like my settings are identical already. Is there anything else I can do o get some more information?
M muhahaa Windows Specialist Joined Apr 13, 2013 Posts 30 May 13, 2013 #6 Use the command !running -ti on the kernel dump.
F FunkyMaggot Member Joined May 13, 2013 Posts 18 May 13, 2013 #7 I'm sorry what am I running this on? Running this with WinDbg gives me "Bad register error in 'running -ti'"
I'm sorry what am I running this on? Running this with WinDbg gives me "Bad register error in 'running -ti'"
V Vir Gnarus BSOD Kernel Dump Expert Joined Mar 2, 2012 Posts 474 May 13, 2013 #8 USB problems frequently are caused by motherboard issues. I've often seen that when a mobo is going bad, the USB ports are some of the first items to go on it. You'll want to provide us the actual kernel dump (MEMORY.DMP). Zip up and upload to a 3rd party filesharing site like Mirrorcreator.
USB problems frequently are caused by motherboard issues. I've often seen that when a mobo is going bad, the USB ports are some of the first items to go on it. You'll want to provide us the actual kernel dump (MEMORY.DMP). Zip up and upload to a 3rd party filesharing site like Mirrorcreator.
F FunkyMaggot Member Joined May 13, 2013 Posts 18 May 13, 2013 #9 Hey Guys, The uploaded memory dump can be found below: Read More: https://dl.dropboxusercontent.com/u/5485099/MEMORY.zip
Hey Guys, The uploaded memory dump can be found below: Read More: https://dl.dropboxusercontent.com/u/5485099/MEMORY.zip
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,245 Location %systemroot% May 14, 2013 #10 Code: BugCheck 101, {19, 0, fffff880009b3180, 4} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Code: Usual causes: Device driver, BIOS bug, hardware defect It appears that the processor didn't respond to the clock interrupt within the given time interval. Update: Code: 0: kd> !sysinfo machineid Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=1553] BiosMajorRelease = 4 BiosMinorRelease = 6 BiosVendor = American Megatrends Inc. BiosVersion = P2.20 BiosReleaseDate = 06/29/2012 SystemManufacturer = To Be Filled By O.E.M. SystemProductName = To Be Filled By O.E.M. SystemFamily = To Be Filled By O.E.M. SystemVersion = To Be Filled By O.E.M. SystemSKU = To Be Filled By O.E.M. BaseBoardManufacturer = ASRock BaseBoardProduct = Z68 Extreme4 BaseBoardVersion = Your BIOS seems to be a little dated, I would suggest checking for any BIOS updates for your motherboard, they may have introduced some greater hardware compatibility and stability patches with the newer version. I also noticed a few drivers in the raw stack text for the hung processor, here are my findings: Code: 4: kd> lmvm VBoxNetFlt start end module name fffff880`06eb9000 fffff880`06ee1000 VBoxNetFlt (no symbols) Loaded symbol image file: VBoxNetFlt.sys Image path: \SystemRoot\system32\DRIVERS\VBoxNetFlt.sys Image name: VBoxNetFlt.sys Timestamp: Wed Dec 19 13:47:16 2012 (50D1C564) CheckSum: 0002B9C5 ImageSize: 00028000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 This driver corresponds to VirtualBox network driver, please update the driver or remove the program if no improvement takes place after updating the driver. Here is the link - https://www.virtualbox.org/wiki/Downloads Code: 4: kd> lmvm k57nd60a start end module name fffff880`06ee3000 fffff880`06f4a000 k57nd60a (no symbols) Loaded symbol image file: k57nd60a.sys Image path: \SystemRoot\system32\DRIVERS\k57nd60a.sys Image name: k57nd60a.sys Timestamp: Tue Feb 15 04:19:05 2011 (4D59FEB9) CheckSum: 00071F18 ImageSize: 00067000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Your Broadcom NetLink Gigabit Ethernet NDIS6.x Unified Driver seems to be a little outdated and may be a possible cause, please update the driver from here - Ethernet NIC Driver Downloads | Broadcom
Code: BugCheck 101, {19, 0, fffff880009b3180, 4} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Code: Usual causes: Device driver, BIOS bug, hardware defect It appears that the processor didn't respond to the clock interrupt within the given time interval. Update: Code: 0: kd> !sysinfo machineid Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=1553] BiosMajorRelease = 4 BiosMinorRelease = 6 BiosVendor = American Megatrends Inc. BiosVersion = P2.20 BiosReleaseDate = 06/29/2012 SystemManufacturer = To Be Filled By O.E.M. SystemProductName = To Be Filled By O.E.M. SystemFamily = To Be Filled By O.E.M. SystemVersion = To Be Filled By O.E.M. SystemSKU = To Be Filled By O.E.M. BaseBoardManufacturer = ASRock BaseBoardProduct = Z68 Extreme4 BaseBoardVersion = Your BIOS seems to be a little dated, I would suggest checking for any BIOS updates for your motherboard, they may have introduced some greater hardware compatibility and stability patches with the newer version. I also noticed a few drivers in the raw stack text for the hung processor, here are my findings: Code: 4: kd> lmvm VBoxNetFlt start end module name fffff880`06eb9000 fffff880`06ee1000 VBoxNetFlt (no symbols) Loaded symbol image file: VBoxNetFlt.sys Image path: \SystemRoot\system32\DRIVERS\VBoxNetFlt.sys Image name: VBoxNetFlt.sys Timestamp: Wed Dec 19 13:47:16 2012 (50D1C564) CheckSum: 0002B9C5 ImageSize: 00028000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 This driver corresponds to VirtualBox network driver, please update the driver or remove the program if no improvement takes place after updating the driver. Here is the link - https://www.virtualbox.org/wiki/Downloads Code: 4: kd> lmvm k57nd60a start end module name fffff880`06ee3000 fffff880`06f4a000 k57nd60a (no symbols) Loaded symbol image file: k57nd60a.sys Image path: \SystemRoot\system32\DRIVERS\k57nd60a.sys Image name: k57nd60a.sys Timestamp: Tue Feb 15 04:19:05 2011 (4D59FEB9) CheckSum: 00071F18 ImageSize: 00067000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Your Broadcom NetLink Gigabit Ethernet NDIS6.x Unified Driver seems to be a little outdated and may be a possible cause, please update the driver from here - Ethernet NIC Driver Downloads | Broadcom
F FunkyMaggot Member Joined May 13, 2013 Posts 18 May 14, 2013 #11 Thanks BlueRobot for the reply. I have applied a bios updated and updated those two drivers. I'm still suspicious of the USB, I plugged a stick in my front port and it blue screened again. The upload for that is below: Read More: https://dl.dropboxusercontent.com/u/5485099/MEMORY2.zip I will see if the random blue screen occurs again. Thanks for the help thus far guys.
Thanks BlueRobot for the reply. I have applied a bios updated and updated those two drivers. I'm still suspicious of the USB, I plugged a stick in my front port and it blue screened again. The upload for that is below: Read More: https://dl.dropboxusercontent.com/u/5485099/MEMORY2.zip I will see if the random blue screen occurs again. Thanks for the help thus far guys.
F FunkyMaggot Member Joined May 13, 2013 Posts 18 May 15, 2013 #12 Yet another bluescreen this morning with the 101 stop code Link the the dump below. Read More: https://dl.dropboxusercontent.com/u/5485099/MEMORY3.zip
Yet another bluescreen this morning with the 101 stop code Link the the dump below. Read More: https://dl.dropboxusercontent.com/u/5485099/MEMORY3.zip
V Vir Gnarus BSOD Kernel Dump Expert Joined Mar 2, 2012 Posts 474 May 15, 2013 #13 Ah ha, well I think I found the USB problem. The one crashdump reported an issue with the VMWare USB driver and it looks like it corrupted some data. It's dated Oct 11, 2012, so if there's a VMware update go for it, otherwise you may need to turn off USB emulation in the meantime. Btw, VMware and VirtualBox are two totally different products and different brands. I do not think that VirtualBox uses a VMware driver (correct me if wrong). Are you actually using multiple VM software? That's a definite no-no.
Ah ha, well I think I found the USB problem. The one crashdump reported an issue with the VMWare USB driver and it looks like it corrupted some data. It's dated Oct 11, 2012, so if there's a VMware update go for it, otherwise you may need to turn off USB emulation in the meantime. Btw, VMware and VirtualBox are two totally different products and different brands. I do not think that VirtualBox uses a VMware driver (correct me if wrong). Are you actually using multiple VM software? That's a definite no-no.
F FunkyMaggot Member Joined May 13, 2013 Posts 18 May 15, 2013 #14 Hmm no update for VMWare Workstation it seems, and i'm not sure how to disable the USB emulation. I do have virtual box installed as well as VMWare workstation. I've been moving over to workstation, maybe I can get rid of vbox completely. I had these problems before workstation though :/
Hmm no update for VMWare Workstation it seems, and i'm not sure how to disable the USB emulation. I do have virtual box installed as well as VMWare workstation. I've been moving over to workstation, maybe I can get rid of vbox completely. I had these problems before workstation though :/
V Vir Gnarus BSOD Kernel Dump Expert Joined Mar 2, 2012 Posts 474 May 16, 2013 #15 True, but having both would've caused problems of its own, and it only complicates our analysis of the situation. It's best to get rid of what we know for sure would cause issues, rather than disregard them. You may have been suffering two different conditions that were creating BSODs by having this setup, rather than the one previously. When I have time I'll scrutinize the crashdumps further.
True, but having both would've caused problems of its own, and it only complicates our analysis of the situation. It's best to get rid of what we know for sure would cause issues, rather than disregard them. You may have been suffering two different conditions that were creating BSODs by having this setup, rather than the one previously. When I have time I'll scrutinize the crashdumps further.
F FunkyMaggot Member Joined May 13, 2013 Posts 18 May 16, 2013 #16 Thanks, i'll see how long I can last without another blue screen... I've noticed today that I get some mouse lag (usb mouse using a front port) and while streaming music it hung for a second. Will keep an eye on things...
Thanks, i'll see how long I can last without another blue screen... I've noticed today that I get some mouse lag (usb mouse using a front port) and while streaming music it hung for a second. Will keep an eye on things...
V Vir Gnarus BSOD Kernel Dump Expert Joined Mar 2, 2012 Posts 474 May 24, 2013 #17 Hey mate. How have things been so far? I unfortunately haven't had time to dive into that memory dump, and tbh, I don't see myself having it in the near future, so I apologize for the unnecessary wait.
Hey mate. How have things been so far? I unfortunately haven't had time to dive into that memory dump, and tbh, I don't see myself having it in the near future, so I apologize for the unnecessary wait.
F FunkyMaggot Member Joined May 13, 2013 Posts 18 May 27, 2013 #18 Hey Vir Gnarus, sorry I haven't been prompt with an update, I've actually been away for a week and got back today. Alas, I was once again the victum of a bluesceren, the same 101 stop code. I am uploading the dump file for this one as we speak, it should be ready in an hour or two: Read More: https://dl.dropboxusercontent.com/u/5485099/MEMORY4.zip
Hey Vir Gnarus, sorry I haven't been prompt with an update, I've actually been away for a week and got back today. Alas, I was once again the victum of a bluesceren, the same 101 stop code. I am uploading the dump file for this one as we speak, it should be ready in an hour or two: Read More: https://dl.dropboxusercontent.com/u/5485099/MEMORY4.zip
F FunkyMaggot Member Joined May 13, 2013 Posts 18 May 28, 2013 #19 Looks like the frequency is increasing... only manged about 90 minutes up time and I got a crash... dump is uploading Read More: https://dl.dropboxusercontent.com/u/5485099/MEMORY5.zip
Looks like the frequency is increasing... only manged about 90 minutes up time and I got a crash... dump is uploading Read More: https://dl.dropboxusercontent.com/u/5485099/MEMORY5.zip
V Vir Gnarus BSOD Kernel Dump Expert Joined Mar 2, 2012 Posts 474 May 28, 2013 #20 I'll see what I can do about looking at them, but no guarantees. At least I can cross analyze to find any patterns between em. If anyone else wants to give it a shot feel free to do so.
I'll see what I can do about looking at them, but no guarantees. At least I can cross analyze to find any patterns between em. If anyone else wants to give it a shot feel free to do so.