Question Plagued by blue screens

Toggle sidebar Toggle sidebar
M

Mastiff37

Distinguished
Jul 4, 2011
63
0
18,530
I'm hoping someone here can help me get to the bottom of my blue screen errors. I never had them when my system was Windows 10, but since Win 11, they have been happening every few days, and for some reason lately they are happening more like every few hours, often when I'm at the machine. This is the most recent one:

Source
Windows

Summary
Shut down unexpectedly

Date
‎5/‎6/‎2022 5:03 PM

Status
Report sent

Problem signature
Problem Event Name: BlueScreen
Code: 124
Parameter 1: 0
Parameter 2: ffffc807e8463028
Parameter 3: b2000000
Parameter 4: 10005
OS version: 10_0_22000
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.22000.2.0.0.768.101
Locale ID: 1033

Extra information about the problem
Bucket ID: 0x124_0_GenuineIntel_PROCESSOR_Mae_BANK0_MSCOD0001_MCACOD0005_PCC_UC_VRFK_IMAGE_GenuineIntel.sys
Server information: ec7c8c0f-6c53-4b6f-b020-0e6f0919f58b

Sometimes they generate the reports, but this one did not. What info can I provide so you gurus can help?
 
Sort by date Sort by votes
you will need to copy the minidump file from c:\windows\mindump directory to a cloud server, share the file for public access and post a link.
then someone can look at the diagnostic dump file in the windows debugger to see why the system shutdown.
 
Upvote 0 Downvote
Here's the intel test. I'll go after the minidump next. Like I said, some crashed recently only give the thing like in my original post, but I have recent crashes with dumps.

--- Genuine Intel Test ---
...
Version 1.0.19.64b.W
...

Expected -- GenuineIntel
Detected -- GenuineIntel

Genuine Intel CPU Module Success

--- Brand String Test ---
...
Version 1.0.23.64b.W
...

IntelR CoreTM i7-9700K CPU 3.60GHz

Brand String Module Success....

--- Cache Test ---
...
Version 1.0.18.64b.W
...

--- Reading Cache Size ---

- Detected L1 Data Cache Size -- 32
- Detected L1 Inst Cache Size -- 32
- Detected L2 Cache Size -- 256
- Detected L3 Cache Size -- 12288

Cache Module Success

--- MMXSSE Test ---
...
Version 1.0.25.64b.W
...
..DetectUtils64 DLL Version - 1.1.3

--- Determining MMX - SSE capabilities ---
..MMX is supported on this CPU..
..SSE is supported on this CPU..
..SSE2 is supported on this CPU..
..SSE3 is supported on this CPU..
..SSSE3 is supported on this CPU..
..SSE4.1 is supported on this CPU..
..SSE4.2 is supported on this CPU..

Testing MMX
Dot Product computed using C code 506
Dot Product computed using MMX intrinsics 506
MMX Dot Product Computation Test Passed
Passed MMX Test

Testing SSE
Dot Product computed using C code 506
Dot Product computed using SSE intrinsics 506
SSE Dot Product Computation Test Passed
Passed SSE Test

Testing SSE2
Complex Product computed using C code 23.00 -2.00i
Complex Product computed using SSE2 code 23.00 -2.00i
SSE2 Complex Product Computation Test Passed
Passed SSE2 Test

Testing SSE3
Complex Product using C code 23.00 -2.00i
Complex Product using SSE3 code 23.00 -2.00i
SSE3 Complex Product Computation Test Passed
Passed SSE3 Test

Testing SSSE3
SSSE3 Absolute Value Tests Passed
SSSE3 Arithmetic Tests Passed
SSSE3 Dot Product Test Passed
Passed SSSE3 Test

Testing SSE4.1
SSE4.1 Blend Tests Passed
SSE4.1 Min Max Tests Passed
SSE4.1 Insert Bit Tests Passed
SSE4.1 Extract Bit Tests Passed
SSE4.1 Bitwise Comparison Tests Passed
SSE4.1 Dot Product Test Passed
SSE4.1 Arithmetic Tests Passed
SSE4.1 Bit Conversion Tests Passed
SSE4.1 Bit Compare Test Passed
Passed SSE4.1 Test

Testing SSE4.2
SSE4.2 Bit Compare Test Passed
SSE4.2 Calculate Bit Set to 1 Test Passed
SSE4.2 CRC Test Passed
Passed SSE4.2 Test


