Reinstalling windows OS does not solve the bsod. how to fix this bsod

jraju

jraju

Member
Joined
Aug 21, 2017
Posts
144
Hi, I raised a thread on system file checker forum and It has happened that I get unusual bsods .I just formatted and reinstalled the windows OS.
There is no log in the windows/memory.dmp as configured in the computer properties section in the startup repair tab sub heads.
I could not see any files in there.
Fortunately I have taken a screen shot with my android phone and herewith I submit the same for your perusal.
Normally I approach this forum only for sfc errors , but never get bsods. I think that it is a hardware driver issue. I do not know which driver is causing.
Hope that you help on this
This has occurred after the reinstallation of windows
 

Attachments

  • bsoderror.jpg
    bsoderror.jpg
    122.5 KB · Views: 13
I just saw the bugcheck in the screenshot - 0x124 - basically a machine check exception.

You have an unknown hardware error.

I doubt that this is a driver error.

Any new or changed hardware?

Regards. . .

jcgriff2
 
hi, Jc, thanks for your tips. I have changed the smps which only gives power supply to the system.

Yes , in software i had updated nvdia graphic drivers from a old driver by msoft to new version of nvidia from their website.
But let me confirm that I have chosen the correct drivers from their page.
But , how do I say that problem comes from this driver
Hi, jc, why there was no memory.dmp in the said folder as has been default in window 7 ultimate
I have enabled hidden files to be shown, but still could not locate the folder to know which went wrong.
can we find which hardware /driver is?
 
Sorry but I'm giving you a reality check based on your last post in this thread as well as this post.

Nobody can offer you any specific fix that is guaranteed to instantly solve your current BSOD problems. It may take time to get to the root cause at times with issues that are not as straight forward as others. We can give you suggestions that we hope will solve your problems, but we cannot guarantee it until proven by you applying it and looking out for future crashes.

At this moment I can give you a suggestion, but I cannot guarantee they will solve your problems. Due to the nature of your crashes, as explained by jcgriff2, it is likely that your problems cannot be solved until you swapped out the faulty component. Unfortunately, even knowing that it's likely a hardware problem the process of pinpointing to a specific component (in rare cases even multiple components) can also be a long-dreaded process.

I note that you ran 1 pass of memtest86 in your recent WU thread, but the instructions that were given recommended 8 passes. MemTest86 allows for up to 4 passes which means that I suggest that you run MemTest86 twice to get to 8 passes.
 
Hi, I ran the memtest allowing all the test to get the pass mark. Should I do another time. Is that what you meant?
I noted 10 pass and it produced the result and I stopped.
How do I run the memtest. Should I do anything more than what is described in the memory test tool instructions.
 
What you see is the memory being tested one time, but that's only 1 pass. You need to let memtest86 repeat that process until it stops running, and then do it again.
 
Hi, the double pass memtest is enclosed for your perusal. But it continues after 2 pass and I stopped the 3rd in the middle and took the photo.
I mentioned particular individual test for sfc /scannow.
I have already enclosed the bsod logs
 

Attachments

  • doublepassmemtest.jpg
    doublepassmemtest.jpg
    113 KB · Views: 8
Let memtest86 continue until it stops by itself.

It will stop after 4 passes have completed. Once it is stopped by itself, then you repeat it until memtest86 stops again. When 4 passes have been completed twice in a row and no errors show up either time, that's a better indication.
 
The main issue I noticed is dump generation failure, commonly a result of bad RAM or hard drive problems.
 
I have checked in computer advanced properties. Then I saw that default memeory dumb is for kernal memory dump and it is in windows folder sub folder memory.dmp. I find no file in that even after enabling all hidden files in view menu.
Then I have tried to create a small dump file in the windows folder and forcibly created a bsod to check if it is creating a minidump in the same path windows subfolder minidump.
I just opened the task manager and forced to end process wininit and got bsod screen. Now I checked the windows folder . A sub folder has been created with minidump and contain some sub folders including cbs, dpx etc etc.
I have checked thoroughly the windows folder , but could not find kernal memory dump folder
i am in windows 7.
But the problem of creating the bsod could not be done as it happens with other error code.
where i can see this memory.dmp is in kernel is not known to me
 
C:\Windows\MEMORY.dmp is a file, not a folder.
 
I enabled to show hidden file of known type and i could see a memory.dmp file of about 750kbs.
can I enclose it if that is the file you need
 
I don't see any added value in analyzing a crash that was manually initiated. It doesn't change the concerns about possible memory or hard drive problems.
 
Yes. You are correct. I downloaded windbg and used that to see something to what it contains. It is absolutely new to me.
anyway, found that it is related to the wininit, which I forcibly done to see if a dumb is created.
Probably,the memory.dmp was not created because it was in system folder protected.
I do not know. When I get the next bsod, I may be able to send the dmp.
 
The memory dump was not created because the system had problems generating it.
 
Feel free to use the report button below the post for such posts :-)
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top