Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

hardware problem?


  • Please log in to reply

#1
spacecat

spacecat

    Member

  • Member
  • PipPip
  • 40 posts
Ever since I brought this computer(I bought it off Ebay so I probably got a very bad install :) ) I have been receiving many different stop messages.It usually occurs when I am playing a game or watching a video,but more recently it happens during web browsing or system idleness, the computer would crash to the blue screen of death or sometimes it would just reboot with bsod or no mini dump.I have mostly ignored the problem and hopedit would go away(lol) but i will try to explain my problem best to you now

I am running windows xp sp3 home edition
Intel®pentium®dual CPU
e2200 @ 2.2 GHz
2.2 GHz 3.25 RAM
ati raedon hd 2400 (g card)
realtek hd audio manager (s card)
avg internet security 3-pack (full edition)

here are some of the stop messages.(please excuse any typos)
(I AM NOT COMPLETELY SURE THE 8 I TYPE ARE 8'S THEY MIGHT BE B'S, sorry)

This one here is one of the most common
bccode: 1000007f
bcp1:000000008
bcp2:8004200
bcp3: 00000000
bcp4:00000000
OSver: 5_1_2600
sp: 3.0
product: 768_1

another one here (not common at all)
bccode:1000050
bcp1:E4D82028
bcp2:00000000
bcp3:bf26aco2
bcp4:00000001
OSver: 5_1_2600
sp: 3.0
product: 768_1

this one is probably the most common

bccode:1000000a
bcp1:00000001
bcp2:000000FF
bcp3:00000001
bcp4:805d3d46
OSver: 5_1_2600
sp: 3.0
product: 768_1

Not very common this one.

bccode:100000d1
bcp1:00000d 00
bcp2:000000ff
bcp3:00000008
bcp4:00000d 00
OSver: 5_1_2600
sp: 3.0
product: 768_1



bccode:100000008e
bcp1:80000004
bcp2:80545BBB
bcp3:AA3cEBB4
bcp4:00000000
OSver: 5_1_2600
sp: 3.0
product: 768_1

here is a mini dump

