System is encountering a crash, but won't run a minidump.


Recommended Posts

For the past week or so, my computer has been having a crashing problem in which i believe a hardware malfunction may be the issue. My top supporting factor is that for the past month or so, I've been getting this error every time i log into Windows.

 

ScriptHost.thumb.PNG.446bbcd849b0c38534acc0b8fd465c2e.PNG 

 

But the thing is, when the system crashes, there's no green screen of death or anything. (I am running 17025 Windows 10 RS4.)

 

Can i get this cleared up? I need a functioning computer to get me by until Summer 2018, when i will be building a new rig. (This one was built by my brother in 2014.)

CPU: AMD Phenom II X3 B75

MOBO: Gigabyte GA-78LMT-USB3 6.0

MEM: 8GB DDR3 Dual channel Unganged (I think the brand was TEAM or something.)

GRAPHICS: Nvidia Geforce GT 640

Edited by Jim K
adjusted image location for easier reading

Hello,

I've been encountering a problem with my Dec. 2014 system build. (The computer was built by my brother.)

 

Approximately a week ago, while playing Swordburst II, I encountered my first brush with this issue: The system crashes, goes to a pitch black screen, the audio is whizzing, pretty much everything you'd expect when the system crashes, but the system is not running a minidump, not showing up a BSOD, and is just simply staying put until i reboot the system, and it starts up like normal just fine with no issues. I also have a special program for diagnosing bluescreen event logs, called NirSoft BlueScreenView. Opening the program showed no loggings of any kind of minidump, confirming the fact that there is no minidump being activated.

 

I made a similar help post to this last night, and it was suggested that i update the video card drivers because i was (and still am, if that helps diagnose,) getting an nvidia.vbs script error every time the system would log in. After updating the video card drivers, i did notice a small boost in performance, but the problem still persists. I also came to another suggestion that it could be dust aggravation. (There was quite a lot of dust) so i had that blown out with an air compressor, still having the issue. A memtest also reported no problems with the memory modules.

 

There doesn't appear to be any physical damage to the system when i checked, so now i just don't know what the possibilities could be.

 

Can i get this cleared up? This thing needs to last me until at least Summer 2018, which is when i will be able to build a new rig. Hopefully it isn't a super-critical problem...

 

EDIT: Forgot to mention one thing: This problem only seems to be occuring, (at the moment,) when playing all kinds of games. Everything else, watching videos, typing documents, working in paint.net work perfectly with no hiccups in performance or errors.

Kind of obvious, but have you run sfc/scannow ? Also check using Dism /Online /Cleanup-Image /StartComponentCleanup  (1st) and Dism /Online /Cleanup-Image /RestoreHealth(2nd)

16 minutes ago, JoseyWales said:

Your hard drive is dying...

If it is (which is a possibility) I recommend using Crystal Disk Info to find out for sure.

On 11/11/2017 at 3:21 AM, SirWeathers said:

For the past week or so, my computer has been having a crashing problem in which i believe a hardware malfunction may be the issue. My top supporting factor is that for the past month or so, I've been getting this error every time i log into Windows.

 

ScriptHost.thumb.PNG.446bbcd849b0c38534acc0b8fd465c2e.PNG 

 

But the thing is, when the system crashes, there's no green screen of death or anything. (I am running 17025 Windows 10 RS4.)

 

Can i get this cleared up? I need a functioning computer to get me by until Summer 2018, when i will be building a new rig. (This one was built by my brother in 2014.)

CPU: AMD Phenom II X3 B75

MOBO: Gigabyte GA-78LMT-USB3 6.0

MEM: 8GB DDR3 Dual channel Unganged (I think the brand was TEAM or something.)

GRAPHICS: Nvidia Geforce GT 640

that error is very suspect, any positive hits on "nvidia.vbs" flag up potential malware infection. The Nvidia driver does not use visual-basic script.

 

https://www.enigmasoftware.com/wormvbsjenxcusa/files/2/

 

