BSOD (weird in general)

[SarK0Y]

next trouble which is very possible ==>> virus.

[Eric Veteran]

This is a Wolfsdale (Pentium D) system? It's very likely the processor. They were infernos.

[Atasas]

36 minutes ago, SarK0Y said:

next trouble which is very possible ==>> virus.

absolutely NO!

[Atasas]

34 minutes ago, Eric said:

This is a Wolfsdale (Pentium D) system? It's very likely the processor. They were infernos.

Utterly disagree!- best, most reliable CPU series ever! LGA775 socket

(not over-clocked or anything, unlike AMD nonsense, I used to get nightmares with)

 

Also, it is ever so simple configuration, not even PCI graphics card- driver missconfig- cant think of as possible, although remember few years ago, had to do something about that...

 

[Atasas]

Here are the results of nothing
 

 

Did, as said- uninstantiated drivers, let Windows update 

 

 

Went back to Intel update

 

 

updated that, restarted

and having the same- identical numbers of driver build

 

 

 

[SarK0Y]

1. well, how often your comp(uter) has went in bsod?

2. can you list symptoms/conditions before it gets bsod?

[Atasas]

Just for the sake of eliminating CPU- Run official "utility"

 

 

 

 

 

@SarK0Y

In relation to the BSOD's:

 

