critical structure bsod

[bigdog4215]

Hello everybody I'm pretty new to pc's and have been getting some bsod's and would appreciate some help.I see them mainly on start ups and last two I got were fixed with recovery options but I don't think that will be the end of them.The repair details said one was ntosknl.exe was corrupt and the second said ntfs was corrupt but it said both were repaired.So I guess I'm ready to learn something new.

 

[x BlueRobot]

Welcome to the forums bigdog4215,

[COLOR="Red"]BugCheck 24[/COLOR], {1904fb, fffff8800374ed48, fffff8800374e5a0, fffff80002a8ce16}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : [COLOR="red"]memory_corruption[/COLOR]

Usual causes:  Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

memory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

Scan for any missing, modified or corrupted protected Windows files with:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Remove:

Start Menu\Programs\AVG

AVG is known to cause BSODs, please remove the program using the official removal program:

• Download tools and utilities | AVG UK

 

[bigdog4215]

Sorry for the delay,been busy with work but the weekend is all mine.I'm running seatools for dos now,it passed the short test and the long test is in progress.I also uninstalled avg and would it be okay to install avast because I don't feel safe on the net without an antivirus.Is there anymore test in seatools for dos that I should run and I ran a seatools application on my desktop before I came here for help,should I rerun those as well.There was one test in seatools I didn't run because it said my hard drive could become unusable,should I run that one too.Thanks


system froze at 28%,how should I proceed

 

[x BlueRobot]

You already have MSE running on your system, having two anti-virus programs can cause serve conflicts and problems. For the Seagate, you will want to run the Basic Tests and the Long Test.

What program did it freeze upon? I would leave it running as long as possible, since chkdsk can seem to freeze on a certain percentage, but then it will complete itself.

 

[bigdog4215]

I had another crash and windows will not boot.I tried repairing and restoring and neither would work,would you suggest reinstalling windows.


well that is strange,I decided to try booting it up and it booted but I guess the system restore completed.I'm still getting bsods',how should I continue?

 

[bigdog4215]

here is this,hope it helps

 

[x BlueRobot]

Have you managed to complete any of the above tests?

 

[bigdog4215]

The check disc scan completed without any errors but it wasn't like a normal check disc that I usually run,it lasted about 30 seconds.The seatools smart scan,short scan,short generic and the long generic passed.I'm running the sfc scannow currently,I read somerwhere that the file checker should be ran 3 times.The crashing seems to be getting worse though and there is something else I noticed when I boot up.It looks like the cmd is started then goes away.

 

[x BlueRobot]

Scan for any malware:

• http://www.sevenforums.com/tutorials/166445-windows-defender-offline.html
• Anti-rootkit utility TDSSKiller

You may also want to scan for infections which could be causing problems for your system.

 

[bigdog4215]

I ran both and nothing found.The anti rootkit only ran for about a minute tops,is that normal?

 

[x BlueRobot]

Yeah it's completely normal, and can upload the results from SFC /SCANNOW command, and have you tried running CHKDSK from command prompt at boot?

Read Option 3 for uploading the results:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
• http://www.sevenforums.com/tutorials/682-command-prompt-startup.html

 

[bigdog4215]

I had to rerun the sfc cause when I brought the last one to the desk top it was empy and I'm gonna run check disc at boot right now.

 

[bigdog4215]

Chkdsk said windows did not find any problems but it said it failed to transfer logs with status 50

 

[x BlueRobot]

There doesn't seem to be any problems with your system files, and if no problems were found, then it should be fine to continue. Here's some explanation for the error code:

• failed to transfer logged messages to the event log with status 50 - Microsoft Community

 

[x BlueRobot]

memory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.

Follow these steps -

Test for any corrupted drivers, by running Driver Verifier for least 24 hours, stop the test if a BSOD occurs before this time frame. Driver Verifier will place stress on the drivers within your system, which will cause corrupted drivers to crash and hopefully be pinpointed.

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

:info: More Help and Information with Driver Verifier - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Memory:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

 

[bigdog4215]

It bsod again and now its trying to attempt repairing but it doesn't seem like its working.Its been trying for about 10 minutes now,any suggestions.


well it finished but was unsuccessful and asked me send or not send then clicked finish and it shut down.

 

[bigdog4215]

I booted back up and disabled driver verifier and used the sfc tool to create a file so here it is

 

[x BlueRobot]

[COLOR="Red"]BugCheck 109[/COLOR], {a3a039d8991b6504, b3b7465eeb9834ca, fffff80002b1afdd, 1}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+30d0 )

Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)

Complete the memory test, and then to beginning to test the CPU.

• http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

Enable "Round off checking" before the test (see first post below tutorial).

 

[bigdog4215]

I ran memtestx86 for 13 passes and no errors were found with both sticks of ram in,do I still need to test each stick individually.I was reading about the stress test with prime95 and it said I should monitor my temps but I do not know what would be considered high temps.

 

[x BlueRobot]

There seems to be no problems with your RAM, and I wouldn't recommend going above 80*C with Prime95.