Run a chkdsk on your system partition. I saw all my pcs crash after upgrading windows 10 to the latest version. Chkdsk fixed it.

 

Although Nvidia driver does look the most likely cause. 

1 hour ago, Mando said:

that error is very suspect, any positive hits on "nvidia.vbs" flag up potential malware infection. The Nvidia driver does not use visual-basic script.

 

https://www.enigmasoftware.com/wormvbsjenxcusa/files/2/

 

I have to agree with Mando here, your system is crashing on a VBS file not a SYS file and that's very suspicious.   A vbscript file is running in your startup folder.... hmmm. That just screams malware.   I just looked on one of my RS4 machines that has an NVidia GPU and there is no nvidia.vbs file to be found. I think you have something else going on there. 

 

  

  • Like 2
  • Thanks 1
1 hour ago, Zag L. said:

I have to agree with Mando here, your system is crashing on a VBS file not a SYS file and that's very suspicious.   A vbscript file is running in your startup folder.... hmmm. That just screams malware.   I just looked on one of my RS4 machines that has an NVidia GPU and there is no nvidia.vbs file to be found. I think you have something else going on there. 

 

  

Gotcha!.thumb.PNG.bb5db351f0b615d72401ed8993b3c674.PNG

Gotcha! Thanks for the help, everyone. I haven't run confirmation benchmarks yet, but i will report back with results. I don't understand how an nvidia disguise trojan got into my system, but the bottom line is that it's gone, now. and i am no longer getting the startup message.

 

Also, I've run a CrystalDiskInfo scan, which detected no problems with the hard disk.

CrystalDisk.thumb.PNG.66204f7cc05a6957541e0cb4488fb5dc.PNG

  • Like 2
2 hours ago, Mando said:

whatever AV protection your using bin it and use a better one mate. 

Since i reinstalled Windows a few months ago, I diddn't have virus protection until i installed Malwarebytes Anti-Malware today.

 

However, despite removing the trojan, I am still encountering this problem, and i still need assistance. What else could it possibly be? Or did the trojan already take its toll?

8 hours ago, SirWeathers said:

Since i reinstalled Windows a few months ago, I diddn't have virus protection until i installed Malwarebytes Anti-Malware today.

 

However, despite removing the trojan, I am still encountering this problem, and i still need assistance. What else could it possibly be? Or did the trojan already take its toll?

Try looking at ALL the suggestions above. It's called troubleshooting.

Yeah -


Take a step back.
It seems you are only half-listening to the posts.  (ie thanking us, but not following the suggestions)

So far, me & 3-4 other people brought to your attention a VBS of nVidia in your startup.
I mentioned and joked "get rid of it - problem solved"  but others also mentioned it shouldnt be there.
You said you had no AV, but just MBAM - what did MBAM say ?

You need to have something else in addition to MBAM - MBAM's strength is removing the things that slip past your AV.
Did you just forget to run an AV ?  Are you in the habit of not using an AV ?  Were you relying on WIndows Defender ?
For AV, you can refer to neowin's list of AV software - I wont mention a recommendation because it will just derail the thread (because every person who isnt running what I recommend will chime in "Ive had [insert crap AV software] and I have no problems")

So, run MBAM again - does it pick up anything.  YOu mention the .vbs isnt there anymore, but then a little later - its back.  Did MBAM remove the .vbs ?  

If you want help, you need to tell us what you did, and what the results were, of your actions.
----------

 

Basically, we dont know 100% the .vbs is the culprit - its very suspicious, other claim they looked it up and its spyware - that might very well be the case.

If it were me,  I would do the following:

1.)  BACKUP ALL YOUR IMPORTANT STUFF

2.)  Re-run MBAM (post results of that scan)
3.) Install a good AV solution
4.)  Use a grfx driver cleaner program

5.) Install latest nVidia drivers  (leave off the nVidia Experience for now- the idea being as little variables as possible)
6.) Test

 

 

 

 

  • Like 2

I believe i may have found the problem. There's something i diddn't mention because i diddn't notice the sound until after i made my previous post reply. A grinding noise coming from the system.

 

