Sysinternals and BSOD file collection

Joined
Nov 12, 2013
Posts
17
OS - Vistax64
original installed OS - yes
OEM
3 years
no re-install on OS

· CPU-
2.30 gigahertz AMD Phenom 9650 Quad-Core
· Video Card - onboard
ATI Radeon HD 3200 Graphics
· MotherBoard - MSI-748 (Aspen)
· Power Supply - Bestec 300W
· System Manufacturer- Hewlett Packard
· Exact model number - HP Pavillion A6750f


[h=1][/h]Thanks, I'm glad I found this site.
 

Attachments

Hi,

First off, there are no DMP files located in your jcgriff2 output folder. Can you please manually navigate to C:\Windows\Minidump and zip up and attach any dumps you may have?

In regards to the perfmon:

cause: A device is disabled preventing it from working properly.
details: The device, USB Wireless 802.11 b/g Adaptor, is disabled.

^^ Is this on purpose?

[TABLE="class: block"]
[TR]
[TD="class: h4"]cause:[/TD]
[TD="class: info b2, align: center"]A device is disabled preventing it from working properly.[/TD]
[/TR]
[TR]
[TD="class: h4, width: 12%"]details:[/TD]
[TD="class: info, align: center"]The device, High Definition Audio Controller, is disabled.[/TD]
[/TR]
[/TABLE]

^^ I presume this is disabled because of a possible 3rd party sound card is installed onto the system?

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

[TABLE="class: block"]
[TR]
[TD="class: h4"]symptom:[/TD]
[TD="class: info, align: center"]
warning.gif

The Security Center reports that Windows Update is disabled.[/TD]
[/TR]
[TR]
[TD="class: h4, width: 12%"]cause:[/TD]
[TD="class: info b2, align: center"]Windows Update is disabled.[/TD]
[/TR]
[/TABLE]

^^ Why? Re-enable it ASAP. Download all of the updates that aren't optional that you do not already have. If it's disabled because you don't like having updates download and install automatically, set it to check for but only download or install with your permission in the Update settings.

Regards,

Patrick
 
Hi,

First off, there are no DMP files located in your jcgriff2 output folder. Can you please manually navigate to C:\Windows\Minidump and zip up and attach any dumps you may have?

It Seem my minidump folder is empty///

In regards to the perfmon:

cause: A device is disabled preventing it from working properly.
details: The device, USB Wireless 802.11 b/g Adaptor, is disabled.

^^ Is this on purpose?

Yes it is

[TABLE="class: block"]
[TR]
[TD="class: h4"]cause:[/TD]
[TD="class: info b2, align: center"]A device is disabled preventing it from working properly.[/TD]
[/TR]
[TR]
[TD="class: h4"]details:[/TD]
[TD="class: info, align: center"]The device, High Definition Audio Controller, is disabled.[/TD]
[/TR]
[/TABLE]

^^ I presume this is disabled because of a possible 3rd party sound card is installed onto the system?

Again correct, I am using a USB sound card
----------------------------------------------------------------------

[TABLE="class: block"]
[TR]
[TD="class: h4"]symptom:[/TD]
[TD="class: info, align: center"]
warning.gif

The Security Center reports that Windows Update is disabled.[/TD]
[/TR]
[TR]
[TD="class: h4, width: 12%"]cause:[/TD]
[TD="class: info b2, align: center"]Windows Update is disabled.[/TD]
[/TR]
[/TABLE]

^^ Why? Re-enable it ASAP. Download all of the updates that aren't optional that you do not already have. If it's disabled because you don't like having updates download and install automatically, set it to check for but only download or install with your permission in the Update settings.

Regards,

Patrick

I check for updates manually, my system as of 11/17 is up to date. Thanks for the quick reply Patrick
 
Understood.

Can you please manually navigate to C:\Windows\Minidump and zip up and attach any dumps you may have and also answer my other questions in regards to disabled devices?

Regards,

Patrick
 
Understood.

Can you please manually navigate to C:\Windows\Minidump and zip up and attach any dumps you may have and also answer my other questions in regards to disabled devices?

Regards,


Patrick
The 2 hardware items are disabled by choice and or necessity. My minidump folder is empty.
 
Thanks.

Is there a MEMORY.DMP located in C:\Windows rather than the Minidump folder?

Regards,

