Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random blue screens after updating 7200.12 firmware(ntoskrnl.exe)


30 Oct 2011   #1

Windows 7 Service Pack 1 64 bit
 
 
Random blue screens after updating 7200.12 firmware(ntoskrnl.exe)

Just updated to the CC49 firmware, think I failed a chkdsk (was out of the house at the time) and have had a couple of random blue screen errors which I believe are being caused by the hard drive. I'm running Seatools test currently, but if anyone would be kind enough to check out my DMP files, perhaps there is something else to blame?


Thanks,

Dan.



Full retail 64 bit SP1

my specs ; Imageshack - danspec.png

My System SpecsSystem Spec
.

30 Oct 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Picklesnipe View Post
Just updated to the CC49 firmware, think I failed a chkdsk (was out of the house at the time) and have had a couple of random blue screen errors which I believe are being caused by the hard drive. I'm running Seatools test currently, but if anyone would be kind enough to check out my DMP files, perhaps there is something else to blame?


Thanks,

Dan.



Full retail 64 bit SP1

my specs ; Imageshack - danspec.png
Memory corruption Probably from a driver please run these two tests.

Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.


*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+



2-Driver verifier


Quote:
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable
My System SpecsSystem Spec
30 Oct 2011   #3

Windows 7 Service Pack 1 64 bit
 
 

Sorry ZigZag not to doubt your knowledge but did you attain that it was memory corruption from my DMP file?


These RAM sticks are brand new, btw
My System SpecsSystem Spec
.


30 Oct 2011   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Picklesnipe View Post
Sorry ZigZag not to doubt your knowledge but did you attain that it was memory corruption from my DMP file?


These RAM sticks are brand new, btw
Picklesnipe

I wish more people would question the results because they are the ones who learn and dont have them again.

Yes it did come from the dmp

BugCheck 109, {a3a039d89598b63a, b3b7465ee8158590, fffff800031011e0, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------


basically I want you to run those two tests to find out if it is memory or a driver giving bad data to the memory.

The first test (memtest) tests the memory outside of windows so no drivers affect it

The second tests the drivers inside the windows environment.

Hope that answers your question.

Ken
My System SpecsSystem Spec
31 Oct 2011   #5

Windows 7 Service Pack 1 64 bit
 
 

I should also note that I left a Seagate long generic test going on over night, but when I woke up I had blue screened. Now, this may have been caused by memory, i'm not sure.



I'm running Memtest on my build currently, i'm at college so I will report back later with results (it'll have about 8 hours to run). I should add that I have a i5 2500k (stock) and the ram is also at stock, but perhaps I need to manually change the timings/voltage. It had been running well before the hard drive firmware update...

I'll also give the driver verifier a whirl...



Is it in any way possible that I suffered memory/driver corruption after updating my HDD firmware? The hard-drive itself seems to be working fine since the update, but I hadn't BSOD'd at all before the update.
My System SpecsSystem Spec
31 Oct 2011   #6

Windows 7 Service Pack 1 64 bit
 
 

Update;





8 hours memtest and not a single error!



How can it be that I am getting memory errors yet my memory is apparently working perfectly?



Edit:
I am getting system lockups when putting the HDD under stress (playing music and opening an app)
My System SpecsSystem Spec
31 Oct 2011   #7

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Picklesnipe View Post
Update;





8 hours memtest and not a single error!



How can it be that I am getting memory errors yet my memory is apparently working perfectly?



Edit:
I am getting system lockups when putting the HDD under stress (playing music and opening an app)



Easy. Memory corruption can also occur when a driver passes bad data. Thats why We want you to run driver verifier.

Memtest tests the ram outside windows so it just tests the memory.

Driver verifier tests inside windows so it tests the drivers.


If you feel it is the HD (it isnt) run this chkdsk

A- CHKDSK /R /F:

Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.

Do this for each hard drive on your system.

When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

Then reboot and let the test run.

It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.

See "CHKDSK LogFile" below in order to check the results of the test.


B- Elevated Command Prompt:


Go to Start and type in "cmd.exe" (without the quotes)

At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"


C-CHKDSK LogFile:


Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter

Expand the Windows logs heading, then select the Application log file entry.

Double click on the Source column header.

Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).

Copy/paste the results into your next post.
My System SpecsSystem Spec
Reply

 Random blue screens after updating 7200.12 firmware(ntoskrnl.exe)




Thread Tools



Similar help and support threads for2: Random blue screens after updating 7200.12 firmware(ntoskrnl.exe)
Thread Forum
Blue Screens and Pop Ups Galore (Ntoskrnl.exe) BSOD Help and Support
Various blue screens, mainly caused by ntoskrnl.exe BSOD Help and Support
computer blue screens often dump report mentions this ntoskrnl.exe BSOD Help and Support
seemingly random blue screens and random codes BSOD Help and Support
Frequent Blue Screens, ntoskrnl.exe BSOD Help and Support
Random blue screens - ntoskrnl.exe+70740 BSOD Help and Support
ntoskrnl.exe causing blue screens and freezes BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 05:45 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33