Tech Support Forum banner
Status
Not open for further replies.

Windows Vista frustration

5K views 11 replies 2 participants last post by  BrettoRex  
#1 ·
Hello,

I recently installed 2Gb of RAM on my machine:

Dealing with a Windows Vista Home Premium with SP1

I have a Radeon X1900 Series Video Card,

Intel Core 2CPU X6800 2.93 GHz Chipset.

For some reason, ever since I installed the RAM i've been getting blue screen error messages:

I reinstalled drivers and am completely up to date (as far as I know) and I still get an error:

(STOP: 0x0000005, 0x849A7D5B, 0xA351A3C, 0x0000000)

I have no idea what to do about this, and it usually has something to do with when I am playing a game, (more recently Spore, WoW, and other such)

Thanks in advance!
 
#2 · (Edited)
Hi. . .

There is part of that STOP error code (bugcheck) missing. If in fact the bugcheck is 0x00000005, there is not enough information to tell you very much as it simply translates to INVALID_PROCESS_ATTACH_ATTEMPT.

So, let's get the dumps and other items so that I can take a look at this for you and see what can be found. Please do the following:

Click on the Live SysInternals AutoRuns link below in my sig area. Save it to desktop. Then download the attached zip file and extract the lone batch file to your desktop. Go to your desktop, right-click on the batch file and select run as administrator. You will see the black "DOS" screen appear and scroll followed by the green status bar. It will take a few minutes to run. It will dump the app and system logs, run AutoRuns, msinfo32 and dxdiag. The output will be in a new folder found within your documents folder named TSF_Vista_Support. It is imperative that you download AutoRuns 1st - or the job will fail.

Zip the contents of the new folder up and attach to your next post.

Any ? - please let me know.

Regards. . .

jcgriff2

.
 
#4 ·
Hi - the autoruns job failed - did you click on the Live SysIntenals AutoRuns link, download it and SAVE it to your desktop?

Also, there are no mini dump files in the zip file you posted. Did you right-click on the batch file and select Run as Administrator? Did you extract the batch file from the zip file to your desktop?

It must be run at an elevated administrative level for it to access the mini dumps and to run autoruns.

To make sure - go to c:\windows\minidump and see if there are files in there.

Regards. . .

jcgriff2

.
 
#7 ·
Hi. . .

I noticed in msinfo32 that there are 97 entries in the extracted wercon area.

While the dumps are processed, please go to wercon and see what is there -
START | type wercon and hit enter

Select entries from the top-left of the screen.

What is there?. . . I unfortunately cannot read most of this msinfo32 area.

Regards. . .

jcgriff2

Code:
9/9/2008 7:30 PM	Windows Error Reporting	Fault bucket 274384715, type 5
Event Name: PCA2
Respon
9/9/2008 7:28 PM	Windows Error Reporting	Fault bucket 274420753, type 5
Event Name: PnPDriverInstallError&#x00
9/9/2008 7:28 PM	Windows Error Reporting	Fault bucket 274420753, type 5
Event Name: PnPDriverInstallError&#x00
9/9/2008 7:28 PM	Windows Error Reporting	Fault bucket 274420753, type 5
Event Name: PnPDriverInstallError&#x00
9/9/2008 7:28 PM	Windows Error Reporting	Fault bucket 274420753, type 5
Event Name: PnPDriverInstallError&#x00
9/9/2008 7:28 PM	Windows Error Reporting	Fault bucket 274420753, type 5
Event Name: PnPDriverInstallError&#x00
9/9/2008 7:28 PM	Windows Error Reporting	Fault bucket 274420753, type 5
Event Name: PnPDriverInstallError&#x00
9/8/2008 7:23 AM	Windows Error Reporting	Fault bucket 306065022, type 5
Event Name: RADAR_PRE_LEAK_32
&
9/10/2008 9:23 AM	Windows Error Reporting	Fault bucket 5014495, type 5
Event Name: MemDiagV1
Res
9/10/2008 7:08 AM	Windows Error Reporting	Fault bucket 184548510, type 5
Event Name: AppHangXProcB1
&#x0
9/10/2008 7:08 AM	Application Hang	The program iexplore.exe version 7.0.6001.18000 stopped interacting with Windows and
8/9/2008 8:31 AM	Windows Error Reporting	Fault bucket 30360553, type 5
Event Name: MpTelemetry