Patrick
 
Yes, that explains it. Let it dump next time.

Regards,

Patrick

System finally "took a dump". It was the fastest one I'd ever seen.... Blue screen flashed quick then system rebooted. I went looking for the DMP file, no luck. I looked in windows/minidump, and windows root ...

Startup and Recovery settings follow...write an event to the system log- check, automatically restart - check, write debugging info - kernel memory dump, dump file: %SystemRoot%\MEMORY.DMP, overwrite existing file - check.

..
 
Do you have an SSD? If so, ensure the firmware is 100% up to date. If not, let's run some hardware diagnostics. Start with a Memtest for NO LESS than ~8 passes (several hours). If no errors after that, move onto chkdsk (attach log afterwards) and then Seatools:

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

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

Chkdsk:

Chkdsk:
There are various ways to run Chkdsk~


Method 1:

Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)

Elevated CMD should now be opened, type the following:

chkdsk x: /r

x implies your drive letter, so if your hard drive in question is letter c, it would be:

chkdsk c: /r

Restart system and let chkdsk run.

Method 2:


Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click <Check Now>.

If you'd like to get a log file that contains the chkdsk results, do the following:

Press Windows Key + R and type powershell.exe in the run box

Paste the following command and press enter afterwards:

get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

This will output a .txt file on your Desktop containing the results of the chkdsk.

If chkdsk turns out okay, run Seatools -

SeaTools | Seagate

You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).

Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.

Regards,

Patrick
 
Do you have an SSD? If so, ensure the firmware is 100% up to date. If not, let's run some hardware diagnostics. Start with a Memtest for NO LESS than ~8 passes (several hours). If no errors after that, move onto chkdsk (attach log afterwards) and then Seatools:

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

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

Chkdsk:

Chkdsk:
There are various ways to run Chkdsk~


Method 1:

Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)

Elevated CMD should now be opened, type the following:

chkdsk x: /r

x implies your drive letter, so if your hard drive in question is letter c, it would be:

chkdsk c: /r

Restart system and let chkdsk run.

Method 2:


Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click <Check Now>.

If you'd like to get a log file that contains the chkdsk results, do the following:

Press Windows Key + R and type powershell.exe in the run box

Paste the following command and press enter afterwards:

get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

This will output a .txt file on your Desktop containing the results of the chkdsk.

If chkdsk turns out okay, run Seatools -

SeaTools | Seagate

You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).

Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.

Regards,

Patrick

Memtest results are pass

I tried running the chkdsk powershell command, this was the result...
PS C:\Users\Carl> get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername -match "wininit"} | fl timecreated, message | out-file
Desktop\CHKDSKResults.txt


The term 'get-winevent' is not recognized as a cmdlet, function, operable progr
am, or script file. Verify the term and try again.
At line:1 char:13
+ get-winevent <<<< -FilterHashTable @{logname="Application"; id="1001"}| ?{$
_.providername -match "wininit"} | fl timecreated, message | out-file Desktop\
CHKDSKResults.txt
 
It's a *101 bug check, I am going to need a Kernel dump to properly analyze this as not enough information is stored in Minidumps for *101's.

Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > change from Small to Kernel Memory Dump.

Note that this will need to be hosted off of Sysnative as Kernel dumps are too large to host onsite. You can use hosting such as Skydrive, Mediafire, etc. Your choice.

Also...

You of course ran chkdsk BEFORE attempting to enter that command, right?

Regards,

Patrick
 
system recovery is set to kernel memory dump here %SystemRoot%\MEMORY.DMP, does that mean I can find that file in my c:/ directory?

Yes I ran chkdsk before running the command, still getting the same result, it doesn't seem to recognize get-winevent as a command
 
system recovery is set to kernel memory dump here %SystemRoot%\MEMORY.DMP, does that mean I can find that file in my c:/ directory?

You got it! It'll be called MEMORY.DMP in C:\Windows

Yes I ran chkdsk before running the command, still getting the same result, it doesn't seem to recognize get-winevent as a command

Strange, I am not sure. When you ran chkdsk, it didn't detect any bad sectors, etc, correct? If not, no log is necessary.

Regards,

Patrick
 
Great, thanks.

CLOCK_WATCHDOG_TIMEOUT (101)

This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

BugCheck 101, {31, 0, fffffa6001bd8180, 3}