I spoke to my former computer-science teacher at my high school, and he stated that it may have been a fan-related issue, so here's exactly what i did.

 

1. Opened up my computer, removed the video card and switched to onboard graphics.

2. OG result: Shortly after reaching the lock screen, the system did the crash, no bluescreen again, revealing that it apparently wasn't the video card.

3. Disabled the external fans.

4. Grinding traced back to the CPU cooler.

 

So, now that I found where it was coming from, I'm thinking the CPU cooler may need to be replaced, The things i haven't done yet that were suggested were the SFC scannow commands, the driver cleaner, and installing an actual AV. So i'll try out those and try the games again. I admit; I do have a little issue with listening to certain advice, and i'm sorry about that. I'll try not to have that happen again.

Umm, don't "assume" anything. DO THEM. put your ear by the fan. Do you hear any sound? It might be the HDD. Put your ear by it. You hear a scraping sound? THOSE are your answer.

 

Don't ask other people, they don't know your PC in and out. Only you do.

There are only 3 things that can make an audible noise - fan, optical drive, and HDD.

If your CPU fan is going out is can be overheating and causing issues.

But like Mindover said - dont assume anything.  Unless your computer science teacher actually got hands on time with your system - I'd keep troubleshooting.  (unless you gave him info you didnt mention in here)
 

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • In the boot options in the UEFI is set to legacy or CMS? It needs to be set to UEFI if it's not already.
    • Researchers claim Microsoft's quantum breakthrough is flawed by basic Python errors by Karthik Mudaliar Microsoft's aggressive roadmap to deliver a commercial quantum supercomputer by 2029 has now hit a bit of a snag, and it's not because of a complex sub-zero dilution refrigerator, but rather because of a few lines of basic Python code. A new critique published in the scientific journal Nature argues that simple software errors effectively manufactured the breakthrough that Microsoft's foundational research claimed back in 2025 into Majorana-based topological qubits. Topological quantum computing, the path that Microsoft chose for its research, relies on creating and controlling "Majorana zero modes." These are exotic quasiparticles that theoretically offer vastly superior error resistance compared to the highly sensitive superconducting qubits currently being championed by rivals like Google and IBM. However, physically proving you have created these particles requires sifting through massive amounts of complex electrical conductance data to isolate a specific "topological gap." Because of the sheer volume of data, physicists rely heavily on custom software pipelines to process the results. This is where the Python scripts come in. Now, according to the critique, Microsoft’s data processing software contained fundamental programming errors that ultimately skewed the published results. By mishandling data arrays or deploying incorrect logic within the Python script, the software supposedly discarded "noisy" or contradictory data. Which is why it only highlighted the specific electrical measurements that supported the topological-gap claim. The researchers behind the critique argued that this makes the findings invalid, suggesting the heralded "quantum leap" was actually a false positive generated by bad code and not a product of groundbreaking physics. However, Microsoft is pushing back hard against these allegations. The Redmond giant has formally rejected the criticism, saying that it's just a minor anomaly rather than a fatal flaw. According to the company, while there may have been a minor oversight in the data parsing scripts, it does not alter the fundamental reality of their physical experiment. Just weeks ago, Microsoft unveiled the Majorana 2 quantum processor, a milestone so significant that the company boldly accelerated its timeline for a commercial quantum supercomputer from 2035 down to 2029. But the new software allegations reopen an old wound. Microsoft's quantum division faced a remarkably similar crisis when a landmark 2018 paper on Majorana particles was famously retracted in 2021 after independent physicists discovered the data had been inappropriately cropped. That historical baggage makes the current Python-related allegations particularly sensitive. If the foundational math and data processing for the 2025 breakthrough are genuinely flawed, the highly anticipated 2029 commercial timeline could easily be delayed or, worse, cancelled.
    • Because of what they have done to VMware I will never buy anything Broadcom again.
  • Recent Achievements

    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
    • One Year In
      Tom Schmidt earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      465
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      123
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!