ba0a8000 ba0b1180 isapnp Sun Apr 13 19:36:40 2008 (480252B8)
ba0b8000 ba0c2580 MountMgr Sun Apr 13 19:39:45 2008 (48025371)
ba0c8000 ba0d4c80 VolSnap Sun Apr 13 19:41:00 2008 (480253BC)
ba0d8000 ba0e0e00 disk Sun Apr 13 19:40:46 2008 (480253AE)
ba0e8000 ba0f4180 CLASSPNP Sun Apr 13 20:16:21 2008 (48025C05)
ba0f8000 ba101200 PxHelp20 Thu Mar 13 01:57:44 2008 (47D88A18)
ba108000 ba111000 AVGIDSErHr Thu Jan 22 20:10:13 2009 (4978D2A5)
ba138000 ba140e00 intelppm Sun Apr 13 19:31:31 2008 (48025183)
ba148000 ba157c00 serial Sun Apr 13 20:15:44 2008 (48025BE0)
ba158000 ba162480 imapi Sun Apr 13 19:40:57 2008 (480253B9)
ba168000 ba177600 cdrom Sun Apr 13 19:40:45 2008 (480253AD)
ba178000 ba186100 redbook Sun Apr 13 19:40:27 2008 (4802539B)
ba188000 ba192000 GEARAspiWDM Thu Mar 19 15:32:37 2009 (49C26595)
ba198000 ba1a2000 nvnetbus Sat Nov 17 23:43:54 2007 (473F7CBA)
ba1a8000 ba1b4880 rasl2tp Sun Apr 13 20:19:43 2008 (48025CCF)
ba1b8000 ba1c2200 raspppoe Sun Apr 13 19:57:31 2008 (4802579B)
ba1c8000 ba1d3d00 raspptp Sun Apr 13 20:19:47 2008 (48025CD3)
ba1d8000 ba1e0900 msgpc Sun Apr 13 19:56:32 2008 (48025760)
ba1e8000 ba1f1f00 termdd Sun Apr 13 19:38:36 2008 (4802532C)
ba1f8000 ba201e80 NDProxy Sun Apr 13 19:57:28 2008 (48025798)
ba208000 ba216880 usbhub Sun Apr 13 19:45:36 2008 (480254D0)
ba218000 ba225300 NVENETFD Sat Nov 17 23:43:45 2007 (473F7CB1)
ba258000 ba266b00 drmk Sun Apr 13 19:45:12 2008 (480254B8)
ba288000 ba290700 wanarp Sun Apr 13 19:57:20 2008 (48025790)
ba298000 ba2a0780 netbios Sun Apr 13 19:56:01 2008 (48025741)
ba2a8000 ba2b0fa0 PQIMount Tue Jun 03 22:43:18 2003 (3EDD1676)
ba2b8000 ba2c2e00 Fips Sun Apr 13 19:33:27 2008 (480251F7)
ba2d8000 ba2e1000 HIDCLASS Sun Apr 13 19:45:25 2008 (480254C5)
ba2e8000 ba2f5a00 xusb21 Tue Aug 28 18:05:11 2007 (46D455C7)
ba2f8000 ba305000 WDFLDR Thu Nov 02 08:54:05 2006 (4549B22D)
ba318000 ba327900 Cdfs Sun Apr 13 20:14:21 2008 (48025B8D)
ba328000 ba32e180 PCIIDEX Sun Apr 13 19:40:29 2008 (4802539D)
ba330000 ba334d00 PartMgr Sun Apr 13 19:40:48 2008 (480253B0)
ba378000 ba380000 nvsmu Sat Oct 13 00:53:08 2007 (471008E4)
ba388000 ba38c300 usbohci Sun Apr 13 19:45:34 2008 (480254CE)
ba390000 ba397600 usbehci Sun Apr 13 19:45:34 2008 (480254CE)
ba3a0000 ba3a6180 HIDPARSE Sun Apr 13 19:45:22 2008 (480254C2)
ba3a8000 ba3ad200 vga Sun Apr 13 19:44:40 2008 (48025498)
ba3b8000 ba3bca80 Msfs Sun Apr 13 19:32:38 2008 (480251C6)
ba3c8000 ba3cf880 Npfs Sun Apr 13 19:32:38 2008 (480251C6)
ba3d8000 ba3de000 StarOpen Tue Jun 27 20:15:56 2006 (44A183EC)
ba3f0000 ba3f5280 avgmfx86 Tue Feb 24 09:31:56 2009 (49A3BE8C)
ba418000 ba41dd00 avgfwdx Wed Mar 11 17:15:24 2009 (49B7F1AC)
ba420000 ba427d80 usbccgp Sun Apr 13 19:45:38 2008 (480254D2)
ba438000 ba43ca80 TDI Sun Apr 13 20:00:04 2008 (48025834)
ba448000 ba44c580 ptilink Fri Aug 17 21:49:53 2001 (3B7D8371)
ba458000 ba45c080 raspti Fri Aug 17 21:55:32 2001 (3B7D84C4)
ba460000 ba466000 kbdclass Sun Apr 13 19:39:46 2008 (48025372)
ba468000 ba46da00 mouclass Sun Apr 13 19:39:47 2008 (48025373)
ba480000 ba484500 watchdog Sun Apr 13 19:44:59 2008 (480254AB)
ba4a0000 ba4a4ca0 AVGIDSShim Thu Jan 22 20:10:29 2009 (4978D2B5)
ba4b8000 ba4bb000 BOOTVID Fri Aug 17 21:49:09 2001 (3B7D8345)
ba54c000 ba54fd80 serenum Sun Apr 13 19:40:12 2008 (4802538C)
ba560000 ba562880 hidusb Sun Apr 13 19:45:27 2008 (480254C7)
ba568000 ba56b900 kbdhid Sun Apr 13 19:39:47 2008 (48025373)
ba574000 ba576780 ndistapi Sun Apr 13 19:57:27 2008 (48025797)
ba584000 ba587c80 mssmbios Sun Apr 13 19:36:45 2008 (480252BD)
ba5a8000 ba5a9b80 kdcom Fri Aug 17 21:49:10 2001 (3B7D8346)
ba5aa000 ba5ab100 WMILIB Fri Aug 17 22:07:23 2001 (3B7D878B)
ba5ac000 ba5ad700 avgrkx86 Tue Feb 24 09:31:10 2009 (49A3BE5E)
ba5b8000 ba5b9100 swenum Sun Apr 13 19:39:52 2008 (48025378)
ba5be000 ba5bf280 USBD Fri Aug 17 22:02:58 2001 (3B7D8682)
ba5c4000 ba5c5f00 Fs_Rec Fri Aug 17 21:49:37 2001 (3B7D8361)
ba5c8000 ba5c9080 Beep Fri Aug 17 21:47:33 2001 (3B7D82E5)
ba5cc000 ba5cd080 mnmdd Fri Aug 17 21:57:28 2001 (3B7D8538)
ba5d0000 ba5d1080 RDPCDD Fri Aug 17 21:46:56 2001 (3B7D82C0)
ba5e8000 ba5e9100 dump_WMILIB Fri Aug 17 22:07:23 2001 (3B7D878B)
ba618000 ba619880 splitter Sun Apr 13 19:45:07 2008 (480254B3)
ba638000 ba639a80 ParVdm Fri Aug 17 21:49:49 2001 (3B7D836D)
ba670000 ba670d00 pciide Fri Aug 17 21:51:49 2001 (3B7D83E5)
ba6ed000 ba6edb80 Null Fri Aug 17 21:47:39 2001 (3B7D82EB)
ba709000 ba709d00 dxgthk Fri Aug 17 21:53:12 2001 (3B7D8438)
ba720000 ba720a80 PQNTDrv Tue Sep 17 00:14:30 2002 (3D8665D6)
ba727000 ba727860 BANTExt Thu May 28 03:43:29 1998 (356CCF51)
ba7f0000 ba7f0c00 audstub Fri Aug 17 21:59:40 2001 (3B7D85BC)
bf000000 bf011600 dxg Sun Apr 13 19:38:27 2008 (48025323)
bf012000 bf065000 ati2dvag Wed Jan 14 04:47:44 2009 (496D6E70)
bf065000 bf0f2000 ati2cqag Wed Jan 14 03:37:06 2009 (496D5DE2)
bf0f2000 bf165000 atikvmag Wed Jan 14 03:45:52 2009 (496D5FF0)
bf165000 bf1af000 atiok3x2 Wed Jan 14 04:53:11 2009 (496D6FB7)
bf1af000 bf581cc0 ati3duag Wed Jan 14 04:22:31 2009 (496D6887)
bf582000 bf7e4680 ativvaxx Wed Jan 14 04:05:40 2009 (496D6494)
bf800000 bf9c2e00 win32k Mon Feb 09 11:13:13 2009 (49900FC9)
bffa0000 bffe5c00 ATMFD Mon Apr 14 01:09:55 2008 (4802A0D3)

