Actually the files are not corrupted - they just need opening with 7-Zip, for some reason the default Windows file extract does not work.
Been having trouble with the IRQL_NOT_LESS_OR_EQUAL BSOD for many months now
- Thread starter stormflora
- Start date
Actually the files are not corrupted - they just need opening with 7-Zip, for some reason the default Windows file extract does not work.
More than once I have seen you comment on the fans ramping up just prior to a BSOD. I wonder if you have any thermal issues? Have you monitored temperatures during gaming and seen any spikes just prior to a BSOD?
Hi. . .
I used 7-zip to get them open. Normal Windows un-zip found them corrupted.
4 dumps, 3 different bugchecks. We are dealing with unknown hardware failure, I think.
Bugchecks -
The 0x1e is interesting because the exception record stated that the game could not be started.
Is it always the same game?
Have you fully tested RAM and hard drive?
Is this a desktop or laptop?
Sorry, I don't feel like reading the last 100 posts right now. Thanks.
Regards. . .
jcgriff2
I used 7-zip to get them open. Normal Windows un-zip found them corrupted.
4 dumps, 3 different bugchecks. We are dealing with unknown hardware failure, I think.
Bugchecks -
- 0x1e (0x80000004,,,) = kernel threw an exception, the exception =
"The game could not be started ([I][B]80000004[/B][/I])",; "NT" (Windows kernel) blamed, which is impossible and is just a default as the real culprit could not be identified. - (2) 0x3b (0xc0000005,,,) = system service threw an exception; exception = 0xc5 = memory access violation; Windows driver npfs.sys blamed, but could not be
- 0xa - driver attempted to access pageable memory when it was not supposed to; "NT" blamed
The 0x1e is interesting because the exception record stated that the game could not be started.
Is it always the same game?
Have you fully tested RAM and hard drive?
Is this a desktop or laptop?
Sorry, I don't feel like reading the last 100 posts right now. Thanks.
Regards. . .
jcgriff2
Sorry guys, I was creating my post when you posted!
Also, OP reported "UNEXPECTED_KERNEL_MODE_TRAP" - I did not see one of these.
JC
Also, OP reported "UNEXPECTED_KERNEL_MODE_TRAP" - I did not see one of these.
JC
As for the exception code 0x80000004, it means that a single step operation was performed. Is this related to the kernel debugger? Is it going to turn it off at all? If so, this would probably solve the blue screen problem (or it would be a good workaround)
- May 7, 2013
- 10,400
What are you referring to when you mean turn off? The kernel debugger? Or are you trying to prevent a BSOD from being shown by enabling the debugging mode at boot?
stormflora
Well-known member
- Jun 26, 2019
- 54
@philc43 Naturally, this was what I suspected as well, so back then (when I was first experiencing the BSODs), I did monitor both the CPU and GPU temperatures while gaming, and they were always safe, often even cooler than safe, so I stopped. But I don't mind doing that again just for debugging purposes.
@jcgriff2 Unfortunately, it's not always the same game. I play different games depending on my mood, and pretty much all of them are subseptible to BSODs, so I figured out that it wasn't just a game thing. It is a desktop.
@MrPepka @x BlueRobot I disabled all debugging (Driver Verifier, Debug Mode) a while back to try to use the system normally, as they were causing slowdowns and issues with using the PC. Surprisingly, even without those enabled, you have all still been able to analyze the dump files, so that's a good thing.
@jcgriff2 Unfortunately, it's not always the same game. I play different games depending on my mood, and pretty much all of them are subseptible to BSODs, so I figured out that it wasn't just a game thing. It is a desktop.
@MrPepka @x BlueRobot I disabled all debugging (Driver Verifier, Debug Mode) a while back to try to use the system normally, as they were causing slowdowns and issues with using the PC. Surprisingly, even without those enabled, you have all still been able to analyze the dump files, so that's a good thing.
Can you please provide a source for your definition of 0x80000004?
I got mine from. . .
mmc.exe won't open - application error 0x80000004
Many more examples from my Google search - 0x80000004 - Google Search
So, please provide us with the source of your interpretation for Exception error code 0x80000004 - like a table or other.
Thanks. . .
John
Also. . .
Sorry, but I have no idea what that means.
What is a "single step" and what does it refer to exactly?
Why would you want to turn off "single step" - assuming for the moment that you could turn it off?
What benefit(s) are derived by turning off "single step"?
Who exactly benefits from turning off "single step"? (I mean - does it benefit the BSOD Analyst by helping him/her figure out the actual cause of the BSOD -- or does it help the OP somehow by ending the BSOD epidemic?)
Lastly, why do you think that this "single step" is the cause of a BSOD?
For info, we had 4 BSODs in that last round -- bugchecks were 0x1e, (2) 0x3b, and a 0xa.
Which BSOD did this "single step" cause (what was the bugcheck of the BSOD)?
Thanks.
Did you ever test all 4 of your RAM sticks?
You need to test them with memtest86+ one stick at a time and alternate the slots - very important.
So, you will end up doing 16 tests - 7 passes minimum on each.
I know that you have 4 - 16 GB sticks - total RAM = 64 GB and these tests will likely be a PIA, but they really need to e done..
Test RAM with memtest.org MemTest86+
What do you do with that much RAM? :)
When the BSODs occur. . .
1. Do they occur only when you play games?
2. If yes, do the BSODs occur at the same general point in the games, i.e., at start-up? Or can you be playing a game for hours, then a BSOD hits?
3. How old is your hardware in general?
4. How old is your PSU?
5. What is the make, model and wattage of your PSU?
6. Have you replaced any of the hardware? i.e., RAM, HDD or SSD, PSU, CPU, Video card, motherboard...
7. Did you reinstall Windows last April because of the BSODs?
8. Where did you get your copy of Windows 10 from?
9. Is it a full retail version (If you bought it from Microsoft, it is full retail) or an OEM version?
Regards. . .
jcgriff2
You need to test them with memtest86+ one stick at a time and alternate the slots - very important.
So, you will end up doing 16 tests - 7 passes minimum on each.
I know that you have 4 - 16 GB sticks - total RAM = 64 GB and these tests will likely be a PIA, but they really need to e done..
Test RAM with memtest.org MemTest86+
What do you do with that much RAM? :)
When the BSODs occur. . .
1. Do they occur only when you play games?
2. If yes, do the BSODs occur at the same general point in the games, i.e., at start-up? Or can you be playing a game for hours, then a BSOD hits?
3. How old is your hardware in general?
4. How old is your PSU?
5. What is the make, model and wattage of your PSU?
6. Have you replaced any of the hardware? i.e., RAM, HDD or SSD, PSU, CPU, Video card, motherboard...
7. Did you reinstall Windows last April because of the BSODs?
Code:
Original Install Date: 4/6/2019, 10:58:46 PM9. Is it a full retail version (If you bought it from Microsoft, it is full retail) or an OEM version?
Regards. . .
jcgriff2
Please:
BSOD Bugcheck NTSTATUS VALUES (EXCEPTION ERROR CODES)
| 0x80000004 STATUS_SINGLE_STEP | {EXCEPTION} Single Step A single step or trace operation has just been completed. |
stormflora
Well-known member
- Jun 26, 2019
- 54
With all due respect, that sounds a bit overkill for RAM testing. I've done quite a bit of research over the months, and the general consensus online is that three passes is more than enough to catch anything, and that going above is actually prone to causing false positives because it is forcing the RAM to overheat. I have heard mentions about alternating the slots (which I admittedly have not yet tested as it is a bit of a pain to disassemble and reassemble the RAM with my physical setup), but I have done not one but two overnight tests for all 64 GB of the RAM together, with flying colours, so I am rather confident that the RAM is fine. Considering how long it would take to do 16 tests with seven passes each (it already takes like 1.5 hours or so for a single 64 GB pass) and the fact that I need to use my PC everyday for work, I'm going to reserve that test as an absolute last resort.
Gaming is not the primary purpose of this PC; I use a lot of programs that easily push past 32 GB. My sole reasoning for upgrading to 64 GB was because of that; I'd constantly hit the 32 GB limit and then experience instability. I occasionally game as a breather, but it is frustrating when my PC BSODs most of the time when doing so.
1 & 2) So far, with the exception of like one BSOD and the ones in the most recent report, all of the other BSODs have all occurred after gaming for several hours. They seem to occur randomly.
3) With the exception of the PSU and the GPU, I've actually replaced every piece of hardware in this PC during winter last year and gradually this year. The GPU is three years old.
4 & 5) The PSU is a 850W Gold from EVGA. I don't recall the exact date I purchased it, but I remember it was not too long ago. Definitely within the ballpark of three years. It has a ten year warranty.
6) As detailed in 3), yes, I've replaced almost everything. I even replaced all of my HDDs with SSDs last month, so that rules that out.
7) Yes I did. It was funny, actually. I wasn't planning on it, but my system got corrupted somehow and I couldn't boot the OS. I had to completely format it and install Windows 10 fresh.
8 & 9) It is fully retail, purchased digitally and registered on Microsoft's site.
In other news, I made some changes to some settings in my BIOS (underclocking my CPU and raising fan speeds) and have purchased a new GPU. I will see if conditions improve.
Last edited:
That error code I posted and asked all of the questions about - 0x80000004 ("single step") turns out to be what is called a "breakpoint" or "hard assert" purposefully placed in programs/apps to force them to crash at a certain point. I've never heard it referred to as a "single step" before, which is why I had no idea what it was.
Software developers place them in programs/apps for specific debugging purposes.
This means that possibly an app, driver or other software on your system contains a breakpoint - or several of them and it/they could be responsible for at least some of the BSODs. The error code tells us that.
There is no way for you to turn this off as breakpoints are hard-coded in the code itself.
That is the reason I asked you about Windows because there is what is known as a Windows "checked build" that contains many hard-asserts/breakpoints.
Do you have any other software installed that is related to games or is used by the games but is not directly related to any game?
The RAM testing is your call. I can only advise. All that I can tell you about BSODs - they can occur when RAM is not properly holding kernel code. This can be caused by RAM itself or some other underlying unknown hardware cause that affects RAMs ability to properly hold kernel code. This could be anything from heat, PSU, motherboard or other hardware that may affect RAM.
If you won't do the RAM tests, I would then suggest to run the system with just 1 stick of RAM at a time and play some games. Then try stick #2, etc...
2 or 3 passes testing RAM simply is not enough and testing all sticks together does not administer the test properly. That is my opinion from my 12+ years of experience working on BSOD threads as well as views held by hardware experts.
One thing that I would also suggest is to swap out the PSU and run the system with a different PSU and see if it BSODs.
You mentioned that you upgraded RAM. Did you add to existing RAM or did you buy all 4 - 16 GB sticks together new (the preferred method)?
Also, given the new SSD(s) - go to the SSD manufacturer's support site and check for a firmware upgrade. Lack of updated SSD firmware absolutely can cause BSODs.
The 0x80000004 Exception error code intrigues me the most.
However, given the sheer number of different bugchecks that you have experienced, some form of unknown hardware failure more than likely exists as well.
Regards. . .
jcgriff2
Software developers place them in programs/apps for specific debugging purposes.
This means that possibly an app, driver or other software on your system contains a breakpoint - or several of them and it/they could be responsible for at least some of the BSODs. The error code tells us that.
There is no way for you to turn this off as breakpoints are hard-coded in the code itself.
That is the reason I asked you about Windows because there is what is known as a Windows "checked build" that contains many hard-asserts/breakpoints.
Do you have any other software installed that is related to games or is used by the games but is not directly related to any game?
The RAM testing is your call. I can only advise. All that I can tell you about BSODs - they can occur when RAM is not properly holding kernel code. This can be caused by RAM itself or some other underlying unknown hardware cause that affects RAMs ability to properly hold kernel code. This could be anything from heat, PSU, motherboard or other hardware that may affect RAM.
If you won't do the RAM tests, I would then suggest to run the system with just 1 stick of RAM at a time and play some games. Then try stick #2, etc...
2 or 3 passes testing RAM simply is not enough and testing all sticks together does not administer the test properly. That is my opinion from my 12+ years of experience working on BSOD threads as well as views held by hardware experts.
One thing that I would also suggest is to swap out the PSU and run the system with a different PSU and see if it BSODs.
You mentioned that you upgraded RAM. Did you add to existing RAM or did you buy all 4 - 16 GB sticks together new (the preferred method)?
Also, given the new SSD(s) - go to the SSD manufacturer's support site and check for a firmware upgrade. Lack of updated SSD firmware absolutely can cause BSODs.
The 0x80000004 Exception error code intrigues me the most.
However, given the sheer number of different bugchecks that you have experienced, some form of unknown hardware failure more than likely exists as well.
Regards. . .
jcgriff2
stormflora
Well-known member
- Jun 26, 2019
- 54
Besides the everyday programs most people use nowadays (Steam, Discord, etc.), nothing else. I wouldn't imagine them causing problems. However, I do run games in borderless windowed, which means that anything else running on the system remains actively running. I would not be surprised if that has something to do with it. But I've played like this in the past as well without problems, so I haven't really considered it as a possibility.
I don't really have plans on changing the PSU for now. I used it in my previous system and never had any BSODs before. I'm doubtful that it would suddenly cause problems right after changing PCs.
The RAM are indeed four brand new sticks that I bought, installed, and immediately set the manufacturer settings to and tested with Memtest86 and Prime95.
I don't think the SSDs are the problem since I've been experiencing BSODs even before swapping them in for the HDDs. But I will look into that.
As mentioned, I did make some changes, so I will be back at the next BSOD incident.
I don't really have plans on changing the PSU for now. I used it in my previous system and never had any BSODs before. I'm doubtful that it would suddenly cause problems right after changing PCs.
The RAM are indeed four brand new sticks that I bought, installed, and immediately set the manufacturer settings to and tested with Memtest86 and Prime95.
I don't think the SSDs are the problem since I've been experiencing BSODs even before swapping them in for the HDDs. But I will look into that.
As mentioned, I did make some changes, so I will be back at the next BSOD incident.
stormflora
Well-known member
- Jun 26, 2019
- 54
Alright, so I have a special situation here. Now, I haven't encountered any real BSOD yet (I have played a few games for a few hours so far), but, I did attempt to run 3DMark and UserBenchmark, and they threw a BSOD as soon as they attempted to benchmark the system. I'm not sure if those BSODs are worth considering (after all, the best test is to just use the computer, and many agree that benchmarking stresses the PC), but if there's even a slight chance that they could be helpful, I have included the minidumps anyway.
According to WhoCrashed, the first one was by intelppm.sys, which I'm not too clear about, and the second one is by rdwm1203.sys, which is an audio driver for a device I have connected (I highly doubt it has problems; it might've been stressed to the point that it crashed).
Again, I'm not too concerned about these BSODs, since they were caused by benchmarking programs, not gaming. I can simply refrain from attempting to use them. I will be back again with any real BSODs that I encounter during PC use.
According to WhoCrashed, the first one was by intelppm.sys, which I'm not too clear about, and the second one is by rdwm1203.sys, which is an audio driver for a device I have connected (I highly doubt it has problems; it might've been stressed to the point that it crashed).
Again, I'm not too concerned about these BSODs, since they were caused by benchmarking programs, not gaming. I can simply refrain from attempting to use them. I will be back again with any real BSODs that I encounter during PC use.
Last edited:
Hi. . .
Why do you not consider these to be "real BSODs"? Any BSOD is serious as it tells us that there is something very wrong with your system, be it a rogue driver (which I think by now we have pretty much discounted software as the cause - although that BSOD with the 0x80000004 exception error code is somewhat bothersome) or unknown hardware failure.
Don't forget that you have had at least one (1) 0x124 bugcheck BSOD - WHEA = a Machine Check Exception, which is about as bad as it gets for hardware failure. 0x124 is very serious.
THE DUMPS
2 more BSODs and 2 more bugchecks.
The first dump -
0x1e (0xc000001d,,,) = the kernel threw an exception; the exception = 0xc000001d = an attempt was made to execute an illegal instruction (for example - division by zero). I do not know what exact illegal instruction was involved with your BSOD. So either a driver or app suddenly issued an illegal instruction here (where it did not do so before that we know of) or there may be a CPU problem.
The probable cause of this BSOD -
intelppm.sys = Intel Processor driver - Driver Reference Table (DRT) | intelppm.sys
This driver appears to be some kind of joint venture between Microsoft and Intel as the dumps do not list a timestamp for it, which is typical of Microsoft Windows drivers.
Please run this Intel CPU test - CPU STRESS testing: Mersenne.org Prime95 and Intel Processor Diagnostic Tool (IPDT)
The second dump -
0x133 - DPC Watchdog Violation
From Microsoft -
From Google -
The probable cause - your Roland audio driver -
Check for a driver update - Roland - Support - Updates & Drivers
Please also check on the SSD firmware.
System files generally are prone to corruption when they are being transferred back and forth between SSD/HDD and RAM. Before a driver or app can be executed, the system must load the module from the SSD into RAM. Then when no longer needed, it is unloaded from RAM and written back to the SSD. This process occurs every second that your system is powered on. Typically what happens is that a problem with RAM (or other underlying hardware failure that negatively affects RAM) and/or a problem with the SSD/HDD or other hardware part that can affect the hard drive fails and the complete file is not written back to the SSD/HDD or is not properly loaded into RAM. Then you end up with corrupted files.
Have you given any thought to my suggestion about running the system with just 1 RAM stick at a time?
We really do need to absolutely rule RAM itself in or out as a possible cause of the BSOD epidemic. Same with the SSDs.
Also, in Windows, "WATCHDOG" often refers to video. Please humor me and check in C:\Windows\LiveKernelReports\WATCHDOG directory. Are there any dumps in there? I've got 130 WATCHDOG dumps on my system - video failure; 0x117 - video TDR timeout; the video driver was unable to reset itself in the time allotted (30 seconds), but ultimately did before the 30 seconds was up. 0x117 Live Kernel Events can easily turn into 0x116 BSODs - where the system BSODs because the video driver was not able to reset itself within 30 seconds and crashed the system. A driver update solved my video problem, but I had no idea at the time that these 0x116's were occurring.
Also, can I please get an updated Sysnative app output?
Just run this app - SysnativeBSODCollectionApp - and upload and attach the output zip file to your next post. Thank you.
What I'm saying here is that I'll be more than happy to run every BSOD dump that you send to me. But if you are going to selectively implement my suggestions (or not do them at all - like the RAM tests), this is all pointless as I'm not really helping you to get any closer to actually solve these BSODs.
I can also guarantee you that you won't find BSOD Analysts as good and knowledgeable as you will here at Sysnative because more often than not, it is our staff members that go to the other forums and answer their BSOD threads! We also run the only BSOD Academy on the Internet.
All of our suggestions to you are of course yours to either do or not do. It is completely your call. But if you really want these BSODs solved, you should think about just following our lead and see where things end up.
Regards. . .
John
Why do you not consider these to be "real BSODs"? Any BSOD is serious as it tells us that there is something very wrong with your system, be it a rogue driver (which I think by now we have pretty much discounted software as the cause - although that BSOD with the 0x80000004 exception error code is somewhat bothersome) or unknown hardware failure.
Don't forget that you have had at least one (1) 0x124 bugcheck BSOD - WHEA = a Machine Check Exception, which is about as bad as it gets for hardware failure. 0x124 is very serious.
THE DUMPS
2 more BSODs and 2 more bugchecks.
The first dump -
0x1e (0xc000001d,,,) = the kernel threw an exception; the exception = 0xc000001d = an attempt was made to execute an illegal instruction (for example - division by zero). I do not know what exact illegal instruction was involved with your BSOD. So either a driver or app suddenly issued an illegal instruction here (where it did not do so before that we know of) or there may be a CPU problem.
The probable cause of this BSOD -
intelppm.sys = Intel Processor driver - Driver Reference Table (DRT) | intelppm.sys
This driver appears to be some kind of joint venture between Microsoft and Intel as the dumps do not list a timestamp for it, which is typical of Microsoft Windows drivers.
Please run this Intel CPU test - CPU STRESS testing: Mersenne.org Prime95 and Intel Processor Diagnostic Tool (IPDT)
The second dump -
0x133 - DPC Watchdog Violation
From Microsoft -
From Google -
The probable cause - your Roland audio driver -
Code:
RDWM1203.SYS Tue May 1 21:16:16 2018 (5AE93B90)Check for a driver update - Roland - Support - Updates & Drivers
Please also check on the SSD firmware.
System files generally are prone to corruption when they are being transferred back and forth between SSD/HDD and RAM. Before a driver or app can be executed, the system must load the module from the SSD into RAM. Then when no longer needed, it is unloaded from RAM and written back to the SSD. This process occurs every second that your system is powered on. Typically what happens is that a problem with RAM (or other underlying hardware failure that negatively affects RAM) and/or a problem with the SSD/HDD or other hardware part that can affect the hard drive fails and the complete file is not written back to the SSD/HDD or is not properly loaded into RAM. Then you end up with corrupted files.
Have you given any thought to my suggestion about running the system with just 1 RAM stick at a time?
We really do need to absolutely rule RAM itself in or out as a possible cause of the BSOD epidemic. Same with the SSDs.
No... it does not rule the SSD(s) out. SSDs are tantamount to RAM and therefore are prone to the same failures as RAM. I've seen many OPs with brand new RAM and SSDs that turn out to be bad. Also, the SSD(s) that you bought could have been sitting on a shelf somewhere for months or years; meanwhile the SSD manufacturer has released new firmware that has not been applied to your "new" SSDs. It is possible, so PLEASE check for firmware updates.
Also, in Windows, "WATCHDOG" often refers to video. Please humor me and check in C:\Windows\LiveKernelReports\WATCHDOG directory. Are there any dumps in there? I've got 130 WATCHDOG dumps on my system - video failure; 0x117 - video TDR timeout; the video driver was unable to reset itself in the time allotted (30 seconds), but ultimately did before the 30 seconds was up. 0x117 Live Kernel Events can easily turn into 0x116 BSODs - where the system BSODs because the video driver was not able to reset itself within 30 seconds and crashed the system. A driver update solved my video problem, but I had no idea at the time that these 0x116's were occurring.
Also, can I please get an updated Sysnative app output?
Just run this app - SysnativeBSODCollectionApp - and upload and attach the output zip file to your next post. Thank you.
What I'm saying here is that I'll be more than happy to run every BSOD dump that you send to me. But if you are going to selectively implement my suggestions (or not do them at all - like the RAM tests), this is all pointless as I'm not really helping you to get any closer to actually solve these BSODs.
I can also guarantee you that you won't find BSOD Analysts as good and knowledgeable as you will here at Sysnative because more often than not, it is our staff members that go to the other forums and answer their BSOD threads! We also run the only BSOD Academy on the Internet.
All of our suggestions to you are of course yours to either do or not do. It is completely your call. But if you really want these BSODs solved, you should think about just following our lead and see where things end up.
Regards. . .
John
Last edited:
stormflora
Well-known member
- Jun 26, 2019
- 54
Hi, I ruled it out those two BSODs because they didn't happen during normal operation and happened because I explicitly tried to benchmark my PC. I'm aware that benchmarking stresses the PC, so I wasn't surprised to see the BSODs happening.
---------------------------------------------------
I attempted to install and run the Intel Diagnostic Tool that you linked. Unfortunately, my PC completely froze at the very last test, the "CPULoad" test. There was no BSOD; the PC just hard froze. I had to force it to restart.
I restarted the PC, and I ran the test one more time, but with Core Temp running to monitor the temperatures. I noticed that on the "CPULoad" test, my CPU would hit 100C!! That's probably why the CPU froze; it reached a dangerous temperature and stopped.
I raised my fan speeds and tried the test again. It failed again, so I further raised my fan speeds and underclocked the CPU's AVX instructions. The test finally stabilized at a maximum of 98C and successfully finished the test.
Does this mean that my CPU has a potential overheating issue? Is that what's causing all of the BSODs to occur? In particular, with AVX instructions? I've attached the log file that the test produced.
On a side note, I attempted to use UserBenchmark again after making these changes, and it went through successfully with a max temperature of 95C. Maybe overheating was the culprit after all?
---------------------------------------------------
I checked Roland's site and there aren't any new drivers. I checked both the Samsung and Crucial sites for my SSDs, but there aren't any new drivers for them as well.
I apologize for being uncooperative with the RAM testing. I am simply trying not to inconvenience myself, as I need my PC for daily work. But I understand that it's difficult to assist when there is a lack of cooperation. Please tell me again: Exactly what would you like me to do? Simply use one single stick at a time?
I looked in the WATCHDOG folder as you requested, and it is empty. I have run the Collection App and attached the zip as requested.
---------------------------------------------------
I attempted to install and run the Intel Diagnostic Tool that you linked. Unfortunately, my PC completely froze at the very last test, the "CPULoad" test. There was no BSOD; the PC just hard froze. I had to force it to restart.
I restarted the PC, and I ran the test one more time, but with Core Temp running to monitor the temperatures. I noticed that on the "CPULoad" test, my CPU would hit 100C!! That's probably why the CPU froze; it reached a dangerous temperature and stopped.
I raised my fan speeds and tried the test again. It failed again, so I further raised my fan speeds and underclocked the CPU's AVX instructions. The test finally stabilized at a maximum of 98C and successfully finished the test.
Does this mean that my CPU has a potential overheating issue? Is that what's causing all of the BSODs to occur? In particular, with AVX instructions? I've attached the log file that the test produced.
On a side note, I attempted to use UserBenchmark again after making these changes, and it went through successfully with a max temperature of 95C. Maybe overheating was the culprit after all?
---------------------------------------------------
I checked Roland's site and there aren't any new drivers. I checked both the Samsung and Crucial sites for my SSDs, but there aren't any new drivers for them as well.
I apologize for being uncooperative with the RAM testing. I am simply trying not to inconvenience myself, as I need my PC for daily work. But I understand that it's difficult to assist when there is a lack of cooperation. Please tell me again: Exactly what would you like me to do? Simply use one single stick at a time?
I looked in the WATCHDOG folder as you requested, and it is empty. I have run the Collection App and attached the zip as requested.
Hi. . .
Thanks for running the tests and checking for the audio driver and the SSD firmware updates.
Then go onto mem stick #2 - same procedure for a day or 2. Then stick 3; same procedure; then stick 4; same procedure.
If RAM itself is the culprit here, testing it in this manner is the best way next to running the 16 tests.
I've asked a hardware expert to look in on your last post as I primarily sit on the software side of the fence and don't get into hardware issues all that often. I buy HP or Toshiba laptops and use them as they are.
My hardware experience is limited to changing a laptop hard drive and changing out 2 - 2 GB sticks of RAM for 2 - 4 GB sticks. That is about it. I've never built a system nor really ever opened up a desktop PC.
I am here and will be here to help until we hopefully figure your problematic system out. I can only imagine your frustration and do understand your reluctance to spend so much time testing components.
Hopefully, the hardware expert can shed more light on your inability to do benchmark tests as well as the problems with the Intel CPU test (which I have run on my laptop without any problems).
The reason that the CPU came up at all was that one of the last 2 dumps named the Intel Processor driver intelppm.sys as the probable cause.
Have a good night,
John
Thanks for running the tests and checking for the audio driver and the SSD firmware updates.
In lieu of testing each stick in all 4 slots each (16 tests), you should try to run the system with just 1 stick of RAM in a different slot than where it is now. Use the system like that for a day or 2; try to stress it.
Then go onto mem stick #2 - same procedure for a day or 2. Then stick 3; same procedure; then stick 4; same procedure.
If RAM itself is the culprit here, testing it in this manner is the best way next to running the 16 tests.
I've asked a hardware expert to look in on your last post as I primarily sit on the software side of the fence and don't get into hardware issues all that often. I buy HP or Toshiba laptops and use them as they are.
My hardware experience is limited to changing a laptop hard drive and changing out 2 - 2 GB sticks of RAM for 2 - 4 GB sticks. That is about it. I've never built a system nor really ever opened up a desktop PC.
I am here and will be here to help until we hopefully figure your problematic system out. I can only imagine your frustration and do understand your reluctance to spend so much time testing components.
Hopefully, the hardware expert can shed more light on your inability to do benchmark tests as well as the problems with the Intel CPU test (which I have run on my laptop without any problems).
The reason that the CPU came up at all was that one of the last 2 dumps named the Intel Processor driver intelppm.sys as the probable cause.
Have a good night,
John
Try using Hardware Monitor from CPUz to monitor the temps and voltages> HWMONITOR | Softwares | CPUID The Zip file is fine.
High temps can certainly be a cause of BSOD's however a failing CPU can also cause the temps to run high and BSOD.
If you run the benchmarking stress tests again while monitoring HWM and see the temps climb and and then have the failure I would remove the CPU heat sink clean off the old thermal paste and install new.
High temps can certainly be a cause of BSOD's however a failing CPU can also cause the temps to run high and BSOD.
If you run the benchmarking stress tests again while monitoring HWM and see the temps climb and and then have the failure I would remove the CPU heat sink clean off the old thermal paste and install new.
Has Sysnative Forums helped you? Please consider donating to help us support the site!