BSOD occurs while opening browsers and playing games.

[Lightwind]

Hi, i hope someone could help about my problem. I'm using windows 7 32bit version and I've been having a lot of pc crashes lately and its getting a blue screen and an error related to irql_not_less_or_equal. i really dont know what it is but i manage to get a minidump file. i dont know how to read this error report but from what i read it tracks down the cause of the problem. i'm hoping to find the answer and fix it. the minidump files are attached, 3 reports all in all. i hope someone can help me. thank you very much

 

[Lightwind]

anybody care to help?
i just had another crash, it happened when i opened a new tab on my browser.

 

[writhziden]

Your network adapter driver is out of date. Please update it from your motherboard site or your laptop/desktop vendor support site. Use http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html to fill in your system specs if you need help with this. You may also need to follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html if you did not custom build your computer. We would prefer that you follow these instructions for better help, regardless.

Loading Dump File [D:\Kingston\BSODDmpFiles\Lightwind\040312-25942-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a50000 PsLoadedModuleList = 0x82b98810
Debug session time: Tue Apr  3 06:44:40.127 2012 (UTC - 6:00)
System Uptime: 0 days 0:11:44.688
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: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 8d936120, The PRCB address of the hung processor.
Arg4: 00000003, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
80786a94 82abbcf3 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
80786ad0 82abb342 00002710 00000000 0000b000 nt!KeAccumulateTicks+0x242
80786b10 82abb1ef 82abcd6a 16c00a0c 00000000 nt!KeUpdateRunTime+0x145
80786b6c 82ac0577 0000ad1b 0000ad1b 000000d1 nt!KeUpdateSystemTime+0x613
80786b6c 82abcd6a 0000ad1b 0000ad1b 000000d1 nt!KeUpdateSystemTimeAssist+0x13
80786c00 82af3461 00000001 00000000 82af34c3 nt!KiIpiSendPacket+0xc2
80786c30 82abdb9d 00000fff 000000fe 00000001 nt!KxFlushEntireTb+0xb2
80786c50 82abd81f 00000000 00000001 00001000 nt!KeFlushTb+0x22a
80786c7c 82ab4046 80786ca4 00000000 00000001 nt!KeFlushMultipleRangeTb+0x19c
80786cb0 82ab3d25 84714904 00000008 85104d10 nt!MiZeroPageChain+0x53
80786d44 82bdb483 00000000 80786d90 82c5e66d nt!MmZeroPageThread+0x452
80786d50 82c5e66d 8080a4a0 b12f036a 00000000 nt!Phase1Initialization+0x14
80786d90 82b100d9 82bdb46f 8080a4a0 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


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_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

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

Start with the steps in http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html and let us know if you need further assistance.

• If you are overclocking any hardware, please stop.

 

[Lightwind]

thank you very much, i'll do as you told, hopefully this solves my problem. thanks!