Solved system_exception_thread_not_handled

tymasincere

New Member
Messages
3
Location
Suffolk UK
Hi all,
I'm getting the above error and consequent BSOD but ONLY at initial start up if the pc has been powered down for some time i.e overnight.
I don't get it at any other time, the pc restarts fine after the initial crash, and it never does it whilst using the pc.
The only other error shown is ksthunk.sys which I believe is driver related?
All drivers are up to date, no yellow triangles in device manager, I've unplugged all peripherals to no effect, and the BIOS is the latest version. Really driving me mad now, just wondered if anyone had a similar experience?
PC specs as below:
Windows 8.1 64 bit pro.
Asus 990FX MB
AMD 4150FX CPU
Radeon HD7950 GPU
16gb Samsung RAM
850w PSU

Many thanks for any help.
 

My Computer

System One

  • OS
    Windows 8.1 64 bit pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Asus MB / Custom build
    CPU
    AMD FX 4100 3.6ghz
    Motherboard
    Asus 990fx
    Memory
    Samsung Green
    Graphics Card(s)
    Radeon HD7950
    Sound Card
    Creative Soundblaster R3conD PCIe
    Monitor(s) Displays
    Hanns 28" LCD
    Screen Resolution
    1920x1200
    Hard Drives
    OCZ Agility 128GB SSD
    Samsung 128GB SSD
    Western Digital 1TB HDD
    PSU
    Be Quiet 850W
    Case
    Coolermaster HSB
    Cooling
    H100 Liquid Cooling
    Keyboard
    Steelseries Shift
    Mouse
    Gamdias Hades Optical
    Internet Speed
    >8mb
    Browser
    Google Chrome
    Antivirus
    Windows Defender
Hi

The issue you described is generally an indication of a failing RAM module. Yes, some modules works fine when they are warm but may fail when they are cold. Your first steps should be nothing but an isolation test of RAM modules.That is remove all but one module and check how the system works. Repeat this with all modules but make sure the test to be run only when the system is off for few hours and cold.
 

My Computer

System One

  • OS
    Windows 7
Hi

The issue you described is generally an indication of a failing RAM module. Yes, some modules works fine when they are warm but may fail when they are cold. Your first steps should be nothing but an isolation test of RAM modules.That is remove all but one module and check how the system works. Repeat this with all modules but make sure the test to be run only when the system is off for few hours and cold.

Many thanks for your answer, I'll eliminate or prove RAM issues over the next few days. Would running Memtest or similar help?
 

My Computer

System One

  • OS
    Windows 8.1 64 bit pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Asus MB / Custom build
    CPU
    AMD FX 4100 3.6ghz
    Motherboard
    Asus 990fx
    Memory
    Samsung Green
    Graphics Card(s)
    Radeon HD7950
    Sound Card
    Creative Soundblaster R3conD PCIe
    Monitor(s) Displays
    Hanns 28" LCD
    Screen Resolution
    1920x1200
    Hard Drives
    OCZ Agility 128GB SSD
    Samsung 128GB SSD
    Western Digital 1TB HDD
    PSU
    Be Quiet 850W
    Case
    Coolermaster HSB
    Cooling
    H100 Liquid Cooling
    Keyboard
    Steelseries Shift
    Mouse
    Gamdias Hades Optical
    Internet Speed
    >8mb
    Browser
    Google Chrome
    Antivirus
    Windows Defender
I have similar issue and I see same problem reported by quite some people. I don't think its RAM issue for its affecting so many people.
I sometimes get system_exception_thread_not_handled and sometimes bad_pool_caller.
I boot once with safe-boot and restart and boot normally it works.
Desperately waiting for solution...
 

My Computer

System One

  • OS
    Win 8.1 64 bit
    Computer type
    Laptop
    System Manufacturer/Model
    Lenovo L530
    CPU
    i5 3230M @ 2.6 GHz
    Memory
    4GB
Would running Memtest or similar help?

Usually memtest won't catch this type of errors. Physically isolating modules is the best way to test.

I don't think its RAM issue for its affecting so many people.

Failing RAM is the most common reason for blue screens. Your issue may or may not be caused by that but unless you are going to test each module separately, you won't know it.
 

My Computer

System One

  • OS
    Windows 7
Would running Memtest or similar help?

Usually memtest won't catch this type of errors. Physically isolating modules is the best way to test.

I don't think its RAM issue for its affecting so many people.

Failing RAM is the most common reason for blue screens. Your issue may or may not be caused by that but unless you are going to test each module separately, you won't know it.
You are correct on both counts - it was indeed a bad RAM module causing the problem. I removed a pair of RAM sticks and problem solved - not sure which of the 2 it is but I'm due to upgrade the RAM soon so can live without both for now, still have 8gb in there.
Many thanks for your quick reply and correct diagnosis, saved me loads of time :thumb:
All the best
John
 

My Computer

System One

  • OS
    Windows 8.1 64 bit pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Asus MB / Custom build
    CPU
    AMD FX 4100 3.6ghz
    Motherboard
    Asus 990fx
    Memory
    Samsung Green
    Graphics Card(s)
    Radeon HD7950
    Sound Card
    Creative Soundblaster R3conD PCIe
    Monitor(s) Displays
    Hanns 28" LCD
    Screen Resolution
    1920x1200
    Hard Drives
    OCZ Agility 128GB SSD
    Samsung 128GB SSD
    Western Digital 1TB HDD
    PSU
    Be Quiet 850W
    Case
    Coolermaster HSB
    Cooling
    H100 Liquid Cooling
    Keyboard
    Steelseries Shift
    Mouse
    Gamdias Hades Optical
    Internet Speed
    >8mb
    Browser
    Google Chrome
    Antivirus
    Windows Defender
Back
Top