Hey all
Over the past week my desktop pc has gotten 2 bsods and then restarted without any seeming damage. It never did this before in the 2 years I've owned it.
First error: system service exception(zrpnh.sys) (might be a bit off, couldn't really write it down fast and accurate before it restarted)
Second error: KERNEL_DATA_INPAGE_ERROR
Any idea what might cause this? I've got some ideas from my own:
- Recently (1 month ago) started working with Powershell for a class. Although this seems the most likely explanation, I don't exactly think I did something wrong. All we've really done so far are basic get-service, get-process commands and creating some variables (int string etc).
- Changed antivirus 1 month ago from AVG to Norton. I know, but AVG basically screwed over my laptop like 6 months ago by auto-deleting crucial system files, making sure the configuration screen stopped working as well as audio. I got Norton 365 for that laptop and it's been working like a charm, no issues so far. I decided to install it on my desktop as well, seeing as you're allowed to install it on 3 devices.
- Faulty hardware? First Google results show it could be attributed to a failed hard drive but I really think that's unlikely, this pc is only 2 years old and fairly well maintained.
Unfortunately I'm not sure what the exact reason is, could be something else entirely. Who knows it could be 1 off events and it won't happen again but I'd rather not have this happen while I'm working again. (rip essay)
Tips on how to look up the problem are appreciated.
ty
Hey all
Over the past week my desktop pc has gotten 2 bsods and then restarted without any seeming damage. It never did this before in the 2 years I've owned it.
First error: system service exception(zrpnh.sys) (might be a bit off, couldn't really write it down fast and accurate before it restarted)
Second error: KERNEL_DATA_INPAGE_ERROR
Any idea what might cause this? I've got some ideas from my own:
- Recently (1 month ago) started working with Powershell for a class. Although this seems the most likely explanation, I don't exactly think I did something wrong. All we've really done so far are basic get-service, get-process commands and creating some variables (int string etc).
- Changed antivirus 1 month ago from AVG to Norton. I know, but AVG basically screwed over my laptop like 6 months ago by auto-deleting crucial system files, making sure the configuration screen stopped working as well as audio. I got Norton 365 for that laptop and it's been working like a charm, no issues so far. I decided to install it on my desktop as well, seeing as you're allowed to install it on 3 devices.
- Faulty hardware? First Google results show it could be attributed to a failed hard drive but I really think that's unlikely, [url=http://www.cnet.com/products/acer-predator-g3620-ur308-core-i7-3770-3-4-ghz-12-gb-2-tb/specs/]this pc[/url] is only 2 years old and fairly well maintained.
Unfortunately I'm not sure what the exact reason is, could be something else entirely. Who knows it could be 1 off events and it won't happen again but I'd rather not have this happen while I'm working again. (rip essay)
Tips on how to look up the problem are appreciated.
ty
Powershell seems unlikely, I doubt you've been messing with individual blocks in the paging file.
I am 99.9% that you don't do maintenance on your hard drive. Random hard drive failures are called random because they can occur at any time for no particular reason. If you want to rule that out simply because it's unlikely I'll apply the same logic to KERNEL_DATA_INPAGE_ERROR: It's unlikely and therefore didn't happen.
Considering it's a SATA II HDD, I'd guess it's pre-2010, max 2011, so it'll probably have 3 (667GB) or 4 platters (500GB). Bonus: 7200rpm. I can definitely think of HDDs that are less likely to fail. You should definitely at least run Chkdsk.
It could also be the RAM. Run memtest86+.
Sidenote: 12GB RAM, possibly 2010 high-end HDD, B75 chipset, GT630 looks a lot like they were just trying to get rid of leftovers from high-end Nehalem systems (the RAM, HDD and maybe PSU (standard 80 PLUs, not even Bronze) and case), got a cheap mobo and GPU and then put an i7 in there to justify a 1000$ price tag. Welcome to the world of pre-builts.
Powershell seems unlikely, I doubt you've been messing with individual blocks in the paging file.
I am 99.9% that you don't do maintenance on your hard drive. Random hard drive failures are called random because they can occur at any time for no particular reason. If you want to rule that out simply because it's unlikely I'll apply the same logic to KERNEL_DATA_INPAGE_ERROR: It's unlikely and therefore didn't happen.
Considering it's a SATA II HDD, I'd guess it's pre-2010, max 2011, so it'll probably have 3 (667GB) or 4 platters (500GB). Bonus: 7200rpm. I can definitely think of HDDs that are less likely to fail. You should definitely at least run Chkdsk.
It could also be the RAM. Run memtest86+.
Sidenote: 12GB RAM, possibly 2010 high-end HDD, B75 chipset, GT630 looks a lot like they were just trying to get rid of leftovers from high-end Nehalem systems (the RAM, HDD and maybe PSU (standard 80 PLUs, not even Bronze) and case), got a cheap mobo and GPU and then put an i7 in there to justify a 1000$ price tag. Welcome to the world of pre-builts.
Disclaimer: I have a fair amount of experience with troubleshooting windows by doing odd jobs over the years, but I am by no means an expert. Do your own research before doing anything drastic based off what I have to say.
What I generally use for troubleshooting blue screens is this nifty MSDN page that documents most blue screens. This subsection describes your specific bluescreen. Unfortunately, quite a few causes of that are hard drive related, so I would back up and look into getting a new hard drive if I were you. Better safe than sorry.
If you want to do your own digging or figure out what the first blue screen was, you can take a look at the event viewer. Any time windows shuts down uncleanly, it will leave a log entry which can be viewed later. This will tell you what stop code (if any) was thrown. You can view all of these logs by opening the event viewer and filtering the system log to event ID 41, as seen here:
http://puu.sh/goUYU/994a087e85.png
I like to fiddle with my system and break it regularly, so you will probably not have quite as many to dig through. Timestamp and blue screen information (called bug check in the logs) will be under the EventData tree.
Disclaimer: I have a fair amount of experience with troubleshooting windows by doing odd jobs over the years, but I am by no means an expert. Do your own research before doing anything drastic based off what I have to say.
What I generally use for troubleshooting blue screens is this [url=https://msdn.microsoft.com/en-us/library/windows/hardware/hh994433.aspx]nifty MSDN page[/url] that documents most blue screens. [url=https://msdn.microsoft.com/en-us/library/windows/hardware/ff559197.aspx]This subsection[/url] describes your specific bluescreen. Unfortunately, quite a few causes of that are hard drive related, so I would back up and look into getting a new hard drive if I were you. Better safe than sorry.
If you want to do your own digging or figure out what the first blue screen was, you can take a look at the event viewer. Any time windows shuts down uncleanly, it will leave a log entry which can be viewed later. This will tell you what stop code (if any) was thrown. You can view all of these logs by opening the event viewer and filtering the system log to event ID 41, as seen here: [img]http://puu.sh/goUYU/994a087e85.png[/img]
I like to fiddle with my system and break it regularly, so you will probably not have quite as many to dig through. Timestamp and blue screen information (called bug check in the logs) will be under the EventData tree.
SetsulPowershell seems unlikely, I doubt you've been messing with individual blocks in the paging file.
I am 99.9% that you don't do maintenance on your hard drive. Random hard drive failures are called random because they can occur at any time for no particular reason. If you want to rule that out simply because it's unlikely I'll apply the same logic to KERNEL_DATA_INPAGE_ERROR: It's unlikely and therefore didn't happen.
Considering it's a SATA II HDD, I'd guess it's pre-2010, max 2011, so it'll probably have 3 (667GB) or 4 platters (500GB). Bonus: 7200rpm. I can definitely think of HDDs that are less likely to fail. You should definitely at least run Chkdsk.
It could also be the RAM. Run memtest86+.
Sidenote: 12GB RAM, possibly 2010 high-end HDD, B75 chipset, GT630 looks a lot like they were just trying to get rid of leftovers from high-end Nehalem systems (the RAM, HDD and maybe PSU (standard 80 PLUs, not even Bronze) and case), got a cheap mobo and GPU and then put an i7 in there to justify a 1000$ price tag. Welcome to the world of pre-builts.
Fair point lol, I'll look into the harddrive possibility. Ty
also yeah I know building your own pc is better both for your wallet and performance, but at the time I really didn't have the knowledge to do so without tons of problems. The local IT store that provided me the PC also gave 2 years warranty and free support forever on all products I bought there. I bought my laptop there too and they've fixed it twice free of charge. Idk, seemed like a fair deal at the time :P.
[quote=Setsul]Powershell seems unlikely, I doubt you've been messing with individual blocks in the paging file.
I am 99.9% that you don't do maintenance on your hard drive. Random hard drive failures are called random because they can occur at any time for no particular reason. If you want to rule that out simply because it's unlikely I'll apply the same logic to KERNEL_DATA_INPAGE_ERROR: It's unlikely and therefore didn't happen.
Considering it's a SATA II HDD, I'd guess it's pre-2010, max 2011, so it'll probably have 3 (667GB) or 4 platters (500GB). Bonus: 7200rpm. I can definitely think of HDDs that are less likely to fail. You should definitely at least run Chkdsk.
It could also be the RAM. Run memtest86+.
Sidenote: 12GB RAM, possibly 2010 high-end HDD, B75 chipset, GT630 looks a lot like they were just trying to get rid of leftovers from high-end Nehalem systems (the RAM, HDD and maybe PSU (standard 80 PLUs, not even Bronze) and case), got a cheap mobo and GPU and then put an i7 in there to justify a 1000$ price tag. Welcome to the world of pre-builts.[/quote]
Fair point lol, I'll look into the harddrive possibility. Ty
also yeah I know building your own pc is better both for your wallet and performance, but at the time I really didn't have the knowledge to do so without tons of problems. The local IT store that provided me the PC also gave 2 years warranty and free support forever on all products I bought there. I bought my laptop there too and they've fixed it twice free of charge. Idk, seemed like a fair deal at the time :P.