MMXSSE Module Success

--- Integrated Memory Controller Test ---
...
Version 1.0.20.64b.W
...

--- Reading Memory Size ---

Detected Memory Size is -- 32.00GB


--- Subtest - Memory Size Test Passed ---


--- Integrated Memory Controller Stress Test ---

Memory to be allocated 1048576 bytes

Memory Allocated.

Test 1 Ones and Zeros Moving Inversions write operations - Passed

Test 1 Ones and Zeros Moving Inversions verification operations - Passed

Test 2 32Bits Sliding Ones write operations - Passed

Test 2 32Bits Sliding Ones verification operations - Passed

Test 3 32Bits Sliding Zero write operations - Passed

Test 3 32Bits Sliding Zero verification operations - Passed

Memory Deallocated.

--- Subtest - Memory Stress Test Passed ---


--- Integrated Memory Controller Test Passed ---
Parallel_PrimeNum
Version - 1.0.0.10

Parsing Parallel_PrimeNum.xml
Module GraphicsW.exe Disabled
Running Module Math_PrimeNum.exe -s 45 -resultName Math_PrimeNum_Parallel_PrimeNum_1_Results.txt
Module GraphicsW.exe Not Tested

--- Prime Number Generation Test ---
...
Version 1.0.23.64b.W
...

..DetectUtils64 DLL Version - 1.1.3
AVX is supported in your OS
Max AVX supported AVX2

Ops Per Sec CycleRun Error Timesec

4720 1 0 1
12253 4 0 2
8140 6 0 3
7960 8 0 4
7823 10 0 5
3870 11 0 6
7730 13 0 7
3842 14 0 8
4513 16 0 9
4533 18 0 10
4513 20 0 11
4495 22 0 12
4406 24 0 13
4482 26 0 14
2129 27 0 15
61261 30 0 16
41203 32 0 17
41290 34 0 18
61735 37 0 19
41048 39 0 20
41004 41 0 21
41177 43 0 22
61667 46 0 23
40821 48 0 24
40998 50 0 25
61676 53 0 26
40970 55 0 27
40931 57 0 28
42428 59 0 29
40510 61 0 30
42459 63 0 31
41913 65 0 32
41049 67 0 33
61979 70 0 34
41094 72 0 35
41319 74 0 36
40916 76 0 37
41295 78 0 38
40360 80 0 39
42090 82 0 40
211868 96 0 41
225976 111 0 42
225216 126 0 43
238526 142 0 44
224143 157 0 45

Operation Per Second -- 224143
Error -- 0

Prime Number Generation Test Passed

Module Math_PrimeNum.exe Completed - Pass

Result - Pass
Parallel_FP
Version - 1.0.0.10

Parsing Parallel_FP.xml
Module GraphicsW.exe Disabled
Running Module AVX.exe -s 45 -resultName AVX_Parallel_FP_1_Results.txt
Running Module Math_FP.exe -s 45 -resultName Math_FP_Parallel_FP_1_Results.txt
Module GraphicsW.exe Not Tested

--- Floating Point Test ---
...
Version 1.0.22.64b.W
...

..DetectUtils64 DLL Version - 1.1.3
AVX is supported in your OS
Max AVX supported AVX2
FMA3 supported
MFLOPS CycleRun Error Timesec

0.13 2 0 1
0.585 11 0 2
0.52 19 0 3
0.455 26 0 4
0.65 36 0 5
0.52 44 0 6
0.455 51 0 7
0.52 59 0 8
0.78 71 0 9
0.455 78 0 10
0.52 86 0 11
0.52 94 0 12
0.52 102 0 13
0.52 110 0 14
0.455 117 0 15
0.52 125 0 16
0.455 132 0 17
0.65 142 0 18
0.52 150 0 19
0.52 158 0 20
0.455 165 0 21
0.845 178 0 22
0.52 186 0 23
0.455 193 0 24
0.52 201 0 25
0.715 212 0 26
0.52 220 0 27
0.52 228 0 28
0.52 236 0 29
0.585 245 0 30
0.52 253 0 31
0.52 261 0 32
0.455 268 0 33
0.65 278 0 34
0.455 285 0 35
0.52 293 0 36
0.52 301 0 37
0.65 311 0 38
0.455 318 0 39
0.52 326 0 40
0.52 334 0 41
0.455 341 0 42
0.585 350 0 43
0.52 358 0 44
0.52 366 0 45