Unloaded modules:
a9312000 a9321000 usbaudio.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba5ca000 ba5cc000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a8fb2000 a8fbf000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a9720000 a972e000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a8f34000 a8f57000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba79e000 ba79f000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba64a000 ba64c000 MSKSSRV.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba5bc000 ba5be000 MSPQM.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba5ba000 ba5bc000 MSPCLOCK.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a8ff7000 a9022000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a9bc2000 a9bed000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba76d000 ba76e000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a9d55000 a9d62000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
aa3bc000 aa3ca000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a9bed000 a9c10000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba608000 ba60a000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba570000 ba574000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba278000 ba285000 i8042prt.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba348000 ba34d000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ba564000 ba567000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ba4b0000 ba4b5000 Flpydisk.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ba4a8000 ba4af000 Fdc.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {1, 1c, 1, 80503d46}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : hardware ( nt+2cd46 )

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

Finished dump check
No idea what the above means but if any if you tech gods could help me out it would be great. :)

Any help would be much appreciated and sorry for any mistakes,typos, retardation im only 14 lol :)
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes

WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply
  • 0

#3
spacecat

spacecat

    Member

  • Topic Starter
  • Member
  • PipPip
  • 40 posts
thanks for the help here are the results (there are a lot lol)
On Fri 31/07/2009 23:02:33 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x1000000A (0x3D830000, 0x1C, 0x0, 0x805452AB)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware





On Fri 31/07/2009 21:39:29 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x1000000A (0xFFFFFFFF, 0xFF, 0x1, 0x80539EC0)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware





On Fri 31/07/2009 19:23:34 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007F (0x8, 0xBA338D70, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\ntoskrnl.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 on your system which cannot be identified.



On Mon 27/07/2009 00:33:29 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x20, 0x2, 0x0, 0x805153EB)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.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 on your system which cannot be identified.



On Fri 24/07/2009 00:03:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007F (0x8, 0xBA338D70, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\ntoskrnl.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 on your system which cannot be identified.



On Sun 19/07/2009 04:16:34 your computer crashed
This was likely caused by the following module: kmixer.sys
Bugcheck code: 0x100000D1 (0xFFFFFF91, 0x2, 0x1, 0xA9201AB4)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\kmixer.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Audio Mixer
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 06/07/2009 17:34:08 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\ntoskrnl.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 on your system which cannot be identified.



On Sun 05/07/2009 15:42:48 your computer crashed
This was likely caused by the following module: kmixer.sys
Bugcheck code: 0x1000000A (0x0, 0x1C, 0x1, 0x804FB03C)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\kmixer.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Audio Mixer
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 04/07/2009 12:45:12 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x1000000A (0x0, 0x1C, 0x1, 0x80530AC2)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware





On Sat 04/07/2009 03:06:19 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x100000D1 (0x456CF335, 0x2, 0x1, 0xA8EFF649)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware





On Mon 29/06/2009 16:53:48 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007F (0x8, 0xBA338D70, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\ntoskrnl.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 on your system which cannot be identified.



On Sun 28/06/2009 21:01:30 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\ntoskrnl.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 on your system which cannot be identified.



On Sun 28/06/2009 18:01:18 your computer crashed
This was likely caused by the following module: ati3duag.dll
Bugcheck code: 0x10000050 (0xE39B3028, 0x0, 0xBF26AC02, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ati3duag.dll
product: ATI Technologies Inc. Radeon DirectX Universal Driver
company: ATI Technologies Inc.
description: ati3duag.dll



On Sun 28/06/2009 16:14:13 your computer crashed
This was likely caused by the following module: ati3duag.dll
Bugcheck code: 0x10000050 (0xE4D82028, 0x0, 0xBF26AC02, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ati3duag.dll
product: ATI Technologies Inc. Radeon DirectX Universal Driver
company: ATI Technologies Inc.
description: ati3duag.dll



On Thu 25/06/2009 21:33:44 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007F (0x8, 0xBA338D70, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\ntoskrnl.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 on your system which cannot be identified.



On Thu 25/06/2009 16:35:00 your computer crashed
This was likely caused by the following module: ati3duag.dll
Bugcheck code: 0x10000050 (0xE4F03820, 0x0, 0xBF26AC02, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ati3duag.dll
product: ATI Technologies Inc. Radeon DirectX Universal Driver
company: ATI Technologies Inc.
description: ati3duag.dll



On Wed 24/06/2009 21:20:54 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\ntoskrnl.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 on your system which cannot be identified.



On Wed 24/06/2009 15:09:18 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0x80000004, 0x80545BBB, 0xB96D39EC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.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 on your system which cannot be identified.



On Sun 21/06/2009 11:37:04 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x805266AA, 0xBA2F7B7C, 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 on your system which cannot be identified.



On Sat 20/06/2009 21:06:28 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x0, 0xFF, 0x1, 0x80546AF6)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.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 on your system which cannot be identified.



On Wed 17/06/2009 19:45:12 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007F (0x8, 0xBA338D70, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\ntoskrnl.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 on your system which cannot be identified.



On Thu 11/06/2009 21:44:54 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x1000000A (0x0, 0x1C, 0x1, 0x80545046)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware





On Tue 09/06/2009 16:50:32 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x1000000A (0x1, 0x1C, 0x1, 0x80503D46)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware





On Sun 07/06/2009 19:18:40 your computer crashed
This was likely caused by the following module: ks.sys
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\drivers\ks.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel CSA Library
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Whew doggie. your OS is a mess.
Can you boot into Safe Mode and does the BSOD's happen there?
  • 0

#5
spacecat

spacecat

    Member

  • Topic Starter
  • Member
  • PipPip
  • 40 posts
appreciate the help
should i log into my acoount or into the administrator?
i will log into my accout now and try to get a bsod to occour,but plz tell me if im in wrong acc
(its getting late(uk)and i might fall asleep lol but sorry if i dont reply till to tommorow morning :) lol)
  • 0

#6
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
It may be RAM problem.

If you have more than one RAM module installed, try starting computer with one RAM stick at a time.
NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below.
If you have only one RAM stick installed...
...run memtest: http://www.techspot....topic62524.html
  • 0

#7
spacecat

spacecat

    Member

  • Topic Starter
  • Member
  • PipPip
  • 40 posts
okay thanks bruni i will try that now --and to rhshafer61 i left my pc on all night on safe mode(no problems but the second I rebooted into ''normal mode'' my computer got bsod and thats never happened before..)---------wish me luck and il use a tut from my mums pc:)but im off to buy some canned air and a wrist spark thingy!(air in a can lol)because i heard somewhere i will need it!!
  • 0

#8
spacecat

spacecat

    Member

  • Topic Starter
  • Member
  • PipPip
  • 40 posts
great :) , went and brought an anti static wrsitband(didnt let me buy c air because im not 18lol :) )i have removed a ddr2 ram now and i have memtest running ,but i hve no idea what's going on. how do i tell if i have faulty ram?? :) its on a weird blue screen thingy!
  • 0

#9
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
It will show you a Failed Message if something is wrong
Let the tests run for at least 2 hours on each stick of memory.
This way we can get a more accurate results.
  • 0

#10
spacecat

spacecat

    Member

  • Topic Starter
  • Member
  • PipPip
  • 40 posts
okay been around 2 h now -- The memcheck says it has 0 pass 7 errors and 0 ecc errors -is my ram busted? :) and should i swap ram and test the over one --or wait longer and see if it passes?
  • 0

Advertisements


#11
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Errors mean bad ram.
Try the other one and see what results are for it.
You are getting the results we figured you would get.
  • 0

#12
stettybet0

stettybet0

    Trusted Tech

  • Technician
  • 2,579 posts
Memtest errors do not necessarily mean bad RAM. They could be due to incorrect BIOS settings (RAM overclocked too high, RAM timings set too tight, or RAM not receiving enough voltage). It would be best to explore those options before spending money on new RAM.

Could you give us the make and model of your RAM and motherboard?

(If you don't know, I'm sure rshaffer61 has a nice canned speech on how to use Everest or CPU-Z to get that information. :))
  • 0

#13
spacecat

spacecat

    Member

  • Topic Starter
  • Member
  • PipPip
  • 40 posts
ok i have a gf7050v-m7 gf7050v-m7 motherboard and it takes up to 2 2gb ddr2 ram and and ddr2 533/667/800 andone of my ram chips says 2 gb ddr800 samsung fg14/10n--and 2gb 800mhz 256x4 no idea whaat thats means------i dont even know what bios is lol but im swapping the ram around now and seeng the results on the over one :)
  • 0

#14
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Try to run the computer with 1 RAM stick at a time, and see, if it'll behave.
  • 0

#15
spacecat

spacecat

    Member

  • Topic Starter
  • Member
  • PipPip
  • 40 posts
uh oh this ram chip has 1 pass 76errors and 0 ecc errors --but on thisone the errors are red near the bottom bit --the over chip had green-- so i guess my ram is royally fu##ed :) :)
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP