[JSntgRvr]

Try the scan first. The /f wont hurt afterwards.

[Advertisements]

Alright, I'll try it in a sec. The PC crashed again and took me to the blue "Your PC ran into a problem" screen when idol, so I'm wondering if it has something to do with still having the graphics adapter disabled. Should I enable it from now on for these next checks?

[SunnySeven]

Alright, I'll try it in a sec. The PC crashed again and took me to the blue "Your PC ran into a problem" screen when idol, so I'm wondering if it has something to do with still having the graphics adapter disabled. Should I enable it from now on for these next checks?

[JSntgRvr]

It should not happen, as the driver is not active. Run the /f command.

[SunnySeven]

It seems I can't run any of the checks (chkdsk /f C: and chkdsk /scan) in safe mode and normal mode is still insanely slow. It'll be hours before I can see the command prompt let alone run something. I need some kind of process kill switch or something because whatever is running(probably that ransomeware) is slowing down the PC to a crawl.

Edited by SunnySeven, 25 January 2019 - 06:20 PM.

[JSntgRvr]

Iam on my cel and can't write much.

Boot to Windows recovery environment command prompt. At the prompt type the following and press enter.

BCDEDIT | Find "OSDEVICE"

Note the partition letter assigned.. Then type:

CHKDSK X: /R

Substitute the X above with the partition letter and press Enter.

Let me know the outcome.

[SunnySeven]

Man I completely forgot that there was a command mode for safe mode, must have been crazy tired the other day. Anyways, I ran a chkdsk /r C: on restart(completely missed that option as well the other day) and left the PC running for awhile. So I guess nothing went wrong.

[JSntgRvr]

Try to recreate the issue running MBAM.

[SunnySeven]

I still get a blue screen, the stop code this time mentions a "BAD OBJECT HEADER".

[JSntgRvr]

The bad pool header error means there's a problem with the way your computer is allocating memory.

 

Create a Restore Point.

 

Run Driver Verifier -
- Windows 10, 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)" click on Next
2. Select 2nd option - "Select individual settings from a full list" Click on Next
3. Check these boxes -

• Special Pool
• Force IRQL checking
• Pool Tracking
• Deadlock Detection
• Security Checks (new as of Windows 7)
• Miscellaneous Checks
• Power framework delay fuzzing (new as of Windows 8)
• DDI compliance checking (new as of Windows 8)
• Click Next

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

 
If Driver Verifier detects a violation, it will flag (disable) the offending driver and force a BSOD. The additional info added to the memory dump file will hopefully yield clues.

If you are unable to boot into normal Windows after VERIFIER_ENABLED BSOD -

• Boot into SAFEMODE - tap the F8 key repeatedly during boot-up
• Select "System Restore"
• Choose the restore point that you created

 

1. Download the Sysnative BSOD Dump + System File Collection App - save to Documents folder -    http:https://www.sysnative.com/blogs/download/sysnativebsodcollectionapp-exe/
 
2. Run the Sysnative app - Double-click on the downloaded EXE file
 
    The two outputs from the Sysnative app are:Publish a Speccy system snapshot and provide the web address for it in your message.  Here are downloadable step-by-step instructions for doing this:

• new folder created in Documents, SysnativeFileCollectionApp 
• a zipped version, SysnativeFileCollectionApp.zip

                     - Using Speccy,  PDF Format 
                     - Using Speccy,  MS-Word Format

[JSntgRvr]

Are we still ON?

[SunnySeven]

Yeah, just been a bit busy. From the looks of it, I'm unable to create a new restore point in any mode other than normal mode since safe mode doesn't have, or even allow a System Protection tab in the System Properties and normal mode is impossible to do anything. So my only option is to restore it to more than a month ago and redo everything in this thread. After reading further ahead, I realized none of the F# keys or shift + F# keys allow me to boot into advanced options since apparently this was disabled for some PC's running Windows 10. So I have no way of getting to the advanced boot options if something does go wrong.

 

Honestly though, I'm about ready to call it quits on the PC. No simple task is easy with this PC. The owner isn't going to mind too much.

[JSntgRvr]

I understand. That computer need an on site diagnostic. A place where a tech can troubleshoot the hardware components.

 

I don't see an issue in software.

 

Wish you luck!

 

Bets regards.

[SunnySeven]

Thanks for all your help, I really appreciate all the help you provided.

[JSntgRvr]

You are welcome.

 

I am proceeding therefore to close this topic.