Million Floating Points per Second MFLOPS -- 0.52
Error -- 0

Floating Point Test Passed

Module Math_FP.exe Completed - Pass

--- AVX Test ---
...
Version 2.0.25.64b.W
...
..DetectUtils64 DLL Version - 1.1.3

--- CPU Features Detection ---
..AVX is supported by this CPU..
..AVX2 is supported by this CPU..
..AVX512BW is NOT supported by this CPU..
..AVX512CD is NOT supported by this CPU..
..AVX512DQ is NOT supported by this CPU..
..AVX512ER is NOT supported by this CPU..
..AVX512F is NOT supported by this CPU..
..AVX512IFMA52 is NOT supported by this CPU..
..AVX512PF is NOT supported by this CPU..
..AVX512VBMI is NOT supported by this CPU..
..AVX512VL is NOT supported by this CPU..
..AES is supported by this CPU..
..PCLMULQDQ is supported by this CPU..

..AVX is supported by this Operating System..

Most Advanced AVX Feature Detected.. AVX2

Testing Most Advanced AVX Feature - AVX2....
AVX2 Test Result --- PASS

Testing AES
AES Test Result --- PASS

Testing PCLMULQDQ
PCLMULQDQ Test Result --- PASS


AVX Module Success

Module AVX.exe Completed - Pass

Result - Pass
Parallel_Math
Version - 1.0.0.10

Parsing Parallel_Math.xml
Module GraphicsW.exe Disabled
Running Module Math_PrimeNum.exe -s 45 -resultName Math_PrimeNum_Parallel_Math_1_Results.txt
Running Module FMA3.exe -s 45 -resultName FMA3_Parallel_Math_1_Results.txt
Module GraphicsW.exe Not Tested

--- Prime Number Generation Test ---
...
Version 1.0.23.64b.W
...

..DetectUtils64 DLL Version - 1.1.3
AVX is supported in your OS
Max AVX supported AVX2

Ops Per Sec CycleRun Error Timesec

4471 1 0 1
10440 3 0 2
4000 4 0 3
4275 5 0 4
4371 6 0 5
4539 7 0 6
3889 8 0 7
3891 9 0 8
3918 10 0 9
2114 11 0 11
4067 12 0 12
3594 13 0 13
2156.5 14 0 15
27199 15 0 16
21074 16 0 17
45082 18 0 18
21954 19 0 19
23083 20 0 20
26327 21 0 21
22719 22 0 22
24694 23 0 23
23891 24 0 24
42585 26 0 25
25255 27 0 26
24047 28 0 27
23149 29 0 28
17555 30 0 29
24135 31 0 30
46881 33 0 31
21211 34 0 32
21602 35 0 33
17367 36 0 34
21291 37 0 35
40078 39 0 36
23071 40 0 37
18578 41 0 38
20527 42 0 39
17914 43 0 40
137681 49 0 41
108743 54 0 42
112960 59 0 43
121920 64 0 44
118947 69 0 45

Operation Per Second -- 118947
Error -- 0

Prime Number Generation Test Passed

Module Math_PrimeNum.exe Completed - Pass

--- FMA3 Test ---
...
Version 1.0.23.64b.W
...
..DetectUtils64 DLL Version - 1.1.3

--- CPU Features Detection ---
..FMA3 is supported by this CPU..
..FMA3 is supported by this Operating System..

Testing FMA3....
FMA3 Test Result --- PASS

FMA3 Module Success

Module FMA3.exe Completed - Pass

Result - Pass
Parallel_GPUStressW
Version - 1.0.0.10

Parsing Parallel_GPUStressW.xml
Module GPUStressW.exe Disabled
Running Module AVX.exe -s 30 -resultName AVX_Parallel_GPUStressW_1_Results.txt
Running Module FMA3.exe -s 30 -resultName FMA3_Parallel_GPUStressW_1_Results.txt
Module GPUStressW.exe Not Tested

--- AVX Test ---
...
Version 2.0.25.64b.W
...
..DetectUtils64 DLL Version - 1.1.3

--- CPU Features Detection ---
..AVX is supported by this CPU..
..AVX2 is supported by this CPU..
..AVX512BW is NOT supported by this CPU..
..AVX512CD is NOT supported by this CPU..
..AVX512DQ is NOT supported by this CPU..
..AVX512ER is NOT supported by this CPU..
..AVX512F is NOT supported by this CPU..
..AVX512IFMA52 is NOT supported by this CPU..
..AVX512PF is NOT supported by this CPU..
..AVX512VBMI is NOT supported by this CPU..
..AVX512VL is NOT supported by this CPU..
..AES is supported by this CPU..
..PCLMULQDQ is supported by this CPU..

