Hello all...
Well.., the problem is as specified in the title and when I checked the event LOG under control panel > admin tools corresponding to the appropriate time when the error occured... there were the following errors under the 'system' tab...

Not sure how to post an image so wil just type it out..

Event ID: 7000
Category: None
(This particular error is been reported very frequently)

The Dev_CBIDDRV service failed to start due to the following error:
The specified driver is invalid.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

----------------

Event ID: 1003
Category: (102)

Error code 000000d1, parameter1 08b0093c, parameter2 00000002, parameter3 00000001, parameter4 b7310384.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Any help?Did you recently install or update any hw, sw or drivers?

Open Device Manager. Click on VIEW - SHOW HIDDEN DEVICES
Any errors?Wow..!!! That was an incredibly amazing fast reply..! Thans for helping Allan...

Well.. I dont remember updating any s/w except for win SP3 updates that i regularly do.
With respect to h/w drivers, Yes. I did update my Nvidia video card's drivers to the most recent one. This was because I accidently deleted the c:\nvidia folder thinking that it contains only the setup files which was not the case. I was told that the drivers themselves were accessed only from there by the system.
Had the "Blue Screen of Death" errors showing up with reference being given to "nv4_disp.dll" which is the Nvidia driver..
Post the driver upgrade, the problem was fixed..First, the nvidia folder DOES only contain the setup files and CAN be deleted. Second, you did not answer my question about device manager.And the device manager thing..
There were no yellow exclamation marks if that's what you meant by an error..

But under the tab 'Portable Devices', my Nokia symbian phone was listed with a red cross over the 'tv LIKE icon'. I assume it just means the device isn't connected at present..Thought of answering the question in the second post... and quite frankly  did not expect a reply before that ..!! 1) The problem is almost certainly related to the driver update. Try rolling back the driver to the previous version. If you uninstalled the older driver before installing the new one, do you still have the older driver? If so, uninstall the new one and install the old one.

2) You said the system is rebooting. Go to System Properties - Advanced - Startup & Recovery Settings and uncheck "automatically restart". Next time there's an error you should get a blue screen error.) Post the entire contents of that error here.I have the recent memory dump de-bugged as below if that could help you..

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service PACK 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.091208-2036
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Wed Feb 17 03:51:11.343 2010 (GMT+5)
System Uptime: 0 days 8:20:29.927
Loading Kernel Symbols
....................................... ........................
....................................... .........................
.......................
Loading User Symbols

Loading unloaded module list
.....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {c0000005, b13e8d2f, b84efc4c, b84ef948}

Probably caused by : afd.sys ( afd!AfdFreeNPConnectionResources+48 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. USUALLY the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: b13e8d2f, The address that the exception occurred at
Arg3: b84efc4c, Exception Record Address
Arg4: b84ef948, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
afd!AfdFreeNPConnectionResources+48
b13e8d2f 897904 mov dword ptr [ecx+4],edi

EXCEPTION_RECORD: b84efc4c -- (.exr 0xffffffffb84efc4c)
ExceptionAddress: b13e8d2f (afd!AfdFreeNPConnectionResources+0x00000048)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000004
Attempt to write to address 00000004

CONTEXT: b84ef948 -- (.cxr 0xffffffffb84ef948)
eax=88ec3008 ebx=00000000 ecx=00000000 edx=4a320033 esi=88d72820 edi=88d72850
eip=b13e8d2f esp=b84efd14 ebp=b84efd1c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
afd!AfdFreeNPConnectionResources+0x48:
b13e8d2f 897904 mov dword ptr [ecx+4],edi ds:0023:00000004=??
Resetting default scope

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_PARAMETER1: 00000001

EXCEPTION_PARAMETER2: 00000004

WRITE_ADDRESS: 00000004

FOLLOWUP_IP:
afd!AfdFreeNPConnectionResources+48
b13e8d2f 897904 mov dword ptr [ecx+4],edi

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from b13dbc18 to b13e8d2f

STACK_TEXT:
b84efd1c b13dbc18 88d72820 88d72898 88d72820 afd!AfdFreeNPConnectionResources+0x48
b84efd34 b13dbbbc 88d72820 b13da7a8 b84efd60 afd!AfdFreeConnectionResources+0x41
b84efd44 b13d886a 88d72898 8a2e9850 89ce8848 afd!AfdFreeConnection+0x5c
b84efd60 8056bd45 89ce8848 00000000 8055b17c afd!AfdDoWork+0x51
b84efd74 80534c1a 8a2e9850 00000000 8a4c4b30 nt!IopProcessWorkItem+0x13
b84efdac 805c61ee 8a2e9850 00000000 00000000 nt!ExpWorkerThread+0x100
b84efddc 80541e02 80534b1a 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: afd!AfdFreeNPConnectionResources+48

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: afd

IMAGE_NAME: afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48a40333

STACK_COMMAND: .cxr 0xffffffffb84ef948 ; kb

FAILURE_BUCKET_ID: 0x7E_afd!AfdFreeNPConnectionResources+48

BUCKET_ID: 0x7E_afd!AfdFreeNPConnectionResources+48

Followup: MachineOwner
Well, I dont have the old driver with me... Even if i did and installed it, i'm guessing I would get the nv4_disp bsod like before..
Nevertheless, do you suggest that I try out the second option first before having a driver rollback done?
Also, is the BSOD likely to stay all night? cuz I'm most likely to take a nap now..If the error generates a blue screen then yes, the error message will remain up until you "hard" reboot. After making the change above you'll need to reboot before it takes effect.Was the memory dump file above able to tell you anything?So far there have been no BSOD's...
but the same Dev_CBIDDRV error is being shown several times in the event logger...
any help?Are you saying there are no problems other than the entry in event viewer? STAY OUT OF THE EVENT VIEWERPretty sharp advice there..!
Okay.. let me then wait for the next possible BSOD..
btw.., can i remind you of the memory dump above?Hi allan.. Last night there came up the BSOD..
It had the words "Bad pool header"..