I had few happen few years ago- (don't remember for sure), but was playing with RAM, HDD's etc...

anyway, since, have build "gaming spec AMD rig", been using it on-off for few years, then that one started to go weird and it has been ASUS mobo capacitor's.

 

Re'started this one (Lenovo) for main usage for about few months now.

Had couple of them, until few weeks ago, it happened twice in a couple of days. 

"IMPORTANT" this 3ghz CPU is replacement (back inn) already, as I had E8200 (I think) before that in it...

 

Re'run all of the BIOS, Drivers scan's, defrag's etc- all has been good, on one (100% sure good 2gb RAM stick), until this evening...

 

 

[Atasas]

1 hour ago, Eric said:

This is a Wolfsdale (Pentium D) system? It's very likely the processor. They were infernos.

 

Bit lazy to dig up E8200 and it happened same way, as before... hardly, ever so hardly two of them misbehaving, especially, with only record evidence of such - Todays crash "report"...

[Atasas]

it just leaves:

 

MOBO (caps)?- hardly... as it worked for few weeks, before today...

 

Q35 driver (reinstalled once again today) or the actual Chip...?

 

SouthBridge Chip? or even NorthBridge????

 

PSU????? although ever so infrequent ~ hardly...

 

This HDD is replacement to an old- nope.

 

RAM- definitely good- tested again and un'pairing issue is not possible (clock speeds) as it is one stick in now

 

all in all no crash reports are "conclusive"...

 

 

 

 

I suppose, until next crash then....

 

[Atasas]

Just for the sake of eliminating SouthBridge CHIP re'run storage driver

 

 

 

 

[SarK0Y]

if system has physical faults, any OS will fail. that's very reason why i suggested to you to try another os. actually, you could try w7 x64 or even w10.

[Atasas]

37 minutes ago, SarK0Y said:

if system has physical faults, any OS will fail. that's very reason why i suggested to you to try another os. actually, you could try w7 x64 or even w10.

Yes, although, I wish I could be sure as what exactly is at fault, as although different OS'es might crash or not, after ALL the tests it should have shown?

 

anyway- found this old chestnut:

 

 

it only says SMART is not fully supported, although works as

 per 

https://en.wikipedia.org/wiki/S.M.A.R.T.

 

 

ANW "detailed report for hardware":

Spoiler

Passed

Thursday, April 13, 2017 23:58:20

Lenovo Solution Center Log File

Wdc-WDCWD1002FBYS-43P1B0-WD-WMATV4231302

DISPLAYNAME

WDC WD1002FBYS-43P1B0 ATA Device

Type

Internal HDD

Model

WDC WD1002FBYS-43P1B0

Manufacturer

Wdc

Serial

WD-WMATV4231302

Firmware

07.00L07

Size

931.51 GiB

Cache

31.9995 MB

Temperature

41 C

Physical Sector Size

512

Logical sector size

512

Logical sectors

1953525168

Supported standards

ATA8-ACS, ATA7-ATAPI, ATA6-ATAPI, ATA5-ATAPI, ATA4-ATAPI

Spec version

Version not reported

Partition schema

MBR

 

INDEX

1

File system

NTFS

Serial

007C29EE

Size

115.02 GiB

Used

26.74 GiB

Free

88.28 GiB

 

INDEX

2

File system

NTFS

Serial

00662662

Size

580.41 GiB

Used

118.77 GiB

Free

461.63 GiB

 

INDEX

3

File system

NTFS

Serial

8C4EEB7C

Size

197.02 GiB

Used

101.00 GiB

Free

96.03 GiB

 

Diagnostics

SMART status test

Passed

Targeted read test

Passed

Random seek test

Passed

Funnel seek test

Passed

SMART short self-test

Passed

SMART drive self-test

Not available

36DA9262

DISPLAYNAME

MAIN_MEMORY

Physical Memory

1.97 GB

 

INDEX

0

Manufacturer

Elpida

Speed

667 MHz

Size

2 GB

Part Number

4542453231554538414346412D36452D4520

Serial

36DA9262

 

Diagnostics

Advanced integrity test

Passed

 

 

 

[SarK0Y]

2 hours ago, Atasas said:

Yes, although, I wish I could be sure as what exactly is at fault, as although different OS'es might crash or not, after ALL the tests it should have shown?

it's not a fact that you'll be able to pinpoint your current problem, but at least you'll get running horsey. furthermore, so far according to your screenshots, seems machine is quite healthy.

[Atasas]

12 hours ago, SarK0Y said:

it's not a fact that you'll be able to pinpoint your current problem, but at least you'll get running horsey. furthermore, so far according to your screenshots, seems machine is quite healthy.

Until next crash...

 

BTW old CPU is only e4500 (not e8200), worked alright... Anyway would be pointless to change, even BSOD said CPU...

[+Warwagon MVC]

3 minutes ago, Atasas said:

Until next crash...

 

BTW old CPU is only e4500 (not e8200), worked alright... Anyway would be pointless to change, even BSOD said CPU...

 

Can you take a nice high quality of your motherboard and with the caps.

[SarK0Y]

1 hour ago, Atasas said:

Until next crash...

 

BTW old CPU is only e4500 (not e8200), worked alright... Anyway would be pointless to change, even BSOD said CPU...

my guess is, your trouble has been software-related. however, frequently even slight-abnormal voltage oscillation could lead to such faults. old cpu's are more bad-Voltage-tolerant.

[Atasas]

2 hours ago, warwagon said:

Can you take a nice high quality of your motherboard and with the caps.

Will do over the weekend

[Atasas]

48 minutes ago, SarK0Y said:

my guess is, your trouble has been software-related. however, frequently even slight-abnormal voltage oscillation could lead to such faults. old cpu's are more bad-Voltage-tolerant.

Guesses left.

I have been inclined to software... but ... doen't make sense TBH.

 

All together, I believe what remains is PSU and CPU and maybe even GPU being intermittent (???)

 

(South,/NothBridge ~ hardly, especially, since this machine never had major Gaming loads or several HDD's to cope with) for the caps to fail, also, when they fail- they just do, kept on going, but increasingly-repeatedly and even predictable way, ie rendering film or moving big files and error codes where somewhat indicating it to be so.

 

Tomorrow, I'll take few decent pics of hardware (MOBO)

[SarK0Y]

8 minutes ago, Atasas said:

I have been inclined to software... but ... doen't make sense TBH.

did you try another os'es? i met really bizarre software-related troubles.

16 minutes ago, Atasas said:

All together, I believe what remains is PSU and CPU and maybe even GPU being intermittent (???)

gpu? test another one. psu is about the same way -- test another one. but you said another cpu has run smoothly.

 

2 hours ago, Atasas said:

BTW old CPU is only e4500 (not e8200), worked alright...

so, we'd have:

 

1. faulty cpu.

2. faulty psu.

3. f'ed up drivers.

4. mixed trouble: for instance, psu & cpu are both f'ed up.

[Atasas]

Hardly related to BSOD's, but went on to play with drivers a bit... oh the memories!

 

 

And other, named Chell1.8b_Win7

 

...

anyway resolutions was issue, as my main display is my TV Hyundai A321 (Q321) with "native" resolution of 1366x768

Used "native"resolutions as in 1280x1024 and "custom ie 1360x768 etc, etc...

 

as in 

 

 

 

 

 

ended up woth M$ Update error...

 

as gone back to the default drivers etc...

 

 

 

as it is the one, that doesn't poke my eyes.

 

Used to be such pain and joy to fiddle with them drivers, core's etc ESPECIALLY with OMEGA for ATI ...

 

and having had some guests etc (Easter after-all_ had few beverages... will open up the case tomorrow..

Sorry chaps.