..AVX is supported by this Operating System..

Most Advanced AVX Feature Detected.. AVX2

Testing Most Advanced AVX Feature - AVX2....
AVX2 Test Result --- PASS

Testing AES
AES Test Result --- PASS

Testing PCLMULQDQ
PCLMULQDQ Test Result --- PASS


AVX Module Success

Module AVX.exe Completed - Pass

--- FMA3 Test ---
...
Version 1.0.23.64b.W
...
..DetectUtils64 DLL Version - 1.1.3

--- CPU Features Detection ---
..FMA3 is supported by this CPU..
..FMA3 is supported by this Operating System..

Testing FMA3....
FMA3 Test Result --- PASS

FMA3 Module Success

Module FMA3.exe Completed - Pass

Result - Pass

--- DGEMM Stress Test ---
...
Version 1.0.11.64b.W
...
..DetectUtils64 DLL Version - 1.1.3

--- CPU Features Detection ---
..AVX is supported by this Operating System..

Most Advanced AVX Feature Detected.. AVX2

maxMatrixSize 1024

minMatrixSize 512

Testing Most Advanced AVX Feature - AVX2....
DGEMM AVX2 Test Result --- PASS


DGEMM Module Success

--- Frequency Check ---
...
Version 1.0.3.64b.W
...
..........
..Expected Frequency -- 3.60
..Measured frequency -- 3.59728
..

FrequencyCheck Passed....
 
Upvote 0 Downvote
Mastiff37 said:
Are you able to access this? https://www.dropbox.com/s/u0axo5le3vodm4c/050522-11687-01.dmp?dl=0
Click to expand...
looked like a stack overflow involving PreSonusHardwa
(name was cut off)

system timer indicated the system was only booted for
1 minute 44 seconds. (is that what you expected, or did the cpu reset)

the bugcheck was called by the cpu because of a unknown internal error. looks like the cpu was restarted with bad power or overheated.

current speed of the cpu was 3564Mhz ( underclocked for 3600Mhz cpu)
overheated cpu can throttle to underclocked speeds.

boils down to: did you think the system was up for longer than 1 min 44 seconds.
if so then they motherboard reset the CPU but the power supply did not delay the restart of the cpu and the cpu got an internal error because of it.
if that is true, the bugcheck would mislead you as to the cause and you would need to look at causes for overheating or why the motherboard reset the cpu. (common with power issues on graphics cards)
 
Upvote 0 Downvote
Yeah, I think it was up longer than 1:44. This is a home build PC, so I poked around in there to look for stuff I might have messed up. The one thing I did find is that the CPU fan was connected to a system fan header instead of the CPU fan header. Any idea whether that could be the source of all this? I fixed it, so a test is underway. Thing is, this problem happens at any old time when the CPU is under no particular load, and it lives in a climate controlled area and has a giant heat sink. But, I'm no expert on the requirements of these things.

Failing that, is there some way I can log the voltage and temp in real time to look for a smoking gun?
 
Upvote 0 Downvote
Mastiff37 said:
Yeah, I think it was up longer than 1:44. This is a home build PC, so I poked around in there to look for stuff I might have messed up. The one thing I did find is that the CPU fan was connected to a system fan header instead of the CPU fan header. Any idea whether that could be the source of all this? I fixed it, so a test is underway. Thing is, this problem happens at any old time when the CPU is under no particular load, and it lives in a climate controlled area and has a giant heat sink. But, I'm no expert on the requirements of these things.

Failing that, is there some way I can log the voltage and temp in real time to look for a smoking gun?
Click to expand...
the cpu has a bunch of sensors they can get warm quickly and cpu fan speed should increase or the CPU clock speed gets reduced if it can not correct the problem.

After this change I would just wait to see if you get this bugcheck again. Good motherboards will reset the cpu when it detects some problems. Poor power supplies have issues where they fake signals to the motherboard and tell the motherboard the power is stable when it is not. This causes the CPU to start before the power is stable. Mostly happens when people are playing a game, the screen goes blank then they see windows a second or two later and do not realize the machine CPU rebooted and they think the game just crashed back to windows. normally the system up timer is under 15 seconds when you see this. yours was longer over a minute. It could be a cpu took that time to overheat and bugcheck to stop the problem. I have not built systems in a few years so maybe someone can recommend good logging tools.
maybe https://www.raymond.cc/blog/monitor-hardware-health-temperatures-voltages-and-fan-speed/