8/8/2008 3:39 AM	Windows Error Reporting	Fault bucket WRONG_SYMBOLS, type 0
Event Name: BlueScreen
&#x0
8/5/2008 9:21 AM	Windows Error Reporting	Fault bucket 30795273, type 5
Event Name: MpTelemetry

8/19/2008 9:29 AM	Windows Error Reporting	Fault bucket 30360553, type 5
Event Name: MpTelemetry

8/15/2008 9:25 AM	Windows Error Reporting	Fault bucket 25580367, type 5
Event Name: MpTelemetry

8/14/2008 7:47 AM	Windows Error Reporting	Fault bucket 291669398, type 5
Event Name: RADAR_PRE_LEAK_32
&
8/1/2008 7:52 PM	Application Error	Faulting application Myst.exe, version 0.0.0.0, time stamp 0x64642066, faulting modu
8/1/2008 7:50 PM	Application Error	Faulting application Qt32inst.exe, version 2.1.0.42, time stamp 0x30d11f72, faulting
8/1/2008 7:50 PM	Windows Error Reporting	Fault bucket 300332401, type 1
Event Name: APPCRASH
Re
7/8/2008 5:30 AM	Windows Error Reporting	Fault bucket 0x7f_d_nt!SwapContext+154, type 0
Event Name: BlueScreen
7/6/2008 8:47 PM	Windows Error Reporting	Fault bucket 0x119_nt!EtwpReserveTraceBuffer+ce, type 0
Event Name: B
7/6/2008 11:44 AM	Windows Error Reporting	Fault bucket 0xD1_nt!EtwpCCSwapTrace+3b1, type 0
Event Name: BlueScre
7/5/2008 4:57 AM	Windows Error Reporting	Fault bucket WRONG_SYMBOLS, type 0
Event Name: BlueScreen
&#x0
7/4/2008 9:49 AM	Application Error	Faulting application MsiExec.exe, version 4.0.6001.18000, time stamp 0x47918d31, fau
7/4/2008 10:52 PM	Windows Error Reporting	Fault bucket WRONG_SYMBOLS, type 0
Event Name: BlueScreen
&#x0
7/4/2008 10:19 AM	Windows Error Reporting	Fault bucket 632932909, type 1
Event Name: APPCRASH
Re
7/16/2008 8:33 AM	Windows Error Reporting	Fault bucket 25580367, type 5
Event Name: MpTelemetry

7/16/2008 7:09 AM	Windows Error Reporting	Fault bucket WRONG_SYMBOLS, type 0
Event Name: BlueScreen
&#x0
7/15/2008 9:27 AM	Windows Error Reporting	Fault bucket 30360553, type 5
Event Name: MpTelemetry

7/11/2008 8:55 AM	Windows Error Reporting	Fault bucket 25580367, type 5
Event Name: MpTelemetry

6/20/2008 1:15 AM	Windows Error Reporting	Fault bucket 263163450, type 5
Event Name: AppHangB1
R
6/20/2008 1:15 AM	Application Hang	The program AgeOfConan.exe version 1.0.0.0 stopped interacting with Windows and was 
6/20/2008 12:10 AM	Windows Error Reporting	Fault bucket 262323506, type 5
Event Name: AppHangB1
R
6/20/2008 12:10 AM	Application Hang	The program AgeOfConan.exe version 1.0.0.0 stopped interacting with Windows and was 
6/20/2008 10:26 PM	Windows Error Reporting	Fault bucket 157294431, type 5
Event Name: BEX
Respons
6/19/2008 8:57 AM	Windows Error Reporting	Fault bucket 803871920, type 1
Event Name: APPCRASH
Re
6/19/2008 8:48 AM	Application Error	Faulting application AgeOfConan.exe, version 1.0.0.0, time stamp 0x485270b2, faultin
6/19/2008 5:54 AM	Windows Error Reporting	Fault bucket 262958573, type 5
Event Name: AppHangB1
R
6/19/2008 5:54 AM	Application Hang	The program AgeOfConan.exe version 1.0.0.0 stopped interacting with Windows and was 
6/19/2008 2:03 AM	Windows Error Reporting	Fault bucket 263594786, type 5
Event Name: AppHangB1
R
6/19/2008 2:03 AM	Application Hang	The program AgeOfConan.exe version 1.0.0.0 stopped interacting with Windows and was 
6/19/2008 11:39 AM	Windows Error Reporting	Fault bucket 249973012, type 5
Event Name: RADAR_PRE_LEAK_32
&
6/19/2008 10:14 PM	Windows Error Reporting	Fault bucket 263094608, type 5
Event Name: AppHangB1
R
6/19/2008 10:14 PM	Application Hang	The program AgeOfConan.exe version 1.0.0.0 stopped interacting with Windows and was 
6/18/2008 8:15 AM	Windows Error Reporting	Fault bucket 16081176, type 5
Event Name: AppHangB1
Re
6/18/2008 8:15 AM	Application Hang	The program hpzsetup.exe version 8.5.0.70 stopped interacting with Windows and was c
6/18/2008 7:51 AM	Windows Error Reporting	Fault bucket 163831406, type 5
Event Name: PCA2
Respon
6/18/2008 6:48 AM	Windows Error Reporting	Fault bucket 6370441, type 5
Event Name: PnPDriverNotFound
&#x
5/29/2008 9:50 PM	Windows Error Reporting	Fault bucket WRONG_SYMBOLS, type 0
Event Name: BlueScreen
&#x0
5/27/2008 11:57 PM	Windows Error Reporting	Fault bucket 25580367, type 5
Event Name: MpTelemetry

