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

Win 10 64bit keeps crashing and can't update (Resolved).

- - - - -

Best Answer phillpower2 , 23 August 2016 - 03:58 AM

Hello Faina, What has been tried without success to correct the problems that you are having; Running Driver Verifier.Running the Windows All in One repair tool.Running Dism /Online /Clea... Go to the full post »


  • Please log in to reply

#1
Faina

Faina

    Member

  • Member
  • PipPipPip
  • 123 posts

Dear experts,

 

I have this problem for several months and I can't fix it, after hours spent looking for a solution... any help appreciated!!!

 

my perfectly working win7 64bit pc (done with the great advice here :) ) was "forced" to go to win 10: after I downloaded and installed all the latest drivers and firmware for everything. Now I have random crashes, even sometimes when the PC is just switch on with nobody using. You can work on it sometimes for hours without any problems and sometimes crash after 2 minutes. I've tried to narrow down the issue based on what I'm doing before the crash but I can't find any common thread...

Do I need to change any hardware?

Do I need to go through the very painful process of install again everything?

Is there any way to get a log with what causes the crash? The tools inside windows doesn't give me a clear indication, or I'm not able to read it.

Another thing is that if I try to update with the latest win 10 patch, the PC won't start anymore and I need to roll back. Already tried with and without the Norton

If possible, I would like to avoid "random" test like "make a clean installation and let see". Of course, if there isn't any other solution I will do that.

 

Configuration:

 

Intel i7 4770K 3.5GHz

Asus Z87-pro V edition

Ram DDR3 at 800MHz

Pantone Huey Pro 1.5.0

2 x Intel SSD 320 Series

Norton 360 latest update

 

Thanks to everybody!

 

cheers


  • 0

Advertisements


#2
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,352 posts

Hello Faina,

 

