• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 247
  • Last Modified:

Can someone analyze my mini-dump?

I was getting some Blue Screen crashes and suspected my SSD.  The manufacturer recommended I upgrade the firmware, which will erase the drive.  I did so and re-installed Win 7 and I got another Blue Screen.  Can someone who knows about this analyze my mini-dump?  The BugCheckCode was 124.
0
hrolsons
Asked:
hrolsons
  • 14
  • 9
  • 4
  • +1
1 Solution
 
Rob MinersCommented:
Press the WinKey + Pause

Click Advanced System Settings, Advanced and under Startup and Recovery select Settings.

Uncheck Automatically restart.

Click on the dropdown arrow under Write debugging information.

Select Small memory dump (64 KB) and the output is %SystemRoot%\Minidump.

Restart the PC normally as this will allow the System to Blue Screen and create the Minidump.

Minidump Files can be found here. C:\WINDOWS\Minidump\Mini122707-02.dmp

Post the mindump file for analysis.
0
 
nobusCommented:
yes plse, post the dmp file here - just attach as file
0
 
hrolsonsAuthor Commented:
Of course, now I can't get it to crash.

I'll attach the original dmp.

031512-14133-01.dmp
0
Reclaim your office - Try the MB 660 headset now!

High level of background noise often makes it difficult for employees to concentrate fully on their jobs – or to communicate clearly on calls. The MB 660 headset helps you create a disruption free workspace.  

 
cantorisCommented:
That BSoD is a "Windows Hardware Error Architecture Uncorrectable Error".

I'd go for SSD Firmware, Motherboard BIOS and driver updates and then get Windows patched up and keep your fingers crossed and your data backed up!

I can't get anything out of that dump file though.  Personally I always enable Kernel Memory Dump writing to capture a bit more info.
0
 
Rob MinersCommented:
The dump file is corrupt. Can you post a more recent dump file?
0
 
hrolsonsAuthor Commented:
I'm trying to get it to crash now.  :)
0
 
nobusCommented:
did you install all the drivers for the mobo?
many of these errors seem to point to the wireless card  -you have one?
0
 
hrolsonsAuthor Commented:
I installed the drivers for the MB from the disk that came with the MB.  I do have a wireless USB for the network connection.  Can you tell me what error points to this?
0
 
hrolsonsAuthor Commented:
It just crashed.  Here is the log:
031712-14960-01.dmp
0
 
cantorisCommented:
The dump really doesn't tell us much more than the BSoD code did.
There's a good article here on the sorts of hardware issues to think about (eg dodgy RAM, overheating, overclocking).  So start by removing any overclocked settings and test your RAM - eg with MemTest86+.

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Good luck.
0
 
nobusCommented:
this error  :  The BugCheckCode was 124.
0
 
hrolsonsAuthor Commented:
I removed the wireless network usb and used a network cable instead and had another crash just now.  I'm starting to think the crashes are happening on shut down so I'm going to try to make it crash.
0
 
hrolsonsAuthor Commented:
We might be getting somewhere.  I've run Prime95, Memtest, Memtest86+ and none found any memory issues.

However, I just ran the included Windows Memory Diagnostics and it crashed 2 times in a row.   I'm going to run it with only 1 memory stick at a time and see if I can pin down the culprit.
0
 
hrolsonsAuthor Commented:
Darn, testing 1 at a time didn't produce any crashes.
0
 
cantorisCommented:
Run MemTest86+ for an extended period of time.

Is anything on your system overclocked?
0
 
hrolsonsAuthor Commented:
No, nothing is overclocked.  I will run MemTest86+ for a few days.
0
 
cantorisCommented:
Overnight would be fine  :)
0
 
hrolsonsAuthor Commented:
I've run it overnight with no problems detected.
0
 
nobusCommented:
>>  testing 1 at a time didn't produce any crashes.  <<  it may have been bad contacts; sometimes the sticks "creep" out a bit, and removing and reinstalling them fixes it
0
 
hrolsonsAuthor Commented:
Ran MemTest86+ for 5 days with no errors.
0
 
nobusCommented:
time to do the real test again
how often does it crash?
also - look  on the net for compatibility problems of that model SSD and the mobo
0
 
hrolsonsAuthor Commented:
Now I can't get it to crash!
0
 
nobusCommented:
keep it that way - maybe it repaired itself (with an update, or reboot)
0
 
hrolsonsAuthor Commented:
No crash, but CHKDSK is finding more bad sectors.  RMA is next step.
0
 
nobusCommented:
try hddRegenerator - it fixed may drives for me : http://www.dposoft.net/hdd.html
0
 
hrolsonsAuthor Commented:
I'm not sure what to accept as the solution.  All comments were helpful, but it just turned out to be a bad hard drive.
0
 
nobusCommented:
so the SSD has bad sectors?
do you have the latest firmware updtae?  it often helps
btw - hddreg is not for SSD drives, afaik
0
 
hrolsonsAuthor Commented:
Yes, it had bad sectors, I contacted the manufacturer and they said to upgrade the firmware which I did.  No bad sectors reporting initially and then after about a week of use bad sectors started showing up and they are going to replace the drive with a different model.
0
 
nobusCommented:
tx for feedback   -first time i came across that one...
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

  • 14
  • 9
  • 4
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now