31 clock ticks in regards to the timeout.

fffffa6001bd8180 is the PRCB address of the hung processor, let's keep this address in mind.

Running a !prcb on processor 0:

Code:
0: kd> !prcb 0
PRCB for Processor 0 at fffff80008d85680:
Current IRQL -- 13
Threads--  Current fffffa8006a02bb0 Next 0000000000000000 Idle fffff80008d8ab80
Number 0 SetMember 1
Interrupt Count -- 0110b8b0
Times -- Dpc    00000535 Interrupt 0000007f 
         Kernel 000ab73a User      0000e398

No match for address, let's try processor 1 this time:

Code:
0: kd> !prcb 1
PRCB for Processor 1 at fffffa60005e5180:
Current IRQL -- 0
Threads--  Current fffffa800b6ae060 Next fffffa8009718bb0 Idle fffffa60005eed40
Number 1 SetMember 2
Interrupt Count -- 01170f02
Times -- Dpc    00000aa5 Interrupt 000001e4 
         Kernel 000abda2 User      0000dd2a


Nope, no match either. I'll spare you the space in the post and tell you that processor #3 is the one we're looking for.

Code:
[/B][/I]0: kd> !prcb 3
PRCB for Processor 3 at [COLOR=#ff0000][U][I][B]fffffa6001bd8180[/B][/I][/U][/COLOR]:
Current IRQL -- 0
Threads--  Current fffffa800cdb9060 Next fffffa8006a02720 Idle fffffa6001be1d40
Number 3 SetMember 8
Interrupt Count -- 017bc2fd
Times -- Dpc    0000419d Interrupt 00001843 
         Kernel 000ac7fb User      0000d1e3

For reference, I did not do !prcb 0 through 6. That would have been very tedious. Instead, you can run the !running -it command. The "i" argument causes it to display idle procs too, and "t" displays the stack trace for the thread running on each proc.

Hint: At times, the 4th parameter of the bugcheck will show you the responsible processor. For example, in your *101 here, it was correct as the 4th parameter was 6.

As this matches the 3rd parameter of the bugcheck, processor #3 is the responsible processor. Now with the information we have here thus far, we know that processor #3 reached 31 clock ticks without responding, therefore the system crashed. Before we go further, what is a clock tick? A clock interrupt is a form of interrupt which involves counting the the cycles of the processor core, which is running a clock on the processors to keep them all in sync. A clock interrupt is handed out to all processors and then they must report in, and when one doesn't report in, you then crash.
If we look specifically at processor #3, we can see it did...well... nothing:

Code:
3: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0

Now how and why did this take place? First, let's check the IRQL of each one of the processors before the system crash:


Code:
3: kd> !irql 0
Debugger saved IRQL for processor 0x0 -- 13
3: kd> !irql 1
Debugger saved IRQL for processor 0x1 -- 0 (LOW_LEVEL)
3: kd> !irql 2
Debugger saved IRQL for processor 0x2 -- 0 (LOW_LEVEL)
3: kd> !irql 3
Debugger saved IRQL for processor 0x3 -- 0 (LOW_LEVEL)

As you can see, the IRQL of the first processor is 13 (which is CLOCK for x64 processors) and the rest are all 0. So we can see that only Processor 0 was at CLOCK level.

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

Now that we have the IRQL, let's look at the call stack of the different processors for more info. Let's start with Processor 0:

Code:
0: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffffa60`01f246d8 fffff800`08c28380 : 00000000`00000101 00000000`00000031 00000000`00000000 fffffa60`01bd8180 : nt!KeBugCheckEx
fffffa60`01f246e0 fffff800`08c62a4a : fffff800`09155460 fffffa60`01f24800 fffffa60`01f24850 fffff800`09155460 : nt! ?? ::FNODOBFM::`string'+0x2df4
fffffa60`01f24720 fffff800`09132f04 : 00000000`00000000 00000027`8d99c1f2 00000000`00000000 00000027`8d99f9dd : nt![COLOR=#ff0000][I][B]KeUpdateSystemTime[/B][/I][/COLOR]+0xea
fffffa60`01f24750 fffff800`08c6220d : 00000000`00000000 00000000`5dffe0dd 00000000`000007ff 00000000`00000000 : hal![COLOR=#ff0000][I][B]HalpHpetClockInterrupt[/B][/I][/COLOR]+0x8c
fffffa60`01f24780 fffff800`08c91305 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000003 : nt!KiInterruptDispatchNoLock+0x14d (TrapFrame @ fffffa60`01f24780)
fffffa60`01f24910 fffff800`08c746d1 : fffffa80`0a8c4008 fffffa80`0a8c7cf0 fffffa80`0a8c4000 00000000`00031f35 : nt!KeFlushTb+0xc1
fffffa60`01f24940 fffff800`08d0a18a : fffff700`01080498 00000000`00000000 fffffa80`0a8c4000 00000000`73576d4d : nt!KeFlushMultipleRangeTb+0x111
fffffa60`01f24980 fffff800`08d2dc21 : fffffa80`0d3b5ac0 00000000`00000001 fffffa60`01f24bb0 fffffa60`01f24be0 : nt!MiAgeWorkingSet+0x4ca
fffffa60`01f24b40 fffff800`08c152e0 : fffffa80`00000c3b 00000000`00000002 fffff800`08dc2408 00000000`00000000 : nt!MiProcessWorkingSets+0x231
fffffa60`01f24bb0 fffff800`08c7cdd0 : fffffa80`06a02b00 00000000`00000001 00000000`00000008 00000000`00000008 : nt! ?? ::FNODOBFM::`string'+0x34ba0
fffffa60`01f24c10 fffff800`08e75227 : fffffa80`06a02bb0 00000000`00000080 00000000`00000000 00000000`00000001 : nt!KeBalanceSetManager+0x120
fffffa60`01f24d50 fffff800`08ca6456 : fffffa60`01b66180 fffffa80`06a02bb0 fffffa60`01b6fd40 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`01f24d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

Look from bottom to top, we can see it goes through various calls.. etc... then we reach the interrupt which happens to be a clock interrupt. If we look right above, we can see that this clock interrupt was involved in updating the system time. This must happen across ALL processors so everything is timed correctly and nothing falls out of sync.

What we can say from this is processor 0 went ahead and took care of a clock interrupt that's in charge of keeping track of things being in time, and processor 3 didn't do... anything. Why did it not do anything whatsoever? Well, if we take a look at the other call stacks from the other processors, we see nothing 3rd party related (device drivers, etc):

Code:
1: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffffa60`0f78e4c0 fffff800`08c67cd9 : 00000000`00000001 fffffa80`08789a20 fffffa80`07bd7800 ffffffff`fc140000 : nt!MmAccessFault+0xc18
fffffa60`0f78e5a0 fffff800`08ec7300 : 00000000`0000000d 00000000`00000000 00000000`00000000 fffffa80`0ae1a770 : nt!KiPageFault+0x119 (TrapFrame @ fffffa60`0f78e5a0)
fffffa60`0f78e730 fffff800`08ec7417 : 00000000`0001020d 00000000`00000000 00000000`00000000 fffff800`08ca75a5 : nt!MiPerformFixups+0x140
fffffa60`0f78e790 fffff800`08c4d5d0 : 00000000`0003b8f5 fffffa60`005e57f0 fffffa80`00b2adf0 fffff800`08c4ef99 : nt!MiRelocateImagePfn+0x107
fffffa60`0f78e7f0 fffff800`08ec74cd : fffffa80`0b595e70 fffff6fd`30081060 fffff6fd`00000002 fffffa80`00000001 : nt!MiValidateImagePages+0x280
fffffa60`0f78e8a0 fffff800`08eb48a5 : ffffffff`ffffffff fffffa80`0b595e70 fffff880`1a0cbbe0 fffff880`000002cf : nt!MiSwitchBaseAddress+0x61
fffffa60`0f78e8e0 fffff800`08ed8ce4 : 00000000`00000004 00000000`01000000 00000000`00000000 00000000`01000000 : nt!MiRelocateImageAgain+0xf5
fffffa60`0f78e920 fffff800`08eacecc : fffffa60`0f78eb70 00000000`00000000 00000000`00000000 fffffa60`0f78eb68 : nt![COLOR=#ff0000][I][B]MmCreateSection[/B][/I][/COLOR]+0x284
fffffa60`0f78eb20 fffff800`08c68bf3 : fffffa80`0b6ae060 00000000`0000000f 00000000`017ce198 00000000`00000000 : nt![COLOR=#ff0000][I][B]NtCreateSection[/B][/I][/COLOR]+0x15f
fffffa60`0f78ebb0 00000000`777b731a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffffa60`0f78ec20)
00000000`017ce178 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777b731a

^^ NtCreateSection is a routine that creates a section object (represents a section of memory that can be shared).

Code:
2: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffffa60`0f232a50 fffff800`08c67cd9 : 00000000`00000001 fffffa60`0f232bb0 00000000`00000000 00000000`495e7280 : nt!MmAccessFault+0xc18
fffffa60`0f232b30 fffff960`00099655 : fffff960`000a51a8 00000000`00000000 fffff900`c6f32b20 00000000`00000000 : nt!KiPageFault+0x119 (TrapFrame @ fffffa60`0f232b30)
fffffa60`0f232cc8 fffff960`000a51a8 : 00000000`00000000 fffff900`c6f32b20 00000000`00000000 fffff960`000b012d : win32k!vAlphaPerPixelOnly+0x95
fffffa60`0f232cd0 fffff960`000a4da3 : fffff900`c2bd5bb0 fffff900`000001d4 00000000`00000750 fffff900`c2b099a0 : win32k!AlphaScanLineBlend+0x304
fffffa60`0f232d90 fffff960`0020a09c : fffff900`00000000 fffff900`00000000 fffff900`c2b099a0 fffff900`c2b099a0 : win32k![COLOR=#ff0000][I][B]EngAlphaBlend[/B][/I][/COLOR]+0x4f3
fffffa60`0f233040 fffff800`08c68bf3 : 00000000`64011250 00000000`00000000 00000000`00000000 fffff900`000001d4 : win32k!NtGdiAlphaBlend+0x163c
fffffa60`0f233420 000007fe`fe2051aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffffa60`0f233490)
00000000`0012af48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fe2051aa

^^ EngAlphaBlend function provides bit-block transfer capabilities with alpha blending. This is a technique by which the color in a source bitmap is combined with that in a destination bitmap to produce a new destination bitmap. GDI performs per-pixel alpha blending, according to the formula: Blend = Alpha * Source + (1 - Alpha) * Destination. This formula is used to compute the alpha blend at each pixel, for each of the red, green, and blue color channels.

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

Overall, from what I can see above with my personal knowledge, I am going to say this is completely a hardware issue given the routines and functions and lack of any sign of software. More specifically, if I had to make an educated guess, I'd say motherboard and/or processor. The hardware is 3 years old therefore it would not surprise me.

What are your options?

1. If your specific HP model has a PCI-e slot for installing a 3rd party video card, and if you have one laying around that the system can actually handle (older nVidia or AMD GPU would do jsut fine...) then I would install it and bypass integrated graphics. Don't go out and spend money on a 3rd party GPU to test this unless you can get one EXTREMELY cheap. I'd save the money for a new system, honestly.

2. If you still crash after #1, likely processor related.

3. If you have not already, I would go ahead with a full clean install of Windows with nothing but the latest drivers for your devices, etc. No 3rd party software (antiviruses, etc). Do this if you have not already to be absolutely sure there's not some fluke OS corruption going on and we just don't see it.

4. Update the BIOS if possible and/or available.

5. Memtest passed according to your reply above, so nothing I can really recommend in regards to that.

6. Clear CMOS and/or load optimized BIOS defaults to rule out any incorrect BIOS entries.

7. Replace the system (buy a new computer).

Regards,

Patrick
 
Ahh crap!!....

Ok, here is what I am observing.....the system crashes occur when watching.. say Netflix streaming, or working in photoshop(16 bit Canon RAW files). The memory.dmp file I sent, was a crash with my Nvidia 8400GS card installed. I removed the card, and went back to business as usual and boom, another crash, while working in Photoshop. Since Memtest was OK, and my drives read OK, maybe it's the CPU?.. I just replaced thermal paste on CPU about 3 months ago.. because it was running very hot (according to Speedfan), and I was getting blue screen crashes.
I have Prime 95, and CPU burn-in, and will run some tests with those. My current temps.. in fahenheit, System-208, CPU-122, Aux-215, Core-99..

Thanks for your help. I 'm trying to narrow the problem down so that I can direct what little funds I have toward the proper solution...
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top