Multiple BSOD errors, Unknown Cause

[jeffpkamp]

The slot I was using became unresponsive, ie it wouldn't even boot to bios until I changed the slot the ram was in. I tested a stick of ram that was suspect all night last night. 9 passes on memtest without an error, so I think that the slot and the stick are not the issue.

I am posting the most recent minidmps.

I guessing this is either a mother board problem, hard drive problem (I don't really think that one), or an OS problem.

Does it sound reasonable to run the computer in ubuntu for the day and see if it crashes there for a test of the OS hyopthesis?

 

[jeffpkamp]

newest crash dump

 

[jeffpkamp]

also it seems to have frozen in ubuntu, so I'm thinking it's not a windows software issue

 

[YoYo155]

also it seems to have frozen in ubuntu, so I'm thinking it's not a windows software issue

Please Download - Speccy - System Information - Free Download

And post a screenshot.

 

[jeffpkamp]

so I have no idea if this is the problem, but my CPU and MOBO temps are super high, like high 70's C.

Heres the screen shot from speccy, let me know if you want something else.

 

[YoYo155]

Those are very high!

Make sure you can hear or see the fan working, if it is continue with these steps.

-If your PC is under warranty the steps specified below may VOID it!-

• Shut-Down the PC
• Unplug from the power brick.
• Remove the battery.
• Let the PC cool down for as long as needed until its only warm to the touch or not at all.
• Buy a can of compressed air.
• If you have a cover on the bottom that can be unscrewed, remove it for grater access.
• When using the compressed air, use short bursts and DO NOT! use it upside-down!!
• First blow into the intake (the grill with the fan) again short bursts.
• Next do the same to the exhaust.
• If you have access the opposite side of the fan blow through there as well.
• Next grab a flashlight and point it inward from the exhaust and look for anything that may be blocking the light from passing through when looking from the intake side (the fan).

Keep posting details!

 

[jeffpkamp]

Fans are working, after looking around the web, these temperatures are the norm for this laptop. Terrifying if you ask me.

It ran all night without a single crash, and I was doing my best to stress it along with DV.

You didn't change any settings other than turning on driver verify right?

I'll keep you posted if it crashes again.

 

[YoYo155]

A good dust-off is always welcomed, but that is up to you.

I did change some settings in the Power-savings Options.
No crashes so far?

 

[jeffpkamp]

Solid as a rock this morning. I did remove some malware yesterday before you worked on it, but I am pretty sure it crashed at least twice after that.

What power settings did you change?

I will give it a week or more before I feel confident it's fixed, but its made it the longest without a crash in at least a week...

thanks for your help so far.

 

[jeffpkamp]

crashed right out of the gate with the original power settings. I'll let it run all day and report back if it crashes with the modified power settings.

 

[jeffpkamp]

Stable for the last five hours since I changed the power settings to the ones you set.

What did you change in the power settings???

Here is the minidump from the crash I had after we turned of DV and changed the power settings back....

 

[YoYo155]

I changed the CPU minimum to 50% from the default 5%.
I had a hunch about the fact that your PC was stable with DV enabled, meaning it was working harder than normal.
So by changing the Power-Saving I'm preventing the CPU clock from dropping to low.

 

[jeffpkamp]

ran through the night fine, however when I went to wake it up this morning from sleep, it crashed. I"m attaching the crash dump. If you are right that it is somehow a low power to the processor problem, it could be the transistion from sleep to active that did this. Here is the dump file.

 

[YoYo155]

Download and install | Aida64 - Trail

Launch the tool.

Go to: Tools> System Stability Test (don't run the test).

Take a screenshot of the Statistics Tab with different configurations:

• Working off of the battery alone. (Name the file Config A)

(Screenshot after 15min) - Before each new configuration Click the "Clear" button at the bottom of the Statistics tab.

• working with the battery and plugged into the power-brick. (Name the file Config B)

(Screenshot after 15min)

• Shutdown the PC completely! and unplug the power-brick, before you continue!
  

• Without the battery inserted into the PC, plugged into the power-brick. (Name the file Config C)

(Screenshot after 15min)


​

​

 

[jeffpkamp]

I updated that value added driver, and I"m worried that may be the source of the crashes, I did a system restore, but I don't know where to check the date on the driver. I'm going to see if it crashes now that I did the system restore.

Also the program you told me to download doesn't show all those details on the trial version, all I am getting is CPU temps.

 

[jeffpkamp]

The errors I am getting are different from before. Apparently I switched the dumps to kernal dumps at some point, so I missed them. I however just got the last one as a mini dump and the last kernal dump I was able to compress to a reasonable size. Here they both are.

 

[YoYo155]

The last dumps are corrupt.
The Kernel Dump option is the default in Windows 7, minidumps are still getting created in C:\Windows\minidump folder.

It's due to it being a laptop.
I find Aida64 more reliable that is why I opted to use it, but it doesn't answer our needs this time.

Follow what I asked above but only with CPUID - HWMonitor

 

[jeffpkamp]

okay, so now the computer is totally screwed I think. It has started failing at windows start.

I tried running system restore, but it crashes at the start of system restore.

I tried running system restore from the install disk, and it gave me the system_management_error BSOD there also.

Not sure if there is anything I can do now...

 

[YoYo155]

Can you recall the changes you made prior to this situation?

 

[jeffpkamp]

I was going to see if DV would stabilize it again, so I turned it on..., but that shouldn't be running when I put in the install disk.