Hardware causing Blue Screen of Death

A friend of mine has been dealing with constant Blue Screen of Death (Windows 10) issues, so she handed her machine over to me to see if I could play technician.

My plan was straightforward—keep it simple and avoid unnecessary headaches by 😁 wiping the hard drive and performing a completely fresh installation of Windows. It seemed like an easy win: just kick off the install, catch a movie while the progress bar crawls along, and call it a day. 😉 Besides, that was actually what she wanted; the system was cluttered with absolute junk anyway.

Well, plans change. Now the OS is pristine—freshly installed, nothing on there except for the drivers that Windows automatically pulled in—yet the damn problem persists.

Basically, about two or three minutes after booting up, the blue screen hits:

"😢 Your PC ran into a problem and needs to restart. We’re just collecting some info, and then we’ll restart for you. If you would like to know more, you can search online later for this error: PAGE_FAULT_IN_NONPAGED_AREA – snp2uvc.sys"

I did some digging online and stumbled upon this: http://www.solvusoft.com/en/files/bs...r/snp2uvc-sys/ (I'm referring to the article itself, not the software they're trying to peddle for download)

I went through their ten-step guide, and when I reached step 10: Perform a Clean Installation of Windows, I noticed this warning:

please Note: If snp2uvc.sys errors still persist after a clean install of Windows, your SYS problem MUST be hardware related. If that is the case, then it is likely you will need to replace the associated hardware causing the snp2uvc.sys error.

So, we're looking at a hardware failure, but which component? What's the next move here? The machine is a Fujitsu laptop.

P.S. I ran a check disk, but it didn't flag anything—it just rebooted normally without any specific error messages—so I'm assuming the hard drive is fine.

I also ran a system scan (sfc /scannow), but it came up clean.

The issue doesn't trigger in Safe Mode. But once it boots up normally, after maybe two or three minutes—I haven't timed it perfectly, but it seems to happen consistently shortly after Windows fully loads—that blue screen pops up again.

Thomas Sanchez30 said:A friend of mine has been dealing with constant Blue Screen of Death (Windows 10) issues, so she handed her machine over to me to see if I could play technician.

My plan was straightforward—keep it simple and avoid unnecessary headaches by 😁 wiping the hard drive and performing a completely fresh installation of Windows. It seemed like an easy win: just kick off the install, catch a movie while the progress bar crawls along, and call it a day. 😉 Besides, that was actually what she wanted; the system was cluttered with absolute junk anyway.

Well, plans change. Now the OS is pristine—freshly installed, nothing on there except for the drivers that Windows automatically pulled in—yet the damn problem persists.

Basically, about two or three minutes after booting up, the blue screen hits:

"😢 Your PC ran into a problem and needs to restart. We’re just collecting some info, and then we’ll restart for you. If you would like to know more, you can search online later for this error: PAGE_FAULT_IN_NONPAGED_AREA – snp2uvc.sys"

I did some digging online and stumbled upon this: http://www.solvusoft.com/en/files/bs...r/snp2uvc-sys/ (I'm referring to the article itself, not the software they're trying to peddle for download)

I went through their ten-step guide, and when I reached step 10: Perform a Clean Installation of Windows, I noticed this warning:

please Note: If snp2uvc.sys errors still persist after a clean install of Windows, your SYS problem MUST be hardware related. If that is the case, then it is likely you will need to replace the associated hardware causing the snp2uvc.sys error.

So, we're looking at a hardware failure, but which component? What's the next move here? The machine is a Fujitsu laptop.

P.S. I ran a check disk, but it didn't flag anything—it just rebooted normally without any specific error messages—so I'm assuming the hard drive is fine.

I also ran a system scan (sfc /scannow), but it came up clean.

The issue doesn't trigger in Safe Mode. But once it boots up normally, after maybe two or three minutes—I haven't timed it perfectly, but it seems to happen consistently shortly after Windows fully loads—that blue screen pops up again.

You could try removing that driver (from what I can tell, it's camera-related) or updating it to a newer version.

Run a RAM test. Windows actually has MemTest built right in, and you shouldn't see a single error in the results...

People constantly assume their system is infected with malware just because some process is eating up CPU cycles or hogging bandwidth. In reality, it’s often just a legitimate Windows process doing its job and using those resources. It works the same way with drivers. A driver doesn't necessarily have to be malicious or broken; it might just be trying to write data to a corrupted segment of your RAM.

Ran memtest, and it came back clean—no errors found.

As for drivers—I checked Device Manager, and there isn't a single device showing an exclamation mark.

Here’s the situation: I went into msconfig and selected "selective startup," which ended up disabling a massive chunk of items under the "Services" tab. Now, when I leave certain things turned off, the system actually behaves... however, the catch is that my internet is completely dead 🙂.

Does anyone happen to know which specific services I need to toggle back on to get my connection working again? The dilemma is that if I just re-enable everything, I'm right back where I started—staring at the Blue Screen of Death.

Just grab Autoruns from Sysinternals, run it up, and see if you spot any red entries... maybe even grab a screenshot

http://i65.tinypic.com/nbsv4n.png 1
http://i68.tinypic.com/16bzd5t.png 2
http://i63.tinypic.com/6pbuko.png 3
http://i67.tinypic.com/10ykg1v.png 4
http://i64.tinypic.com/elb62g.png 5

There we go. I see some red text popping up, but frankly—I haven't the slightest clue what it's actually trying to tell me. 😁

All that red stuff over there shouldn't be happening... the yellow parts look totally fine to me...

You could try disabling them or just deleting those entries entirely. But honestly, if you're dealing with some smarter strain of malware, it'll just write itself right back into the registry the second you hit delete.

Maybe give HijackThis a shot to wipe everything out at once, though I suspect it hasn't seen an update in ages, so I'm not sure how much teeth it still has left...

Or just wait until you can get a hold of someone who actually knows their way around a terminal. Software isn't really my specialty.

Jeffrey Allen92 said:All that red stuff over there shouldn't be happening... the yellow parts look totally fine to me...

You could try disabling them or just deleting those entries entirely. But honestly, if you're dealing with some smarter strain of malware, it'll just write itself right back into the registry the second you hit delete.

Maybe give HijackThis a shot to wipe everything out at once, though I suspect it hasn't seen an update in ages, so I'm not sure how much teeth it still has left...

Or just wait until you can get a hold of someone who actually knows their way around a terminal. Software isn't really my specialty.

Alright, I'll give it a shot tomorrow. But honestly, why bring up malware when this machine is running a fresh, clean install of Windows?

By the way, I noticed we're technically in the hardware thread, yet the conversation seems to have drifted almost entirely toward software issues—so, if the moderators want to move this to a different section, feel free.

Thomas Sanchez30 said:Alright, I'll give it a shot tomorrow. But honestly, why bring up malware when this machine is running a fresh, clean install of Windows?

By the way, I noticed we're technically in the hardware thread, yet the conversation seems to have drifted almost entirely toward software issues—so, if the moderators want to move this to a different section, feel free.

You could just download Blue Screen View and run a scan with it. It'll show you exactly what's triggering the Blue Screen of Death.