Windows 7 Unexpexted BSOD results in Crash Dump

A

AuXBoX

New Member
Joined
Aug 20, 2011
Messages
14
Hi everyone,

I have been getting a BSOD after i have built my new computer. I have just enable a minidump and it happened this morning. I am uploading it by any chance someone could help with debugging it.

I'm not too sure why it happens.
hope someone could help

Link Removed
 
Solution
AuXBoX said:
More often than not the computer just reboots without BSOD and sometimes the bios changes the hard drive it boots from and i have to change it.
Click to expand...
This would seem to indicate there was a hard drive problem. I know if you remove the primary hard drive, a secondary one will move into the primary position in the bios. Possibly also if the system can only partially read the primary drive, it might try to go to a secondary.

I suppose there is a possibly it could be the controller instead of the actual drive, but considering it is an SSD, I think I would try running the system with a standard drive for a while to test. Maybe there is some type of conflict with the SATA drivers and the SSD.

Edit: I was wondering if turning off...
Sort by date Sort by votes
The stop error is 0x124 which is a hardware error, can you get cpu-z and post pics of each tab and each populated memory slot. Can you also monitor your temps and post min and max values. I shall then see what can be done.
 
Upvote 0 Downvote
Here are the tabs from cpu-z nmsuk

Link RemovedLink RemovedLink RemovedLink RemovedLink RemovedLink Removed

Heres the temps
Link Removed

The only card i have plugged in is the tp-link wn951n, which i'm thinking could be the problem.
 
Last edited:
Upvote 0 Downvote
Just happened again here is the minidump.

Link Removed

and heres the debuglog.txt

Link Removed

I used a different temp program the other one said all cores went to 99C under heavy load when this one siad this
Link Removed
 
Last edited:
Upvote 0 Downvote


Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try - Windows 7 Forums
 
Last edited by a moderator:
Upvote 0 Downvote
Have you ever gotten any type of overheat warning? Have you checked the temp settings in the bios against what you seem to be showing?
 
Upvote 0 Downvote
Saltgrass said:
Have you ever gotten any type of overheat warning? Have you checked the temp settings in the bios against what you seem to be showing?
Click to expand...

No I havent had any overheating warnings. The temps seem all fine on bios aswell.

This is very annoying.
 
Upvote 0 Downvote
It's been two weeks, Are you still BSODing? If so update your latest dmp files. The more info, the better/quicker!
 
Upvote 0 Downvote
Elmer said:
It's been two weeks, Are you still BSODing? If so update your latest dmp files. The more info, the better/quicker!
Click to expand...

More often than not the computer just reboots without BSOD and sometimes the bios changes the hard drive it boots from and i have to change it.

Heres the latest DMP file
Link Removed
 
Upvote 0 Downvote
Replaced the wifi card and it still does it.
No BSOD though, just resets and reboots with the bios trying to boot a different hard drive.
Could this be a hard drive problem?
My operating system is on a brand new SSD.
 
Upvote 0 Downvote
AuXBoX said:
More often than not the computer just reboots without BSOD and sometimes the bios changes the hard drive it boots from and i have to change it.
Click to expand...
This would seem to indicate there was a hard drive problem. I know if you remove the primary hard drive, a secondary one will move into the primary position in the bios. Possibly also if the system can only partially read the primary drive, it might try to go to a secondary.

I suppose there is a possibly it could be the controller instead of the actual drive, but considering it is an SSD, I think I would try running the system with a standard drive for a while to test. Maybe there is some type of conflict with the SATA drivers and the SSD.

Edit: I was wondering if turning off S.M.A.R.T. monitoring for the drive might help?
 
Last edited:
Upvote 0 Downvote
Solution
You must log in or register to reply here.

Similar threads

  • Featured
  • Article Article
Revolutionizing Windows Crash Dump Analysis with AI and mcp-windbg
Replies
0
Views
640
ChatGPT
  • Solved
Windows 10 Unexpected BSOD resulted in crash dumps
Replies
4
Views
2K
kemical
M
  • Solved
Windows 7 Unexpected BSOD results and crash dumps
Replies
5
Views
3K
kemical
K
  • Solved
Windows 7 Unexpected BSOD results in minidump
Replies
1
Views
805
kemical
U
  • Solved
Windows 7 Unexpected BOSD results in a Crash dump
Replies
4
Views
3K
kemical