BSOD: System Thread Exception Not Handled and Driver IRQL Not Less Or Equal

[canderot]

Hi everyone,

I have a Toshiba Satellite E45-B4100. I recurrently get a BSOD with those two errors mentioned in the title. I changed its original HDD for a Samsung 850 EVO 250GB SSD almost inmediately after I got the laptop. I have not updated to windows 10 yet so I have windows 8.1 Update 1.

I usually get a System Thread Exception Not Handled error, except for today, when I got a Driver IRQL Not Less or Equal. Unfortunately, I live in Argentina but bought the machine in the US, so I can't have it replaced.

I've attached the minidump files here. Does anyone know what I could do to fix this?

Thanks in advance,
Cami

 

[johnbl]

looks like there is a problem with your wireless ethernet drivers their code is being corrupted. Change the memory dump from minidump to kernel dump:https://www.sophos.com/en-us/support/knowledgebase/111474.aspx

run cmd.exe as an admin, then run
sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth
then run
verifier.exe /standard /all
and reboot your machine. this will force windows to check drivers that are writing outside of their own memory areas and it will force a bugcheck and name the bad driver in the memory .dmp.
note: when done testing turn of verifier functions by running
verifier.exe /reset
or your machine will run slower until you do.

then put the file c:\windows\memory.dmp on a server and post a link.
it will be larger and will contain extra tracking info to figure out what caused the problem.
--------
third bugcheck was also in networking code that supports the wireless driver.
also a stack overrun.

--------
second bugcheck was also in networking code but was in
\SystemRoot\system32\DRIVERS\Netwbw02.sys Mon Mar 23 01:53:41 2015
this is the driver for Intel® Wireless WiFi Link Driver - Intel® Wireless WiFi Link Adapter.
I would look for a update from intel or from your motherboard vendor.

network stack was again corrupted. I can not tell why from a minidump, would need a kernel memory dump.

-------
bugcheck in networking code (bad memory address passed to driver)
first guess would be your ethernet driver but I can not tell which one with a mini dump.
(need a kernel memory dump to dump the info) will look at the other bugcheck to see if one is more clear as to the cause.

you might want to go to the vendor website and look for driver updates for the various toshibia drivers like:
\SystemRoot\System32\drivers\TVALZ_O.SYS Wed Jul 25 16:23:25 2012



machine info:
BIOS Version 1.10
BIOS Release Date 01/12/2015

Manufacturer TOSHIBA
Product Name Satellite E45-B
Version PSPNAU-001002
Product CA10CU
Version 2.0
Chassis Type Notebook
Processor Version Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz
Processor Voltage 89h - 0.9V
External Clock 100MHz
Max Speed 2700MHz
Current Speed 2500MHz

4GB bank samsung memory Part Number M471B5173QH0-YK0
2GB bank Hynix/Hyundai memory Part Number HMT425S6AFR6A-PB

 

[canderot]

Thank you john!

I did as you said; sfc found corrupted files, then dism said it fixed component store corruption. I uploaded the CBS.log and the memory.dmp here. Kernel dump is also set. I haven't yet gotten another blue screen but then again they happen only about twice a month.

looks like there is a problem with your wireless ethernet drivers their code is being corrupted. Change the memory dump from minidump to kernel dump:https://www.sophos.com/en-us/support/knowledgebase/111474.aspx

run cmd.exe as an admin, then run
sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth
then run
verifier.exe /standard /all
and reboot your machine. this will force windows to check drivers that are writing outside of their own memory areas and it will force a bugcheck and name the bad driver in the memory .dmp.
note: when done testing turn of verifier functions by running
verifier.exe /reset
or your machine will run slower until you do.

then put the file c:\windows\memory.dmp on a server and post a link.
it will be larger and will contain extra tracking info to figure out what caused the problem.
--------
third bugcheck was also in networking code that supports the wireless driver.
also a stack overrun.

--------
second bugcheck was also in networking code but was in
\SystemRoot\system32\DRIVERS\Netwbw02.sys Mon Mar 23 01:53:41 2015
this is the driver for Intel® Wireless WiFi Link Driver - Intel® Wireless WiFi Link Adapter.
I would look for a update from intel or from your motherboard vendor.

network stack was again corrupted. I can not tell why from a minidump, would need a kernel memory dump.

-------
bugcheck in networking code (bad memory address passed to driver)
first guess would be your ethernet driver but I can not tell which one with a mini dump.
(need a kernel memory dump to dump the info) will look at the other bugcheck to see if one is more clear as to the cause.

you might want to go to the vendor website and look for driver updates for the various toshibia drivers like:
\SystemRoot\System32\drivers\TVALZ_O.SYS Wed Jul 25 16:23:25 2012



machine info:
BIOS Version 1.10
BIOS Release Date 01/12/2015

Manufacturer TOSHIBA
Product Name Satellite E45-B
Version PSPNAU-001002
Product CA10CU
Version 2.0
Chassis Type Notebook
Processor Version Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz
Processor Voltage 89h - 0.9V
External Clock 100MHz
Max Speed 2700MHz
Current Speed 2500MHz

4GB bank samsung memory Part Number M471B5173QH0-YK0
2GB bank Hynix/Hyundai memory Part Number HMT425S6AFR6A-PB