A fresh install is always a last resort but some times it is unavoidable I`m afraid  :(

 

Basics first please;

 

1. Copy any dmp files from C:\Windows\Minidump onto the desktop.

 

2. Select all of them, right-click on one, and click on Send To> New Compressed (zipped) Folder.

 

3. Upload the zip folder using the More Reply Options tab then the Attach button, bottom left of the dialogue input box 


  • 0

#3
Faina

Faina

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 123 posts

phillpower2,

 

thanks for your answer and sorry for the delay!

 

attached the file as you requested

 

thanks again for your support!!!

 

cheers

Attached Files


  • 0

#4
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,352 posts

Hello

 

A lot of crash dmps there so took a look at the first three and the latest three to see if there was a pattern, there is but nothing that identifies any particular driver or service/s so you could be looking at 1: bad RAM. 2: a flaky storage device, one of your crash dmps below to which I have added some notes in blue to what I have highlighted in red;

 

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a01f596419da9a, Reserved
Arg2: b3b72bdfb69a93d7, Reserved
Arg3: 0000000000000001, Failure type dependent information
Arg4: 0000000000000018, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
 
Debugging Details:
------------------
 
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
 
BUGCHECK_STR:  0x109
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
PROCESS_NAME:  System A driver or software issue would be named here if it was responsible for the crash, the fact that none are means it could be hardware related.
 
CURRENT_IRQL:  2
 
BAD_PAGES_DETECTED: 943e
 
LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff802145d2760
 
STACK_TEXT:  
ffffd000`ed1e20b8 00000000`00000000 : 00000000`00000109 a3a01f59`6419da9a b3b72bdf`b69a93d7 00000000`00000001 : nt!KeBugCheckEx
 
 
STACK_COMMAND:  kb
 
SYMBOL_NAME:  PAGE_NOT_ZERO
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: Unknown_Module As above no driver or software identified as the cause so could again point to bad RAM or storage device.
 
IMAGE_NAME:  Unknown_Image As above.
 
DEBUG_FLR_IMAGE_TIMESTAMP:  0
 
BUCKET_ID:  PAGE_NOT_ZERO
 
Followup: MachineOwner
---------
 
 *** Memory manager detected 37950 instance(s) of page corruption, target is likely to have memory corruption. Points towards bad RAM or flaky storage device.
 
Couple of things for you to do but will only suggest one at a time to make things easier for both of us;
 
Try running the computer in Safe Mode only (no networking) use the computer offline for a while and see if it crashes, if not, restart in Safe Mode with Networking, use the computer as you normally would including internet connection, see if the computer crashes and then post back with an update for us please.
 
Windows 10 Safe Mode instructions below courtesy of MS;
 
Restart your PC. When you get to the sign-in screen, hold the Shift key down while you select Power Power icon 
 > Restart.
After your PC restarts to the Choose an option screen, select Troubleshoot > Advanced options > Startup Settings > Restart.
After your PC restarts, you'll see a list of options. Select 4 or F4 to start your PC in Safe Mode. Or if you'll need to use the Internet, select 5 or F5 for Safe Mode with Networking.
 

  • 1

#5
Faina

Faina

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 123 posts

phillpower2,

 

thanks for the time spent to analyse my log files :)

 

FYI, my RAM is F3-1600C9D-16GAR: I don't mind to change it if this could be the problem. If yes, what do you recommend with similar spec, stability and that match my MB?

I have 2 hold HDD connected: is long time I want replace them so I will

Could be the 2 SSD cause of the issue? They are still supported by intel

 

I will do the test as suggested: please give me some time to do it

 

thanks!

 

cheers


  • 0

#6
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,352 posts

Hello Faina,

 

We cannot say for sure that anything needs to be replaced at the moment and really need to wait on the results of the testing in Safe Mode etc.

 

Specs that I find for your RAM is two 8GB sticks, is that correct.


  • 0

#7
Faina

Faina

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 123 posts

Phillpower2,

 

yes, it's 2 8Gb sticks

 

thanks

 

cheers


  • 0

#8
Faina

Faina

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 123 posts

Phillpower2,

 

I've done a 5h test on the PC in the 2 recovery mode (without and with the network) and it didn't crash, looks like everything normal. Could you please tell me what are the next steps?

 

thanks!!

 

cheers


  • 0

#9
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,352 posts

Apologies for the delay Faina  :(

 

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

 

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 10/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

 

 

- 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.  


  • 1

#10
Faina

Faina

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 123 posts

Phillpower2,

 

I can't even use my PC anymore if I enable the verifier. The PC crash all the time when Asus AI Suite 3 try to load. To make it usable again I've disable the command, but no dump file was generated.

 

The Concurrency Stress Test option is not available in Win10.

 

Could you please tell me if I'm wrong somewhere, or what are the next actions?

 

thanks

 

cheers


  • 0

Advertisements


#11
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,352 posts

Hello Faina,

 

I can't even use my PC anymore if I enable the verifier. The PC crash all the time when Asus AI Suite 3 try to load. To make it usable again I've disable the command, but no dump file was generated.

 

 

Temporarily disabling AI should allow DV to run but lets try something else first.

 

Download then run the Windows All in One Repair (free)  from here, disregard the malware guidance but follow the other steps to the letter and in particular ensuring that you first create a new restore point and perform a proper Windows clean boot before running the repair, details for the clean boot here.


  • 1

#12
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,352 posts

Not heard back from you Faina, do you still require assistance or is the issue now resolved, an update would be appreciated.


  • 0

#13
Faina

Faina

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 123 posts

Phillpower2,

 

apologise for the lack of response, I was packed with my job

 

I'll do the test tonight!

 

thanks!

 

cheers


  • 0

#14
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,352 posts

No problem, was just checking that you were still around.


  • 0

#15
Faina

Faina

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 123 posts

Phillpower2,

 

I've run the Windows All in One Repair, twice, in safe mode (restore point done, power reset done, registry back up done, clean boot done)

the PC is still starting :)

 

Do I need to run the DV now or do you want I do something else? Do you want the log?

 

Please let me know :)

 

thanks!

 

cheers


  • 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