Unsolved

3276

March 3rd, 2022 13:00

System Thread Exception Not Handled

I am now grasping at straws for a fix on this issue...

I have a Dell Precision 3430 SFF, Core i7-8700 that suddenly threw a BSOD error one day while I was using it.  I don't even remember the original BSOD error, it has had a few different ones but now has settled on System Thread Exception Not Handled.

My problem is simply this... I am trying to install Windows on a new, blank SSD, via bootable flash drive created from Windows 10 Media creation tool.  This bootable media has been used to image numerous other machines so I know it works.  When I hit F12 and set the computer to boot from the flash drive, it starts out normally, showing me the Windows splash icon, the little dots go round and round a couple time and then fails to a BSOD, with the System Thread Exception error. 

Googling the issue always comes up with 'bad video drivers' but Windows doesn't exist on the machine yet, therefore no video drivers.  I have used the onboard graphics as well as an add-in card I happened to have, same error.  

I can play around in BIOS and run the diagnostics as long as I like and the machine behaves normally, but when trying to reinstall windows I get the BSOD.

I have replaced the SSD, the RAM, and finally the MOBO.  I have successfully updated the BIOS manually from a USB flash drive, made certain that the date/time and other BIOS settings were correct.  I tried booting from an external DVD drive, even gone so far as to pull a cd drive from an old Optiplex and popped it into the Precision 3430 (which had none by default) and the same thing occurs.  One person advised that the bootable media should be a USB 2.0 drive, less than 32GB, and should be plugged into a USB 2.0 port on the computer.  I followed that advice and still the same error.  Finally, I ran extensive diagnostics on the machine using the Dell Diagnostics pre-boot system and all systems passed 100%, no errors.  I even did the extended mem test and hd test, both passed.

ANY advice on this would be greatly appreciated.  Next step is parting it out if I cant figure out why this is happening.

 

6 Professor

 • 

1.5K Posts

March 4th, 2022 09:00

It could be a ram module starting to get bad. Make a bootable usb with memtest and do "a bit" of cycles to test 

Alternative would be to remove the ram, install just one in slot 1, and see if it installs. If yes, you could redo the test with the other modules until finding the one causing the bsod

March 4th, 2022 13:00

Thanks for the suggestion Mazzinia, I did just that and the memory is fine.  I have actually tried 3 different sticks of RAM and the issue persists.  

It does seem like it would be a RAM issue but I've used sticks from a known working machine as well as two brand-new modules I got from NewEgg and the MOBO is brand new, literally had to take it out of Manufacturer mode.  Its all just so baffling...

6 Professor

 • 

1.5K Posts

March 5th, 2022 07:00

Do you have any spare videocard, to try swapping just in case ?

And it could be a defected mb, with issues with one ram slot .... or it could have one (or more) pin of the cpu socket slightly bent

March 5th, 2022 10:00

At this point the only thing that hasnt been replaced in this system is the CPU so by order of elimination, it must be an issue with the CPU... which would explain getting this error with the original build and carrying over even on a new MOBO, new RAM and new SSD.  I don't have any extra CPUs laying around so this computer is going to be parted out, I'm not going to spend any more time on it.  

 

Thanks for all your suggestions, I guess I needed to hear someone else say it could be a CPU issue, I couldnt bring myself to admit it, haha!

0 events found

No Events found!

Top