BSOD with blame on ntoskrnl.exe and ntkrnlmp.exe

Ray2003 · 20 Feb 2015

Hi everyone. My computer BSOD'd again with only the ethernet cable connected. It actually froze while it was supposedly collecting the crash reports. I noticed there was no minidump file in the minidump folder but WhoCrashed (I know, I know, Arc, you hate the program but I ran it before I checked the minidump folder) showed the following, which is strange because where did it get this info from. With the zip file, I also included a camera of the frozen BSOD screen (which never stopped/started collecting the crash info).

On Fri 2/20/2015 1:43:39 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!IoFreeWorkItem+0x8AC)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8000363BFED, 0xFFFFF880009A99D8, 0xFFFFF880009A9230)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

gregrocker · 20 Feb 2015

Did you remove the wireless card?

Ray2003 · 20 Feb 2015

Yes, the wireless card is NOT in the computer.

Arc · 21 Feb 2015

Hi Ray. I dont hate WhoCrashed.

I just think that is is not efficient in reading a crash dump.

As per the camera snap, the crash dump is not recorded. So there is no new crash dump in the folder.

No network related issue is there after 17th.

Anyway, there are two things common between a stop 0x1E and stop 0x7E, a BIOS bug and a remote control program.

If you have any sort of remote control program installed, uninstall it as a test.

Also, check with gateway that if there is any BIOS update available for your model. http://panam.gateway.com/product/def...x?modelId=2294 .... apparently it seems to me that there is a scope for it. Your BIOS is ....

Code:

BiosVersion = P01-A3        
BiosReleaseDate = 05/17/2010

There is an update available ....

Attachment 350366

Please be aware that the BIOS updates are risky. If you dont have any previous experience with it, dont do it yourself. Take assistance of anybody who knows about it, or even you may call a technician to do it for you.

As it is an old branded desktop, two more questions will be there .....

► Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator - The most trusted PSU Wattage Calculator
Also let us know the wattage of your PSU.

► Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Let us know the results.

Ray2003 · 22 Feb 2015

Thanks. I'll do these steps and get back to you within a few days!

Arc · 23 Feb 2015

OK, no problem. :) You are welcome.

Ray2003 · 11 Mar 2015

Thanks for the update and major apologies for taking so long to implement them. I've been busy and lazy. Anyways . . .

I've downloaded both the screenshot Bios updates but could only update one of them (the first one dated 10/04/2010). The other one, when I hit "flash" on the updater, says, "Error: Can't analyze the IIM Information." Should I figure out a way to install this second part of the BIOS update (dated 08/03/15)?

As far as I know, I have no remote control program.

I went on the eXtreme Power Supply Calculator, and I put in the info as best I could, and the site told me 290W for recommended PSU Wattage.

Here is the Speccy snapshot URL:

http://speccy.piriform.com/results/E...oBX6BqHdP21BRV

I've had one BSOD since the last message, and it didn't record it as a minidump.

Please advise. Thank you so much!

Arc · 12 Mar 2015

You updated the BIOS with the right one.

Now it is an waiting game. Wait and see how it goes. Report us for any necessity about the issue.