I've been getting these little errors with my pc, and last night I got 2 blue screens of death.

Today when I booted up it appeared to be in safe mode, low res, etc and said I needed to run scandisk, so I did...took almost an hour I guess and when I rebooted my pc appears to be running fine.

Is there any way to determine whether my pc is on it's last legs or what might be damaged or needs repaired?

tks

http://simhq.com/forum/ubbthreads.php/topics/3507236/Re_First_BSOD_ever.html#Post3507236

if MiniDumps are enabled, we have a few members with the MS debug Tools to let you know which driver or event caused them.

you might be able to check in your event viewer, as a BSOD in Windows 7 logs in the Event viewer and usually logs the driver/error.

Start, Control Panel, Admin Tools, Event Viewer, System.

thanks guys...

here's what I have:



On Tue 2/7/2012 3:47:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020612-19921-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x37D38)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800452FD38, 0xFFFFF88008A97980, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 2/7/2012 3:47:05 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x26478)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800452FD38, 0xFFFFF88008A97980, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 2/7/2012 3:30:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020612-20451-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80038FDE10, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 2/3/2012 2:37:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020312-33275-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF8A00C6FDD18, 0x0, 0xFFFFF800032D13A5, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 1/27/2012 1:52:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012712-27128-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000300BB05, 0xFFFFF880048E4570, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 1/27/2012 5:33:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012712-24117-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80038FDE10, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

These 2 Are Obviously DirectX sys Files, affiliated to Graphics Card,
Ensure Drivers are Up to Date





As the description says, its a memory error, can be either a bad stick of ram, bad PSU, or bad driver.

Run Windows Memory Diagnostic, if its Clean, run Memtest (at least 5 passes), if thats clean run system file checker ( "sfc /scannow", in Admin Priv. Dos Box ).


It looks more like either a driver issue, or bios setting, or a failing component.

I would run a Memory test, a HDD test, and check to make sure all drivers and bios settings are up to date.

And it would not hurt to install the latest DirectX runtimes


http://www.microsoft.com/download/en/details.aspx?id=8109

thank you very much!

That 'WhoCrashed' is a very good little program, Bib4Tuna! It isolated the cause of my BSOD.

Turned out to be a bad stick of ram.