BSOD + Restart on Vista

how can one tell which hardware/driver is malfunctioning by lookin the BSOD error message???????

can somebody comment on this please!!!!!!!!!!!!!!!!!!!!!!!!!!
 
the biggest problem is that tuneup asked me to delete the system recovery files to save space as it took up nearly 20gb. and me thinking that i havent faced any problems deleted them. apart from that, i used the one click maintainance. i let it fix all the problemes apart from defraging for which i use diskeeper 2008 these days.
 
@vb86 mailed my friend who works at Vista Support ,awaiting for his response ,once i get the mail will post what can be done to solve this problem else u solve it by ur self there is a work around to call Vista USA support

1) Install Skype on friends comp.
2) Call 1-800-936-5700.
3) You will reach dumb Microsoft Customer care.
4) Use some fake name dont tell them that ur calling from India ,tell some place in USA.
5) If they ask for ur no,tell ur not ready to reveal the no.
6) Put a bit accent and tell (actually yell) them that u got a pop on ur machine saying ready to install service pack 1 ,u went ahead and installed it ,now u are getting this bluescreen error.
7) They will ask you to contact ur vendor tell them that ur vendor( name some company like Dell,HP,compaq) requested for complete reinstalltion and you are not ready to loose data
8) More over it was Microsoft update and not my vendors update so you help me now.
9) they will not ask you for serial key of ur vista ( i am sure about this)
10)once u reach the technical support talk casually tell them what all happened and do not reveal from where are u calling.
11) Microsoft US support work timings 6.00PM-9.30AM(IST)
12) please do act like a dumb when speaking to tech support

PS:ALL U NEED TO MENTION IS SP1 SCREWED UR COMPUTER
Do this i am sure u will get free support ( btb i work at Microsoft and i do the same ) ,have any issues PM me took some time to help u ,no i need to study :mad: as i have exam in the morning :cry:
 
I looked at the memory dump. Unfortunately there isn't much information in it, though it points to memory corruption. This is further bolstered by the fact that you've seen two different bugchecks. There are two likely sources: buggy drivers, and bad memory.
BTW, how many different CD emulation programs do you have? I count AnyDVD, but I suspect you have something else too (daemon tools and something from gearsoft?).
 
daemon and poweriso. poweriso doesnt work on startup. since i have 2 ram sticks, i tested them individually. they worked fine. ive out both of them back and since then, there hasnt been a problem. ive rebooted a few times to check. will try a few times today and update you guys. thanks..
 
i personally havent used it. another thing ive noticed these days is that when i boot my pc, the resident shield in avg av is sometimes disabled. again, this is random and doesnt always happen.
 
results from who crashed:

On Tue 16-12-2008 15:37:23 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1A (0x4000, 0x8DFC38B0, 0x55, 0x17F7ED)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
On Tue 16-12-2008 06:03:14 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1A (0x4000, 0x86C03210, 0x1, 0x17F7ED)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
On Mon 15-12-2008 15:36:13 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x50 (0xB3377F54, 0x0, 0x820C6C5F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
On Sun 14-12-2008 18:22:18 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x8224B1BD, 0x815FF914, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
On Sat 13-12-2008 05:50:30 your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x8F10E8F8, 0x8F10EA44, 0x8224D430)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
On Wed 10-12-2008 05:49:29 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x94F6E05B, 0x8E3398A4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
On Mon 08-12-2008 06:29:27 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x30, 0x991B23C8, 0x8E667000, 0x963DD66C)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
On Wed 03-12-2008 05:37:28 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x50 (0xD8FE802D, 0x0, 0x958A040D, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
On Mon 28-04-2008 18:32:15 your computer crashed
This was likely caused by the following module: nvlddmkm.sys
Bugcheck code: 0x50 (0x8D3DF89C, 0x0, 0x8BDEA9A9, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 176.44
company: NVIDIA Corporation
description: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 176.44
On Mon 21-04-2008 20:52:27 your computer crashed
This was likely caused by the following module: nvlddmkm.sys
Bugcheck code: 0xD1 (0x8D3F26DC, 0x2, 0x0, 0x8C1E4098)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 176.44
company: NVIDIA Corporation
description: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 176.44
On Wed 12-12-2007 14:23:15 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x9F (0x3, 0x857D85A8, 0x871C5030, 0x93B367F8)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
Click to expand...

please note that the last 3 took place way back.
 
Back
Top