Computer keeps on freezing, sometimes BSOD

usasma · 14 Dec 2009

OK, let's try Driver Verifier. Please follow these directions exactly:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) 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 "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then 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.

Reboot the system and waitfor it to crash to the Blue Screen. 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.
Reboot into Windows (after the crash) and turn offDriver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

reghakr · 14 Dec 2009

Where's torrentg, he undetsnadsnthese better than anyone i;ve dealt with before,\\

Sorry about the keyboard errors, it;s getting dumped in the snow soon.

matmos · 15 Dec 2009

hey guys

i had a talk yesterday with the costumer support of the company i bought the computer from and we came to the conclusion that i should try working with windows xp in a dual boot mode to rule out a hardware problem. they told me that otherwise it could just be a driver incompatiblity problem with windows 7 and it's just a matter of time until a correct update will be released. so, i'm going to follow his order.

thanks a lot though!

reghakr · 15 Dec 2009

I think you should follow usasma's solution.

matmos · 15 Dec 2009

so you really think it's not a hardware problem?

should using windows 7 be so complex that it's recommended to take on such a procedure with the drivers?

just asking cause i'm also calculating time loss here. i spent so much of it in the last month fixing the computer instead of finishing my homeworks from uni.

matmos · 15 Dec 2009

well

i took on your advice and turned on the verifier. hopefully i'll report back soon enough.

chev65 · 15 Dec 2009

Hmmm, It might be easier to just update from the manufacture site. There are lots of Windows 7 drivers for your board there. >> ASRock > Products > Motherboard > N68-S > Download

matmos · 15 Dec 2009

so it happened. i used the varifier. used then my computer and it crashed and here is the minidump file attached.

matmos · 18 Dec 2009

hey

just wondering, could it be that a recent xml something something update from microsoft from two days ago help to solve my ongoing problem? do you guys know anything about it?

zigzag3143 · 18 Dec 2009

matmos said:

hey

just wondering, could it be that a recent xml something something update from microsoft from two days ago help to solve my ongoing problem? do you guys know anything about it?

HI and welcome

Never seen this one before so I am going to get a second pair of eyes.

In the mean time It looks harware related. Seems like svchost failed. Analysis inconclusive

Ken J+

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\121509-12531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a4b000 PsLoadedModuleList = 0x82b93810
Debug session time: Tue Dec 15 16:38:36.375 2009 (GMT-5)
System Uptime: 0 days 4:11:37.625
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
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: 00000060, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 807c4120, The PRCB address of the hung processor.
Arg4: 00000001, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  1c

STACK_TEXT:  
9cf6270c 82ab6cf3 00000101 00000060 00000000 nt!KeBugCheckEx+0x1e
9cf62748 82ab6342 00002626 00000000 000ebe00 nt!KeAccumulateTicks+0x242
9cf62788 82ab61ef 82ae316a e0f95f9c 00000000 nt!KeUpdateRunTime+0x145
9cf627e4 82abb577 0000001b 0000001b 000000d1 nt!KeUpdateSystemTime+0x613
9cf627e4 82ae316a 0000001b 0000001b 000000d1 nt!KeUpdateSystemTimeAssist+0x13
9cf62890 82c8086d 00000001 bacb9787 00000053 nt!KeFlushProcessWriteBuffers+0x137
9cf62d00 82c8148c 00000053 9cf62d24 00000002 nt!ExpQuerySystemInformation+0x2516
9cf62d1c 82a8e42a 00000000 02b34598 00000010 nt!NtQuerySystemInformation+0x76
9cf62d1c 77b464f4 00000000 02b34598 00000010 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0084fb60 00000000 00000000 00000000 00000000 0x77b464f4


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:  CLOCK_WATCHDOG_TIMEOUT_2_PROC_VRF_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_2_PROC_VRF_ANALYSIS_INCONCLUSIVE

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