5/24/2008 4:00 AM	Application Error	Faulting application AgeOfConan.exe, version 1.0.0.0, time stamp 0x48304989, faultin
5/24/2008 4:00 AM	Windows Error Reporting	Fault bucket 766316842, type 1
Event Name: APPCRASH
Re
5/23/2008 4:43 AM	Application Error	Faulting application AgeOfConan.exe, version 1.0.0.0, time stamp 0x48304989, faultin
5/23/2008 4:43 AM	Windows Error Reporting	Fault bucket 766316922, type 1
Event Name: APPCRASH
Re
5/23/2008 12:52 AM	Windows Error Reporting	Fault bucket 242003580, type 5
Event Name: AppHangB1
R
5/23/2008 12:52 AM	Windows Error Reporting	Fault bucket 244633532, type 5
Event Name: AppHangB1
R
5/23/2008 12:52 AM	Application Hang	The program AgeOfConan.exe version 1.0.0.0 stopped interacting with Windows and was 
5/23/2008 12:52 AM	Application Hang	The program iexplore.exe version 7.0.6001.18000 stopped interacting with Windows and
5/22/2008 4:37 AM	Windows Error Reporting	Fault bucket 241540514, type 5
Event Name: AppHangB1
R
5/22/2008 4:37 AM	Application Hang	The program AgeOfConan.exe version 1.0.0.0 stopped interacting with Windows and was 
5/22/2008 2:26 AM	Windows Error Reporting	Fault bucket 632977673, type 1
Event Name: APPCRASH
Re
5/22/2008 2:26 AM	Windows Error Reporting	Fault bucket 632977673, type 1
Event Name: APPCRASH
Re
5/21/2008 10:14 AM	Application Error	Faulting application ngen.exe, version 1.1.4322.573, time stamp 0x3e55926a, faulting
5/21/2008 10:14 AM	Application Error	Faulting application ngen.exe, version 1.1.4322.573, time stamp 0x3e55926a, faulting
5/20/2008 7:57 AM	Windows Error Reporting	Fault bucket 11656272, type 5
Event Name: ServiceHang