these look like the old tools that were used years ago.
 
Last edited:
  • Like
Reactions: Mastiff37
Upvote 0 Downvote
Well, no BSOD yet, but I'm back to a possibly related problem where the computer won't wake up after leaving it for a while. I thought it was a sleep problem at first, but I disabled sleep and it persists. I still allow the screen to be turned off, and sometimes I come back to find it unresponsive. The monitor light blinks, indicating no signal (I think, it's solid when actually functional). So basically, black screen, computer won't respond and I have to reboot to get back online.

The only complain in the reliability history is that the computer wasn't shut down right (as a result of my reboot), so I don't know how to explain this. Any ideas?
 
Upvote 0 Downvote
Mastiff37 said:
Bleh. Shortly after posting, got another BSOD: https://www.dropbox.com/s/1eby8uyc0myvqwe/050822-12890-01.dmp?dl=0
Click to expand...
bugcheck 0x124
called by cpu
Error : Unknown (Proc 0 Bank 0)
Status : 0x0000000000000000
Severity : Fatal
System Uptime: 0 days 0:25:29.169

stack has repeated 01010101`01010101

I would suspect tevirtualmidi64.sys(Virtual MIDI driver ) but I have no proof.
you would want to run verifier on all of your third party drivers and have the system bugcheck on a bad driver. this problem might not get flagged by verifier.

you could also just use microsoft autoruns and disable that particular driver and see if the problem goes away. https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

you might also change the memory dump to kernel then provide the memory.dmp file it will show what was running on all of the cpu cores and the internal logs. (it will also show the various usb logs)

is this midi device connected via usb?

i would also update your wifi driver:
A7000.sys Mon Dec 25 01:29:04 2017
looks like a netgear
https://kb.netgear.com/000055980/A7000-Software-Version-1-0-0-15-Windows
(looks to be 9 months newer than your version)

windows 11 made some slight changes to how usb works. one of these drivers might not work correctly on windows 11. It should show up in the internal logs. verifier might also bugcheck on the driver if it was updated to catch the problems.
 
Last edited:
Upvote 0 Downvote
Mastiff37 said:
I did a clean install of windows 11 and unfortunately got several crashes during install and after. Here's the most recent. This should at least get rid of confusion caused by various drivers and apps I no longer use: https://www.dropbox.com/s/75j105xfgsmvtz2/050822-6093-01.dmp?dl=0
Click to expand...
bugcheck was called by the cpu unknown error on cpu 0 cache bank 0
no strange drivers installed. system timer was 3 min 5 seconds before cpu error crash.

guess I would be looking at basic voltages and bios settings and confirm the cpu can pass simple tests outside of windows (prime95)
 
Upvote 0 Downvote
Mastiff37 said:
Well, Intel diagnostics all pass. I'm running prime95 now. The crash times seem so random and unrelated to usage...
Click to expand...
Mastiff37 said:
Well, Intel diagnostics all pass. I'm running prime95 now. The crash times seem so random and unrelated to usage...
Click to expand...
I looked at the docs for the status registers from the cpu dump. it had this one bit set: this bit was set:
from intel docs:
• PCC (processor context corrupt) flag, bit 57 — Indicates (when set) that the state of the processor might have been corrupted by the error condition detected and that reliable restarting of the processor may not be possible. When clear, this flag indicates that the error did not affect the processor’s state, and software may be able to restart. When system software supports recovery, consult Section 15.10.4, “Machine-Check Software Handler Guidelines for Error Recovery” for additional rules that apply. •

the internal error that triggered the bugcheck was
00000000 00000101
which turns out to be defined by the processor Docs as
internal parity error

this would lead to suspect, voltage problems, heating problems or clock rate problems.
 
Last edited:
Upvote 0 Downvote
johnbl said:
I looked at the docs for the status registers from the cpu dump. it had this one bit set: this bit was set:
from intel docs:
• PCC (processor context corrupt) flag, bit 57 — Indicates (when set) that the state of the processor might have been corrupted by the error condition detected and that reliable restarting of the processor may not be possible. When clear, this flag indicates that the error did not affect the processor’s state, and software may be able to restart. When system software supports recovery, consult Section 15.10.4, “Machine-Check Software Handler Guidelines for Error Recovery” for additional rules that apply. •

the internal error that triggered the bugcheck was
00000000 00000101
which turns out to be defined by the processor Docs as
internal parity error

this would lead to suspect, voltage problems, heating problems or clock rate problems.
Click to expand...
system up timer not matching the expected values might mean that the motherboard logic detected a problem and reset the cpu.
 
Upvote 0 Downvote
johnbl said:
system up timer not matching the expected values might mean that the motherboard logic detected a problem and reset the cpu.
Click to expand...
a good power supply sends a signal to the motherboard that the power is ok. if the power supply has issues it will reset this signal and the motherboard logic will reset the cpu. poor quality power supplies will fake the signal and set the signal to be ok even when it is not. This can allow the CPU to restart before the power is stable and then the cpu gets parity errors in its cache banks that the cpu memory controller detects and causes a bugcheck like the one your cpu is getting. This would be 2 problems: cheap power supply that does not set power_ok signal and some power condition that the motherboard is detecting and resetting the cpu.
often in this case people replace the power supply with a known good and still have issues but get a black screen and the cpu reboots without getting a bugcheck.
the screen goes black until the power supply tells the motherboard the power is ok, then the system starts to boot. Old system would be counting memory but with fast startup it boots very quickly
 
Upvote 0 Downvote
johnbl said:
a good power supply sends a signal to the motherboard that the power is ok. if the power supply has issues it will reset this signal and the motherboard logic will reset the cpu. poor quality power supplies will fake the signal and set the signal to be ok even when it is not. This can allow the CPU to restart before the power is stable and then the cpu gets parity errors in its cache banks that the cpu memory controller detects and causes a bugcheck like the one your cpu is getting. This would be 2 problems: cheap power supply that does not set power_ok signal and some power condition that the motherboard is detecting and resetting the cpu.
often in this case people replace the power supply with a known good and still have issues but get a black screen and the cpu reboots without getting a bugcheck.
the screen goes black until the power supply tells the motherboard the power is ok, then the system starts to boot. Old system would be counting memory but with fast startup it boots very quickly
Click to expand...

Thanks for that. Is there any way I can have certainty before I start throwing more money at this thing? I'm pretty sure it's not overheating at this point, so I'm thinking either power supply issues, faulty CPU, faulty motherboard. I suppose it could be memory, but the tests pass.
 
Upvote 0 Downvote
Mastiff37 said:
Thanks for that. Is there any way I can have certainty before I start throwing more money at this thing? I'm pretty sure it's not overheating at this point, so I'm thinking either power supply issues, faulty CPU, faulty motherboard. I suppose it could be memory, but the tests pass.
Click to expand...
parity error was inside the cpu, so it will not be your external ram.
First fix attempt is to update the bios or set it to defaults. check the voltages that the bios sees and make sure they are within range.

after that I would remove or disable bios functions. IE turn off any cpu function that could change the cpu core speed. turn off functions you are not using.
check the connections from the power supply to the motherboard and any graphics card. sometimes connectors can have a pin pushed out of the plastic sockit.

remove or disable hardware that is connected to the system. with newer systems even USB devices can mess up the system bus now that the connections are going thru the bus rather than a external USB chip.

I would also change the memory dump type to kernel, it will dump more info into the file memory.dmp and it will contain the internal logs, and show what is going on with all the cpu and the plug and play system. not sure it will be useful since I think the machine is rebooting because the motherboard sees a problem and resets the cpu.
if you have been overclocking or overheating sometimes people take the cpu off and see charred cpu pads that you might be able to clean/polish. some people have found problems with bent motherboard pins under the cpu. you can take a photo and look up the actual pin and see what it does.
problem is many functions are based on voltage on a pin then the voltage is converted to a frequency. The frequency is used to set the speed of the bus transfers between the levels of the cache memory in the cpu. if the pin gets charred, the voltage drops and the cpu converts it to the wrong frequency and your cpu corrupts the data as it goes thru the cache memory levels inside of the cpu. Bios also uses tables to set these values that is why want to update the bios and lock the frequency of the CPU if you are having problems.
you can take a look at the various tools: https://www.itechtics.com/check-hardware-details-windows/
or maybe someone can suggest a good tool to monitor your power settings to look for fluctuations

note: you should also make sure your main power connection is not going thru a power strip. There have been cases where that has been the cause. One time a person would get this bugcheck when the motor to his refrigeration turned on. just had to put it on a different circuit. Those are the only ones I recall that were external to the machine.
 
Last edited:
Upvote 0 Downvote
Thanks for the help. I think I did change the dump to kernel prior to the last error. Do the files go someplace different, or still .dmp in the minidump folder?

Poking around in the BIOS I noticed I was in csm mode instead of uefi. I thought win11 required UEFI. Should this have any effect on my issues?
 
Upvote 0 Downvote
Mastiff37 said:
Here's the memory dump: https://www.dropbox.com/s/t6zofteqpire6iy/MEMORY.DMP?dl=0
Click to expand...
plug and play is complaining about not having a driver for
pci vendor 8086 = intel
device = 1911
this device is listed as (it might be incorrectly listed)
Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussiuon
it does not seem to match your cpu model i7 9700k

you should run the intel chipset update and see if it gets installed in device manager.
it is listed as connected to pci bus 2. It could be messing up

It is the Intel Neural Network Accelerator or GNA for short. This is an AI co-processor inside the CPU die. This is a technology used to process speech recognition without user training sequence.

see if you can get this working on your window control panel device manager


i will check some other logs.

system was up for 23 minutes.,
your usb 3.0 hub is asleep
all of the usb devices are waiting for a wake signal including the usb 3 hub. I would go into windows control panel device manager and right mouse click on the usb hub and tell windows not to put it to sleep. same with the HID devices. (or tell windows to run in high performance mode until you figure out this problem)

looks like you have usb hubs that are trying to tell you usb 3 hub to wake up and it is not so the hub is telling the parent hub to reset.
(i would run in high performance mode until you find the problem)

problem: debugger indicates that two system files have been modified
pci.sys 78 modifications
usbxhci.sys 10 modifications

not good since we are looking at problems with the pci bus
and usb the modified file provides intel usb extensions

your system seems to be running a key and mouse logger tool
(unexpected) maybe it is part of your web building tools
qtwebengineprocess.exe

i would kill filecoauth.exe
does it inject keystrokes, what happens if the usb port is asleep when the software injects keystrokes? overflow a buffer connected to the usb which is connected to the PCI bus?

(or make sure the ports never go to sleep)

need to determine if you want this running or if it is malware
 
Last edited:
Upvote 0 Downvote
johnbl said:
plug and play is complaining about not having a driver for
pci vendor 8086 = intel
device = 1911
this device is listed as (it might be incorrectly listed)
Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussiuon
it does not seem to match your cpu model i7 9700k

you should run the intel chipset update and see if it gets installed in device manager.
it is listed as connected to pci bus 2. It could be messing up

It is the Intel Neural Network Accelerator or GNA for short. This is an AI co-processor inside the CPU die. This is a technology used to process speech recognition without user training sequence.

see if you can get this working on your window control panel device manager


i will check some other logs.

system was up for 23 minutes.,
your usb 3.0 hub is asleep
all of the usb devices are waiting for a wake signal including the usb 3 hub. I would go into windows control panel device manager and right mouse click on the usb hub and tell windows not to put it to sleep. same with the HID devices. (or tell windows to run in high performance mode until you figure out this problem)

looks like you have usb hubs that are trying to tell you usb 3 hub to wake up and it is not so the hub is telling the parent hub to reset.
(i would run in high performance mode until you find the problem)

problem: debugger indicates that two system files have been modified
pci.sys 78 modifications
usbxhci.sys 10 modifications

not good since we are looking at problems with the pci bus
and usb the modified file provides intel usb extensions

your system seems to be running a key and mouse logger tool
(unexpected) maybe it is part of your web building tools
qtwebengineprocess.exe

i would kill filecoauth.exe
does it inject keystrokes, what happens if the usb port is asleep when the software injects keystrokes? overflow a buffer connected to the usb which is connected to the PCI bus?

(or make sure the ports never go to sleep)

need to determine if you want this running or if it is malware
Click to expand...

Thanks. I ran some Intel tools and they found no drivers to update, but windows update did have two Intel drivers (one of them the Gaussian mixture thing) and those are installed. I don't see anything in device manager related to this though?

I turned off sleep mode for the USB hubs. Is high performance mode in addition to that?

I have nothing installed other than what comes in Win11 except various debug utilities, I may have gotten malware though. I'll do a scan for that.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom