[phillpower2]

Rounding errors are caused by unstable voltages so we should check your PSU output, 

 

Please take expanded screenshots and only use the method below to attach them.

 

Download Speedfan and install it.  Once it's installed, run the program and post here the information it shows.  The information I want you to post is the stuff that is circled in the example picture I have attached.

If you are running on a vista machine, please go to where you installed the program and run the program as administrator.

 

 (this is a screenshot from a vista machine)

 

 Download then run HWMonitor and post a screenshot so that we have a comparison to the Speedfan results, details from here

 

To capture and post a screenshot;

Click on the ALT key + PRT SCR key..its on the top row..right hand side..now click on start...all programs...accessories...paint....left click in the white area ...press CTRL + V...click on file...click on save...save it to your desktop...name it something related to the screen your capturing... BE SURE TO SAVE IT AS A .JPG ...otherwise it may be to big to upload... then after typing in any response you have... click on browse...desktop...find the screenshot..select it and click on the upload button...then on the lower left...after it says upload successful...click on add reply like you normally would.

 

Screenshot instructions are provided to assist those that may read this topic but are not yet aware of the “how to”.

[Advertisements]

Here they are.

Sorry that SpeedFan picture isn't zoomed in enough

Attached Thumbnails

• 
• 

Edited by rei158, 11 November 2015 - 03:58 PM.

[rei158]

Here they are.

Sorry that SpeedFan picture isn't zoomed in enough

Attached Thumbnails

• 
• 

Edited by rei158, 11 November 2015 - 03:58 PM.

[phillpower2]

One of the memory slots is showing too high of voltage but other than that everything else looks ok, before suggesting any hardware check that involve opening the case we should take a look at the drivers, this can be long winded sometimes but at times can be quite quick, please read the following thoroughly before proceeding;

 

To see if we can identify any driver conflicts please refer to the copy/paste details below provided courtesy of  jcgriff2 

 

1. Create a Windows System Restore Point -

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8/ 8.1 - Using Microsoft System Restore (Windows*8) | HP® Support

2. Run Driver Verifier -

- Windows 7 & Vista - START | type verifier 
- Windows 8.1 & 8 - Press WIN +X keys | select "Command Prompt (Admin)" | type verifier 

Make these selections - 
1. Select 2nd option - Create custom settings (for code developers)
2. Select 2nd option - Select individual settings from a full list
3. Check these boxes -

▪ Special Pool 
▪ Pool Tracking 
▪ Force IRQL checking
▪ Deadlock Detection
▪ Security Checks (new as of Windows 7)
▪ Concurrency Stress Test (new as of Windows 8)
▪ DDI compliance checking (new as of Windows 8) 
▪ Miscellaneous Checks

4. Select last option - Select driver names from a list
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where "Microsoft" IS NOT the Provider
7. Click on Finish 
8. Re-boot[/HIDE]

 

 

- If the Driver Verifier (DV) finds a violation, it will result in a BSOD

 

- After re-start, you may not be able to log on to normal Windows

... • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up

... • Select "System Restore"

... • Choose the restore point that you created in step #1

 

- For Driver Verifier status

--- select last option, 1st screen -or-

--- type verifier /query (in a cmd/DOS screen)

- To turn Driver Verifier off - verifier /reset then re-boot

 

- The Driver Verifier needs to run as long as possible - even if the status screen appears clear.

- All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use

 

If your system does BSOD while the Driver Verifier is running, please retrieve the dump file from c:\windows\minidump and attach it to your next reply.

 

Please note that Driver Verifier may need to be left running for up to 72hrs, you should use the computer as you normally would and DV will not affect this unless a BSOD occurs.  

[rei158]

Is this normal? It is frozen. Or it should boot to desktop and verify in desktop?
Also there was no option for ddi and concurrency.

 

 

 

EDIT:
It was a freeze I guess. Restarted and it just booted like normal. Then I went through making those verifier options again and rebooted. It just booted up normally, queried the verify in cmd, it gave some long texts, but didn't look into it much. I haven't reset the verifier yet and will be going to sleep. Will be back at the same time tomorrow. 

Attached Thumbnails

• 

Edited by rei158, 11 November 2015 - 05:08 PM.

[phillpower2]

Just acknowledging that I have read your last post and will wait to hear back from you if you get a crash within the next 72 hrs etc.