5/20/2008 7:31 PM	Windows Error Reporting	Fault bucket 7682418, type 5
Event Name: PnPGenericDriverFound&#x000d
5/20/2008 7:26 PM	Windows Error Reporting	Fault bucket 7682418, type 5
Event Name: PnPGenericDriverFound&#x000d
5/20/2008 6:34 PM	Windows Error Reporting	Fault bucket 11640871, type 5
Event Name: MsSearchTerminateProcess&#x
5/20/2008 1:41 AM	Windows Error Reporting	Fault bucket 12091117, type 5
Event Name: RADAR_PRE_LEAK_32
&#
5/20/2008 1:35 AM	Application Error	Faulting application HitmanBloodMoney.exe, version 0.0.0.0, time stamp 0x00000000, f
5/20/2008 1:35 AM	Windows Error Reporting	Fault bucket 346406616, type 1
Event Name: APPCRASH
Re
5/20/2008 1:33 AM	Application Error	Faulting application HitmanBloodMoney.exe, version 0.0.0.0, time stamp 0x00000000, f
5/20/2008 1:33 AM	Windows Error Reporting	Fault bucket 346406616, type 1
Event Name: APPCRASH
Re
5/20/2008 1:32 AM	Application Error	Faulting application HitmanBloodMoney.exe, version 0.0.0.0, time stamp 0x00000000, f
5/20/2008 1:32 AM	Windows Error Reporting	Fault bucket 346406616, type 1
Event Name: APPCRASH
Re
5/20/2008 1:19 AM	Application Error	Faulting application hitmanbloodmoney.exe, version 0.0.0.0, time stamp 0x00000000, f
5/20/2008 1:19 AM	Windows Error Reporting	Fault bucket 346406616, type 1
Event Name: APPCRASH
Re
5/20/2008 1:18 AM	Windows Error Reporting	Fault bucket 346406616, type 1
Event Name: APPCRASH
Re
5/20/2008 1:17 AM	Application Error	Faulting application HitmanBloodMoney.exe, version 0.0.0.0, time stamp 0x00000000, f
5/20/2008 1:12 AM	Application Error	Faulting application hitmanbloodmoney.exe, version 0.0.0.0, time stamp 0x00000000, f
5/20/2008 1:12 AM	Windows Error Reporting	Fault bucket 346406616, type 1
Event Name: APPCRASH
Re
5/20/2008 1:08 AM	Application Error	Faulting application hitmanbloodmoney.exe, version 0.0.0.0, time stamp 0x00000000, f
5/20/2008 1:08 AM	Windows Error Reporting	Fault bucket 346406616, type 1
Event Name: APPCRASH
Re
5/20/2008 1:07 AM	Application Error	Faulting application HitmanBloodMoney.exe, version 0.0.0.0, time stamp 0x00000000, f
5/20/2008 1:07 AM	Application Error	Faulting application HitmanBloodMoney.exe, version 0.0.0.0, time stamp 0x00000000, f
5/20/2008 1:07 AM	Windows Error Reporting	Fault bucket 346406616, type 1
Event Name: APPCRASH
Re
5/20/2008 1:07 AM	Windows Error Reporting	Fault bucket 346406616, type 1
Event Name: APPCRASH
Re
5/20/2008 1:07 AM	Windows Error Reporting	Fault bucket 346406616, type 1
Event Name: APPCRASH
Re
5/20/2008 1:06 AM	Application Error	Faulting application HitmanBloodMoney.exe, version 0.0.0.0, time stamp 0x00000000, f
5/20/2008 12:19 AM	Windows Error Reporting	Fault bucket 7682418, type 5
Event Name: PnPGenericDriverFound&#x000d
5/19/2008 8:04 PM	Windows Error Reporting	Fault bucket 14577866, type 5
Event Name: RADAR_PRE_LEAK_32
&#
5/19/2008 11:40 PM	Windows Error Reporting	Fault bucket 181837692, type 5
Event Name: RADAR_PRE_LEAK_32
&
5/18/2008 10:37 AM	Application Error	Faulting application WMIADAP.EXE, version 6.0.6000.16386, time stamp 0x4549af43, fau
5/17/2008 7:28 PM	Windows Error Reporting	Fault bucket 3437825, type 5
Event Name: PnPDriverNotFound
&#x
5/17/2008 7:28 PM	Windows Error Reporting	Fault bucket 3437824, type 5
Event Name: PnPDriverNotFound
&#x
5/17/2008 7:28 PM	Windows Error Reporting	Fault bucket 3503251, type 5
Event Name: PnPDriverNotFound
&#x
 
#8 ·
Hey,


So I went to the wercon application, and I assume you want the data in the problem history tab?

The latest problem for windows has this information:

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033

Files that help describe the problem (some files may no longer be available)
Mini090808-01.dmp
sysdata.xml
Version.txt

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: 1000007e
BCP1: C0000005
BCP2: 8E125FF8
BCP3: 8C6A3B08
BCP4: 8C6A3804
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1
Server information: ea09db30-8d28-4b27-afeb-f35d0d058257



Attached are the temporary files as well.

Is this the information you needed? If you need different or more specific information, go ahead and let me know.

Before I posted the problem to the forums, I upgraded all my drivers, and the problem still didn't go away.

Thanks!

-Fil
 

Attachments

#9 · (Edited)
Hi. . .

I have not seen dump outputs quite like these and don't exactly know what to make of it. There is an obvious problem - but you already knew that. Please read on:

The loaded module list in most of your dumps looks like this:
Code:
6a000   Unknown_Module_8040a000 Unknown_Module_8040a000 Sat Jan 19 02:29:43 2008 
7b000   _        ?            Sat Jan 19 02:31:21 2008 (4791A749)
83000   ___________________________ ???????????????????U??????? Sat Jan 19 02:27:
c4000   __       ??           Sat Jan 19 00:28:01 2008 (47918A61)
a4000   _____________G_____________ ????????????G?ďż˝?????????? Fri Feb 22 00:00:
b4000   ___      ??Ă©          Sat Jan 19 00:34:27 2008 (47918BE3)
8b000   _________________________________________ ??????????????????????????¶?
98000   ________ ????????     Sat Jan 19 00:52:19 2008 (47919013)
de000   Unknown_Module_80698000 Unknown_Module_80698000 Sat Jan 19 00:32:48 2008 
e7000   ________j_______ ????????j?????A Sat Jan 19 00:53:08 2008 (47919044)
ef000   __________G______ ??????????G?????? Sat Jan 19 00:32:51 2008 (47918B83)
16000   Unknown_Module_806ef000 Unknown_Module_806ef000 Sat Jan 19 00:32:57 2008 
25000   Unknown_Module_80716000 Unknown_Module_80716000 Sat Jan 19 00:49:54 2008 
34000   _______________________________________ ??
???????????S????????,??T Sat Jan 19 00:49:51 2008 (47918F7F)
7e000   ____________________________80734000 ???????????u???????????»?? Sat Jan 
85000   Unknown_Module_8077e000 Unknown_Module_8077e000 Sat Jan 19 00:49:42 2008 
93000   Unknown_Module_80785000 Unknown_Module_80785000 Sat Jan 19 00:49:40 2008 
a3000   ___________________ ????ĂŞ????????????? Sat Jan 19 00:49:13 2008 (47918F5
ab000   Unknown_Module_807a3000 Unknown_Module_807a3000 Sat Jan 19 00:49:40 2008 
c9000   Unknown_Module_807ab000 Unknown_Module_807ab000 Sat Jan 19 00:49:40 2008 
fb000   ________________________________ ??????????????????????????????? Sat Jan
c9000   nt       Âą            Sat Jan 19 00:30:58 2008 (47918B12)
fc000   __________ ?????????   Sat Jan 19 00:27:20 2008 (47918A38)
7a000   Unknown_Module_89a09000 Unknown_Module_89a09000 Sat Jan 19 00:41:20 2008 
85000   _G_______________________ ?G??????????????ĂŻ??c???? Sat Jan 19 00:55:51 2
b0000   ____________________________jj____G___ ???????????????????????????jj????
ea000   Unknown_Module_89bb0000 Unknown_Module_89bb0000 Sat Jan 19 00:56:19 2008 
f2000   ______________________ ????????>???????????? Sat Jan 19 00:56:48 2008 (4
0d000   Unknown_Module_89cf2000 Unknown_Module_89cf2000 Sat Jan 19 00:55:44 2008 
18000   _____    ?????        Sat Jan 19 00:28:54 2008 (47918A96)
51000   ____     ????         Sat Jan 19 00:50:10 2008 (47918F92)
.

The output should look like the following - which a few of your dumps did:
Code:
2000   kdcom    kdcom.dll    Sat Jan 19 02:31:53 2008 (4791A769)
2000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Jan 19
3000   PSHED    PSHED.dll    Sat Jan 19 02:31:21 2008 (4791A749)
b000   BOOTVID  BOOTVID.dll  Sat Jan 19 02:27:15 2008 (4791A653)
c000   CLFS     CLFS.SYS     Sat Jan 19 00:28:01 2008 (47918A61)
c000   CI       CI.dll       Fri Feb 22 00:00:56 2008 (47BE5708)
c000   fileinfo fileinfo.sys Sat Jan 19 00:34:27 2008 (47918BE3)
2000   Wdf01000 Wdf01000.sys Sat Jan 19 00:52:21 2008 (47919015)
f000   WDFLDR   WDFLDR.SYS   Sat Jan 19 00:52:19 2008 (47919013)
5000   acpi     acpi.sys     Sat Jan 19 00:32:48 2008 (47918B80)
e000   WMILIB   WMILIB.SYS   Sat Jan 19 00:53:08 2008 (47919044)
6000   msisadrv msisadrv.sys Sat Jan 19 00:32:51 2008 (47918B83)
d000   pci      pci.sys      Sat Jan 19 00:32:57 2008 (47918B89)
c000   partmgr  partmgr.sys  Sat Jan 19 00:49:54 2008 (47918F82)
b000   volmgr   volmgr.sys   Sat Jan 19 00:49:51 2008 (47918F7F)

.

.

I found multiple buchecks and most are listing as the probable cause simply as ????????????????, unknown module, unknown image or the Microsoft NT Kernel module ntrkpamp.exe.

Some of the bugchecks:
0x0000000a = 0xa = IRQL_NOT_LESS_OR_EQUAL and indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

0x0000007e = 0x7e = A system thread generated an exception - in this case the first parm of 0xc0000005 tells us that a memory violation occurred.

0x000000fc = 0xfc = An attempt was made to execute non-executable memory.

0x00000119 = 0x119 = The video scheduler has detected a fatal violation.

0x000000d1 = 0xd1 = A kernel-mode driver attempted to access pageable memory when it should not have

0x0000007f = 0x7f = The Intel CPU generated a trap and the kernel failed to catch this trap. The first parameter of 0x0000000d = indicates that an unknown exception occurred, possibly a protection fault that pertains to access violations for applications, which is indicative of a memory access violation.

Some of the mini kernel dumps were corrupted and not readable. The majority of them tell me that modules are paged-out or are corrupted.

I would place hardware issues before software ones at this time - simply b/c if the Vista installation was a corrupted as the dumps tend to indicate, I don't see how the system could perform at all.

I would like to see a Vista Health report from your system, please - do this:
START | type cmd.exe into the start search box | right-click on cmd.exe | run as administrator - the black "DOS" screen will appear - then type the following:
Code:
[b][size=3]
perfmon /report
[/b][/size]
It will run for 60+ seconds and open in an IE7 screen - save it in HTML format - very important. Zip it up and attach to your next post.

In the interim, I suggest you run a memory test using memtest86+ - click on the link in my signature area below. You will need to make an ISO and boot up w/it. Let it run all night.

I also recommend that you run chkdsk -
START | type cmd.exe into the start sesarch box | right-click on cmd.exe | run as administrator - the black "DOS" screen will appear - then the the following:
Code:
[b][size=3]
chkdsk /r
[/b][/size]
Answer YES to the question and re-boot.

I have included a summary dbug output below and have attached the full dbug output.

Regards. . .

jcgriff2

.

Code:
.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
.
BugCheck A, {89d3938c, 2, 1, 81cf585b}
Probably caused by : ????????????????????????????????? ( nt+b685b )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck 1000007E, {c0000005, 8e125ff8, 8c6a3b08, 8c6a3804}
Probably caused by : Unknown_Module_81c12000 ( nt+1d5b18 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck FC, {8eff5911, a1071101, 81d2db6c, 0}
Probably caused by : ?_?A?_ ( nt+a5155 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck A, {61, 1b, 1, 81cb5cb3}
Probably caused by : ? ( nt+b3cb3 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck 119, {1, 10117b1, 12e17b1, 12e17b0}
Probably caused by : Unknown_Module_81c09000 ( nt+cd163 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck A, {300, 1b, 0, 81cbacba}
Probably caused by : Unknown_Module_81c07000 ( nt+b3cba )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck D1, {8e61e810, 2, 1, 89f2a261}
Probably caused by : ? ( nt+5ad84 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck A, {0, 1b, 0, 81af9cba}
Probably caused by : ? ( nt+b3cba )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck D1, {15d, 2, 1, 8e507be9}
Probably caused by : ? ( nt+5ad84 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck 119, {1, 1ae43, 1bae43, 1bae42}
Probably caused by : Unknown_Module_81a3e000 ( nt+cd163 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck 1000007E, {c0000005, 8e92dff8, 8bf42b08, 8bf42804}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck A, {0, 1b, 0, 81ac9cba}
Probably caused by : ntkrpamp.exe ( nt!KiUnwaitThread+14 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck A, {90, 1b, 1, 81afdcbf}
Probably caused by : Unknown_Module_81a4a000 ( nt+b3cbf )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck D1, {c, a, 0, 8e91041f}
Probably caused by : ? ( nt+5ad84 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck 7F, {d, 0, 0, 0}
Probably caused by : ntkrpamp.exe ( nt!KiSystemFatalException+f )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck 119, {1, 17e97, 197e97, 197e95}
Probably caused by : ntkrpamp.exe ( nt!EtwpReserveTraceBuffer+ce )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck D1, {de34188, 2, 1, 8e42b04e}
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2ac )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck A, {4, ff, 1, 81a643e0}
Probably caused by : _ ( nt+543e0 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
.
*** WARNING: Unable to verify timestamp for ?????????????????????????????????
*** ERROR: Module load completed but symbols could not be loaded for ?????????????????????????????????
Debug session time: Wed Sep 10 03:41:44.881 2008 (GMT-4)
System Uptime: 0 days 0:27:18.082
*** WARNING: Unable to verify timestamp for ?????????????????????????????????
*** ERROR: Module load completed but symbols could not be loaded for ?????????????????????????????????
BugCheck A, {89d3938c, 2, 1, 81cf585b}
Probably caused by : ????????????????????????????????? ( nt+b685b )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
*** WARNING: Unable to verify timestamp for Unknown_Module_81c12000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_81c12000
Debug session time: Mon Sep  8 14:49:11.099 2008 (GMT-4)
System Uptime: 0 days 1:46:27.601
*** WARNING: Unable to verify timestamp for Unknown_Module_81c12000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_81c12000
BugCheck 1000007E, {c0000005, 8e125ff8, 8c6a3b08, 8c6a3804}
Probably caused by : Unknown_Module_81c12000 ( nt+1d5b18 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
*** WARNING: Unable to verify timestamp for ?ð?A?
*** ERROR: Module load completed but symbols could not be loaded for ?ð?A?
Debug session time: Wed Sep  3 17:09:47.215 2008 (GMT-4)
System Uptime: 0 days 2:45:29.928
*** WARNING: Unable to verify timestamp for ?ð?A?
*** ERROR: Module load completed but symbols could not be loaded for ?ð?A?
BugCheck FC, {8eff5911, a1071101, 81d2db6c, 0}
Probably caused by : ?_?A?_ ( nt+a5155 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
*** WARNING: Unable to verify timestamp for ?
*** ERROR: Module load completed but symbols could not be loaded for ?
Debug session time: Wed Sep  3 00:08:41.795 2008 (GMT-4)
System Uptime: 0 days 1:10:39.188
*** WARNING: Unable to verify timestamp for ?
*** ERROR: Module load completed but symbols could not be loaded for ?
BugCheck A, {61, 1b, 1, 81cb5cb3}
Probably caused by : ? ( nt+b3cb3 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
*** WARNING: Unable to verify timestamp for Unknown_Module_81c09000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_81c09000
Debug session time: Thu Aug 28 04:56:15.581 2008 (GMT-4)
System Uptime: 0 days 7:43:52.323
*** WARNING: Unable to verify timestamp for Unknown_Module_81c09000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_81c09000
BugCheck 119, {1, 10117b1, 12e17b1, 12e17b0}
Probably caused by : Unknown_Module_81c09000 ( nt+cd163 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
*** WARNING: Unable to verify timestamp for Unknown_Module_81c07000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_81c07000
Debug session time: Wed Aug 27 21:11:45.443 2008 (GMT-4)
System Uptime: 0 days 5:11:41.533
*** WARNING: Unable to verify timestamp for Unknown_Module_81c07000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_81c07000
BugCheck A, {300, 1b, 0, 81cbacba}
Probably caused by : Unknown_Module_81c07000 ( nt+b3cba )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
*** WARNING: Unable to verify timestamp for ?
*** ERROR: Module load completed but symbols could not be loaded for ?
Debug session time: Tue Aug 26 05:50:32.131 2008 (GMT-4)
System Uptime: 0 days 0:37:19.410
*** WARNING: Unable to verify timestamp for ?
*** ERROR: Module load completed but symbols could not be loaded for ?
BugCheck D1, {8e61e810, 2, 1, 89f2a261}
Probably caused by : ? ( nt+5ad84 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
*** WARNING: Unable to verify timestamp for ?
*** ERROR: Module load completed but symbols could not be loaded for ?
Debug session time: Sat Jul  5 00:10:50.005 2008 (GMT-4)
System Uptime: 0 days 2:59:04.746
*** WARNING: Unable to verify timestamp for ?
*** ERROR: Module load completed but symbols could not be loaded for ?
BugCheck A, {0, 1b, 0, 81af9cba}
Probably caused by : ? ( nt+b3cba )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
*** WARNING: Unable to verify timestamp for ?
*** ERROR: Module load completed but symbols could not be loaded for ?
Debug session time: Fri Jun 20 07:56:11.535 2008 (GMT-4)
System Uptime: 0 days 9:20:55.861
*** WARNING: Unable to verify timestamp for ?
*** ERROR: Module load completed but symbols could not be loaded for ?
BugCheck D1, {15d, 2, 1, 8e507be9}
Probably caused by : ? ( nt+5ad84 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
*** WARNING: Unable to verify timestamp for Unknown_Module_81a3e000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_81a3e000
Debug session time: Thu Aug  7 13:55:28.000 2008 (GMT-4)
System Uptime: 1 days 12:25:02.394
*** WARNING: Unable to verify timestamp for Unknown_Module_81a3e000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_81a3e000
BugCheck 119, {1, 1ae43, 1bae43, 1bae42}
Probably caused by : Unknown_Module_81a3e000 ( nt+cd163 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Debug session time: Sat Jul 19 18:59:19.563 2008 (GMT-4)
System Uptime: 0 days 2:40:46.267
BugCheck 1000007E, {c0000005, 8e92dff8, 8bf42b08, 8bf42804}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Debug session time: Thu Jul 17 05:45:22.861 2008 (GMT-4)
System Uptime: 0 days 6:30:18.351
BugCheck A, {0, 1b, 0, 81ac9cba}
Probably caused by : ntkrpamp.exe ( nt!KiUnwaitThread+14 )
PROCESS_NAME:  System
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
*** WARNING: Unable to verify timestamp for Unknown_Module_81a4a000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_81a4a000
Debug session time: Wed Jul 16 23:14:36.178 2008 (GMT-4)
System Uptime: 0 days 12:01:37.490
*** WARNING: Unable to verify timestamp for Unknown_Module_81a4a000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_81a4a000
BugCheck A, {90, 1b, 1, 81afdcbf}
Probably caused by : Unknown_Module_81a4a000 ( nt+b3cbf )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
*** WARNING: Unable to verify timestamp for ?
*** ERROR: Module load completed but symbols could not be loaded for ?
Debug session time: Wed Jul 16 03:06:40.764 2008 (GMT-4)
System Uptime: 0 days 0:43:29.064
*** WARNING: Unable to verify timestamp for ?
*** ERROR: Module load completed but symbols could not be loaded for ?
BugCheck D1, {c, a, 0, 8e91041f}
Probably caused by : ? ( nt+5ad84 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
Debug session time: Mon Jul  7 01:45:21.684 2008 (GMT-4)
System Uptime: 0 days 8:58:31.660
BugCheck 7F, {d, 0, 0, 0}
Probably caused by : ntkrpamp.exe ( nt!KiSystemFatalException+f )
PROCESS_NAME:  csrss.exe
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
Debug session time: Sun Jul  6 16:32:47.494 2008 (GMT-4)
System Uptime: 0 days 0:29:06.739
BugCheck 119, {1, 17e97, 197e97, 197e95}
Probably caused by : ntkrpamp.exe ( nt!EtwpReserveTraceBuffer+ce )
PROCESS_NAME:  System
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
Debug session time: Sun Jul  6 07:37:23.732 2008 (GMT-4)
System Uptime: 0 days 0:14:44.918
BugCheck D1, {de34188, 2, 1, 8e42b04e}
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2ac )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
*** WARNING: Unable to verify timestamp for Âą
*** ERROR: Module load completed but symbols could not be loaded for Âą
Debug session time: Thu May 29 17:48:47.366 2008 (GMT-4)
System Uptime: 0 days 4:01:21.132
*** WARNING: Unable to verify timestamp for Âą
*** ERROR: Module load completed but symbols could not be loaded for Âą
BugCheck A, {4, ff, 1, 81a643e0}
Probably caused by : _ ( nt+543e0 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
.
 
#12 ·
Okay,

So I did the memory test, and it only gets to about 14%, 29% overall, then freezes...I left it for a full day just to make sure.

It was telling me that there were some hardware problems.

Any other luck on your end?

Thanks!

-Fil
 
Status
Not open for further replies.
You have insufficient privileges to reply here.