BSOD while doing certain things..

[writhziden]

Those are the files we have been asking for and that are included if you follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html.

 

[DevilJho]

sigh, I noted this minidump folders in my laptop..
but my home PC just doesn't have them..

this is really frustrating..

and my system hung for like twice after trying to emulate what made my system BSOD..

the thing is, on one of the tries (I enabled Minidump instead of kernel dump),
the BSOD shows creation of dump file to 100, and the system restarted itself after it hit 100.

but when log in to windows, no DMP files anywhere in C:\windows\.
I even search the entire hard disk for *.dmp.. No luck..

are there anything that could have prevented the DMP files from being created?

 

[writhziden]

are there anything that could have prevented the DMP files from being created?

Yes... :banghead:


post#18

 

[DevilJho]

Yes... :banghead:

yes what?

 

[writhziden]

See previous posts. I edited the last one...

 

[DevilJho]

sigh, guess I will run a chkdsk for all hard disk and do the memtest one more time..
this is gonna take such a long time..

feel like just reinstalling my whole damn windows.. LOL

 

[writhziden]

Make sure to run the Memtest86+ diagnostic for at least 7-10 passes. I have seen it take up to 21 passes to find errors before.

 

[DevilJho]

Make sure to run the Memtest86+ diagnostic for at least 7-10 passes. I have seen it take up to 21 passes to find errors before.

dang...

ok, will give it a go..
to hard disk check, do i have to run it on all HD or jutst the main one where i had my windows on?

the others are just for data storage, no apps or progs running from them.

 

[writhziden]

Run the disk checks on any drives that are connected to the system on a regular basis.

 

[DevilJho]

ok, this is the result of my chkdsk


CHKDSK is verifying files (stage 1 of 3)...
281344 file records processed. File verification completed.
67 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
320426 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
281344 file SDs/SIDs processed. Cleaning up 124 unused index entries from index $SII of file 0x9.
Cleaning up 124 unused index entries from index $SDH of file 0x9.
Cleaning up 124 unused security descriptors.
Security descriptor verification completed.
19542 data files processed. CHKDSK is verifying Usn Journal...
37600184 USN bytes processed. Usn Journal verification completed.
Windows has checked the file system and found no problems.

1953512447 KB total disk space.
147906796 KB in 106391 files.
62240 KB in 19543 indexes.
0 KB in bad sectors.
444227 KB in use by the system.
65536 KB occupied by the log file.
1805099184 KB available on disk.

4096 bytes in each allocation unit.
488378111 total allocation units on disk.
451274796 allocation units available on disk.

Internal Info:
00 4b 04 00 f8 eb 01 00 93 95 03 00 00 00 00 00 .K..............
6b 03 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 k...,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

**********************

nothing seems to be wrong with me HDD, right?

also, i will run memtest tonight when I'm off to sleep and let the memtest cook overnight.

will post the results tomorrow..

 

[writhziden]

Disk check looks clean. We'll see what happens with the memory diagnostics.

 

[DevilJho]

ok, I cooked the memtest overnight..
made seven passes and all seven passes is clean, no errors..

if you want me to post the snapshot for that, lemme know..

thanks..

so whats my best next step since my disk and mem looks clean

T.T

 

[DevilJho]

Amazing grace..
a minidump was created last night before I did the memtest..

and here it is, hope you guys can help me check it out..

 

[writhziden]

Please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with the full crash reports.

Interestingly, you have been asked for this information on all four pages of this thread now... Fourth time's a charm?

 

[DevilJho]

Please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with the full crash reports.

Interestingly, you have been asked for this information on all four pages of this thread now... Fourth time's a charm?

ouch, ok ok.. try and get those for you

 

[writhziden]

In the meantime: Your crash points to memory problems or driver conflicts.

• If you are overclocking any hardware, please stop.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 213901
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.

You already ran memtest86+ once for seven passes, so it is up to you whether you want to run it again. I would recommend it when you find time to run it again.

 

[DevilJho]

I tried the verifier once..

it BSOD on me once but again, it did not create a dump file..

I will cook the windows memory diagnostic overnight tonight and post the results out..
if still memory clean, then I will try and provide the other info u requested (for the fourth time)..

sigh..

 

[writhziden]

Sometimes having Verifier active on too many drivers at once can prevent .dmp files from being created. Try Verifier on only five non-Microsoft drivers at a time. Run that for 24-36 hours. Then try the next set of five. Run that for another 24-36 hours. Etc. Do so until you have tested all non-Microsoft drivers.

 

[DevilJho]

I've decided to screw it all and reinstall my windows
and see how it goes from there..

Thanks for all the suggestions but I think I will be back after the re-installation.
LOL

 

[writhziden]

Good luck!