[rei158]

Erm? I'm lost, did the verifier even work then? Or what should I be seeing if the verifier starts working.
The pc has just been crashing AS usually.

Edited by rei158, 12 November 2015 - 09:59 AM.

[phillpower2]

Have you checked whether or not DV is running by following the steps included in my reply #19

- For Driver Verifier status

--- select last option, 1st screen -or-

--- type verifier /query (in a cmd/DOS screen)

 

 

Can you upload only the last two dumps for us to take a look at while you check to see if DV is actually running.

[rei158]

Here they are.

Attached Thumbnails

• 

Attached Files

•  111215-16234-01.zip   40.85KB   300 downloads

[phillpower2]

Both dumps point towards the CPU but only one was a DV generated crashdump which tells us the following;

 

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.19045.x86fre.win7sp1_gdr.151019-1254
Machine Name:
Kernel base = 0x82c00000 PsLoadedModuleList = 0x82d42b90
Debug session time: Thu Nov 12 13:09:58.593 2015 (UTC - 5:00)
System Uptime: 0 days 0:00:24.218
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 8c3fe024, Address of the WHEA_ERROR_RECORD structure.
Arg3: b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 00000800, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 1f

STACK_TEXT:
80dca8ac 83019fcd 00000124 00000000 8c3fe024 nt!KeBugCheckEx+0x1e
80dca8e8 82cc4d44 8c3b5051 8c3fe024 82c56430 hal!HalBugCheckSystem+0xab
80dca918 8301a27f 852fc2d0 83027e40 00000000 nt!WheaReportHwError+0x230
80dcaa2c 8301a371 852fc2d0 852fc320 00000002 hal!HalpMcaReportError+0x3b
80dcaa50 8301a48d 00000000 852fc320 00000000 hal!HalpMceHandler+0x8b
80dcaa70 8301a5d6 00000000 852fc2d0 80dcab90 hal!HalpMceHandlerWithRendezvous+0x4b
80dcaa80 830105f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x34
80dcab90 8300d261 00000000 80dc5750 00000000 hal!HalpMcaExceptionHandler+0x87
80dcab90 00000000 00000000 80dc5750 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x124_GenuineIntel_VRF_PROCESSOR_BUS

BUCKET_ID: 0x124_GenuineIntel_VRF_PROCESSOR_BUS

Followup: MachineOwner

 

Can you do the following to see where this particular file is located;

 

Right click on the task bar then select Start Task Manager.

On the Processes tab, right click on csrss then select Properties, is csrss located in C:\Windows\System32 or somewhere else.

[rei158]

Yes, it is located in System32 folder. And there were two instances of csrss running in the task manager.

[phillpower2]

Did you check the location of both, if not can you do so and get back to us.

[rei158]

Yes, both are in C:\Windows\System32

[phillpower2]

Two instances of csrss running in the task manager is ok but not sure why there are two instances found in C:\Windows\System32, this aside for one moment while you do a couple of checks for us;

 

Can you first of all try running the computer in Safe Mode to see if it crashes, make a note of what happens then try Safe Mode with Networking and again make a note of what happens then get back to us.

[rei158]

That last answer was poorly written: both instances traced back to the same folder, but
there is only one csrss.

 

In Safe Mode only, I kept the computer running for 10 minutes, all seemed fine.
Then went to Safe Mode with networking and on first boot it crashed in "Please Wait" welcome screen
and gave 0x101 BSOD.

Then I tried again booting from Safe Mode only, no problems.
Now I am writing this in Safe Mode with Networking and it booted up normally.
 

Included the BSOD file just in case.

 

EDIT: 23:32- will be going to sleep now.

Attached Files

•  111215-16859-01.zip   21.83KB   308 downloads

Edited by rei158, 12 November 2015 - 03:33 PM.

[phillpower2]

No problem 

 

Your update throws slight doubt on this being a hardware issue, it still could be due to the fact that the computer was not under load when in Safe Mode but lets take a look at software for a moment.

 

Is ESET a paid for or a free/trial product.

 

How long has ESET been on the machine, does its installation coincide with the issue first starting.

 

Download and run DriverMax (free) from here and see what if any driver updates it suggests, let us know before updating anything, please note that you are only allowed to update two drivers a day for free.