Sign in with
Sign up | Sign in
Your question
Solved

Random BSOD on Windows 7 x64

Last response: in Windows 7
Share
July 31, 2013 1:44:10 PM

Hello.
I've been experiencing some weird bluescreens lately and I can't figure out what's causing them. I have ran both Memtest and Windows Disk-Check without any errors, have reinstalled drivers, removed antivirus, etc.. However they still keep happening like one each day when I'm not even using the computer for gaming or something else they might stress it. Yesterday it happened while watching a video using BSPlayer and today when I was having dinner.
This is what WhoCrashed tells me for the three last ones:

"Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 31-07-2013 20:24:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-20498-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41201, 0xFFFFF68000032DA8, 0xF4100000A8B09867, 0xFFFFFA80067F1900)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 31-07-2013 20:24:32 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF68000032DA8, 0xF4100000A8B09867, 0xFFFFFA80067F1900)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 29-07-2013 23:43:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-18392-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFFA0008078750, 0x0, 0xFFFFF8000399B7CA, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. "

They all seem to be related to "ntoskrnl.exe". I couldn't manage to fix it myself so I had to call the cavalry. :) 
Someone has any ideas?

My setup is: i5 750@3.1ghz, Asus P7P55D-Pro, 2x4GB Gskill Ripjaws, Asus GTX650 TC (however I just noticed it says Nvidia GeForce GTX 650 on device manager)

Thank you.
a b $ Windows 7
July 31, 2013 1:54:44 PM

Yes, the problem seems Windows Kernel related. Since you already verified the RAM was fine, we can eliminate that. Can you do a windows repair from the original installation disk?
m
0
l

Best solution

July 31, 2013 1:56:00 PM

eliminate hardware problems 1 at a time. Run for 3 days with one ram stick, run for 3 days with the other ram stick, run for 3 days on onboard gpu.
If none of this works re install windows. If it still crashes I am out of ideas.
Share
Related resources
July 31, 2013 2:04:16 PM

clutchc said:
Yes, the problem seems Windows Kernel related. Since you already verified the RAM was fine, we can eliminate that. Can you do a windows repair from the original installation disk?

I am doing a sfc /scannow right now just to double check if something's up. If it comes clear I'll try that.

chriss000 said:
eliminate hardware problems 1 at a time. Run for 3 days with one ram stick, run for 3 days with the other ram stick, run for 3 days on onboard gpu.
If none of this works re install windows. If it still crashes I am out of ideas.

Meanwhile if nothing else fixes it, I'll run memtest over night and post updates.

Thank you for the quick responses


m
0
l
July 31, 2013 2:11:45 PM

The sfc /scannow told me something weird at the end:
"Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.log windir/Logs/CBS/CBS.log. For example C:\Windows\Logs\CBS\CBS.log
The system file repair changes will talke effect after the next boot."

I opened the file and it is huge, if you want me to post some information that it has please tell me.
m
0
l
a b $ Windows 7
July 31, 2013 2:12:32 PM

Good idea on the SFC run.
m
0
l
July 31, 2013 2:31:08 PM

Tried the repair feature and it said that the system recovery options on the CD are not compatible with this version of Windows. Weird. Also when I booted back into Windows I got insta bsod.

On Wed 31-07-2013 21:23:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-16848-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000375B7E5, 0xFFFFF8800A6C6C80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

m
0
l
a b $ Windows 7
July 31, 2013 3:11:03 PM

Well... if you can't use the Win7 repair, you are in a bit of a pickle. You may be forced to do a clean install of Win7.

Before giving up, try running CCleaner in case it is a corrupted registry problem: http://www.piriform.com/ccleaner/download
(if you can boot now, that is)

If still no joy, try Driver Sweeper from Safe Mode in case it is indeed a driver issue. I would start by uninstalling my gfx driver, then boot to DS in SM, and have it remove any Nvidia, AMD, ATI GRAPHICS driver remnants it finds. Re-boot and install the latest driver for your card.
http://www.techspot.com/downloads/4266-driver-sweeper.h...

While in DS, see if there are any old remnants from other device drivers you no longer need. I once had some old HP printer driver remnants that were messing up my system from back when I used to have an older HP printer.
m
0
l
July 31, 2013 3:38:22 PM

CCleaner had a good time on my computer. It had an enormous list of things it removed and repaired. After it rebooted, I went into SM and did what you said and interestingly enough I had some old HP printer drivers there aswell as some Nvidia and Asus ones. I am now doing a fresh install of the GPU drivers.
I hope it ceases the bluescreens since both the CCleaner and DS removed a lot of stuff.

I'll keep this topic updated.
Thanks a lot clutchc!
m
0
l
a b $ Windows 7
July 31, 2013 3:43:55 PM

Don't get carried away and do too much at once. Too much "cleanup" can result in losing something important. ;-)
But, yeah, stay in touch.
m
0
l
August 1, 2013 7:57:18 AM

Sadly, the bsod's continued. I formatted windows just to make sure it wasn't any driver problems and I got some weird bluescreens.

System Information (local)
--------------------------------------------------------------------------------

computer name: HUGO-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 6440411136 total
VM: 2147352576, free: 1990172672




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 01-08-2013 00:54:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080113-21278-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41287, 0x8158, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 01-08-2013 00:54:56 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41287, 0x8158, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 01-08-2013 00:51:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080113-26052-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x4E (0x99, 0x21CB0A, 0x6, 0x100000001)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I added the other 2x2gbs of ram I had taken out thinking they were broken and ran memtest for 9 hours straight. 0 errors and no BSOD since. I don't know if it fixed anything but I have a feeling this computer was RAM oc'd in the store I bought it. Here's some cpu-z screenshots:
http://img547.imageshack.us/img547/5720/9osg.jpg
http://img163.imageshack.us/img163/8339/f3ky.jpg
http://img594.imageshack.us/img594/1586/0cra.jpg
http://img547.imageshack.us/img547/7937/j56c.jpg
Task Manager:
http://img838.imageshack.us/img838/4330/9zlz.jpg

My ram is http://www.gskill.com/en/product/f3-10666cl9d-4gbxl- and http://www.gskill.com/en/product/f3-14900cl9d-8gbxl .

Thank you in advance
m
0
l
a b $ Windows 7
August 1, 2013 8:07:52 AM

Aha! You may have a point there. Have you tried resetting your BIOS to its default settings? That will reset the RAM to stock. Unless you know how to do that yourself in BIOS.
m
0
l
August 1, 2013 8:30:52 AM

My bios doesn't show the values for each ram dimm, even when I'm checking the ram frequency on bios it only shows 1333mhz that regards the 2x2GB and not the 2x4GB I have also installed; same thing with clocks (only shows 9-9-9-24).
By resetting bios do you mean this? http://www.asus.com/Motherboards/P7P55D_PRO/#support_Kn...
m
0
l
a b $ Windows 7
August 1, 2013 12:35:11 PM

(Man, Asus really need to get someone with a better grip on the English language to write that stuff)

Yes, but that would be the "hatchet" method rather than the "scalpel" method though. After doing that, you'll have to re-enter BIOS and reset your date/time and any other changes you may have had.

But looking at the pics of your RAM sticks in CPU-Z, I see a problem you are going to have in spite of anything you may do. (1) You have mismatched memory timings. It's good that you are keeping matching pairs in each channel, but the pairs aren't matched between each other. That spells trouble for dual channel memory systems. (2) your sizes are mismatched. So only 8gb is being mapped as dual channel, leaving the rest run as single channel. (3) you are mixing XMP 1.2 and 1.3. Not sure that's good. Leave out the 2 x 2GB sticks for now. Put the 2x4GB sticks in the A1,B1 slots.

Look at the memory in CPU-z under the memory tab rather than the SPD tab. The memory tab should show actual values while in service.
m
0
l
August 1, 2013 1:23:35 PM

http://img62.imageshack.us/img62/2038/h7o1.jpg
Here is the memory tab. I'll try doing that if another bsod happens.
If it happens and I change my total ram to 2x4GB (that were previously memtested along with the other 2x2gb ones) and put them in A1 and B1, do I need to run memtest again? Just to be sure.

Thank you for the help
m
0
l
a b $ Windows 7
August 1, 2013 3:48:25 PM

If you've never run memtest on the 2 x 4GB sticks, yes. I would... to prove they are good. Again, 1 pass on each stick in the 1st slot individually so that if an error shows up, you can tell which stick it is in.

Your CPU-Z/memory tab obviously is with both pairs in. That is what should happen. They all default to the lesser sticks' speed and timings. And it is running as single channel. That is odd, unless CPU-Z is just generalizing. There should be 8GB @ dual channel and 4GB at single channel. Maybe that board defaults to single channel for the whole lot, I don't know. But single channel is slightly slower than dual channel. So if it were mine, I'd go for 8GB at dual channel rather than 12GB at single channel. Unless you have other needs for the extra memory, no game I know of even uses all of the 8GB.
m
0
l
August 1, 2013 6:23:12 PM

Makes sense, I'm gonna do that tomorrow and report back.
Thank you a lot for the help so far :) 
m
0
l
August 2, 2013 6:46:14 AM

Ok I just tested each dimm (of the 2x4gb set) on the A1 slot for 1 pass and 0 errors. After that I installed both, went into bios and changed a couple of settings to match the ram defaults as it says on the sticker. In the bios, DRAM Frequency was 1333mhz and I put it into auto since these work at 1866mhz and the max option was like 1600mhz; and the clocks I changed them to 9-10-9-28. Today I'll test the computer to see if its stable now.
I'll add some cpu-z pics here just to make sure everything's ok:
http://img801.imageshack.us/img801/4787/abzc.jpg
http://img823.imageshack.us/img823/9116/pjp5.jpg

Thank you :) 
m
0
l
a b $ Windows 7
August 2, 2013 9:57:05 AM

Did you ever say what make/model motherboard you had? Just scrolled back up and didn't see it.
Edit: was it the Asus P7P55D PRO
m
0
l
a b $ Windows 7
August 2, 2013 10:16:02 AM

Did you ever reset your BIOS to the default values? If not, I would go into BIOS and save the settings you have now to one of your profiles so you can come back to it later. Then go to the exit screen and load the default values. You may have to make a few changes to that depending on what you did at the beginning to install Windows. Example: You may have set your SATA controller to AHCI instead of IDE. And you may have changed your boot order. But mainly we want all the MB/memory values to be at default.

Your CPU-Z memory values don't look like what I would expect. Doubling that 482MHZ (DDR) only gives you 964MHZ memory speed. I would expect you to be at either the controller's default 1333MHZ or the memory's default 1600MHZ.
m
0
l
August 2, 2013 10:55:01 AM

No I didn't. Everything else besides the CPU BCLK values and what I just changed in the DRAM tab to match what the stickers on the RAM say is default.
Should I change the DRAM Frequency to 1600mhz, 1333mhz or keep it at Auto?
m
0
l
a b $ Windows 7
August 2, 2013 11:43:08 AM

Since we are trying to isolate a problem right now, I would start at auto. That should put the memory at the rated speed; 1600MHZ. If there's no joy after that, set it at 1600MHZ.

Wait. Why is your BCLK not at default?
m
0
l
August 2, 2013 12:52:06 PM

My CPU has always been overclocked. Never caused any problems.
I think I'll leave my settings alone for now since this is the third day I haven't had any BSOD. I think the RAM fix was the nail in the coffin and the rest was probably just old drivers causing conflicts.
m
0
l
a b $ Windows 7
August 2, 2013 2:46:53 PM

OK. I can see you not wanting to mess with it if it is behaving now. But just out of curiosity, what processor are you using and what is the BCLK set at?
I take it you didn't O/C it yourself.
m
0
l
August 2, 2013 4:47:26 PM

i5 750 @ 3.1ghz 42ºc idle/65ºc~ load
I looked into it for a few months and I decided to try it some time ago. Worked out fine. From what I've read, I guess P7P55D-PRO is a good match for this cpu.
m
0
l
a b $ Windows 7
August 2, 2013 5:48:08 PM

You looked into what?

And you didn't mention what the BCLK was set at.
m
0
l
August 2, 2013 6:20:28 PM

Into overcloking this cpu. BCLK is set at 160.
m
0
l
a b $ Windows 7
August 2, 2013 6:38:20 PM

A BCLK of 160 on the i5-750 is a fairly high BaseCLocK. My 2nd machine is an i7-870/Biostar TPower i55. Basically it's the same Lynnfield CPU as yours w/higher multi. That is about the max BCLK I have been able to get to run stable. I didn't know before that you had it O/C'd. Or maybe it didn't register with me. But if you have any more BSOD issues, I would almost bet that your O/C is the problem.

That explains the odd memory freq. Did you lower the other components' multipliers that run from the base clock? Any voltage changes you made?
m
0
l
August 3, 2013 5:04:43 AM

No, I didn't change any voltage settings. Keep in mind that when I bought this pc, it came with 3.7ghz clock which ran stable for like 1.5 years. I only changed it because it's very hot this month where I live so the temps were getting a little crazy and I decided to lower it to a reasonable clock.
m
0
l
August 4, 2013 5:53:21 PM

Well, guess what. When I thought it was solved, it said hello again.

On Mon 05-08-2013 00:16:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-26800-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC5002EAE8, 0x98100001C9408820, 0xFFFFF67C5002EAE9)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 05-08-2013 00:16:43 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC5002EAE8, 0x98100001C9408820, 0xFFFFF67C5002EAE9)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 05-08-2013 00:14:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-19484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFFA80C2433180, 0x0, 0xFFFFF80002AB8EA5, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I also tried to upload dumpfiles from Driver Verifier to a public site:
http://www.filedropper.com/desktop_1

My apologies if this forum has a file attachment system but I couldn't find it.
Thank you
m
0
l
a b $ Windows 7
August 4, 2013 6:27:56 PM

Set the BCLK back to default. In fact, set the entire BIOS back to default. You can save your current settings first, if you want.

Then test the system for a few days. See if the crashes go away.
m
0
l
August 4, 2013 6:52:03 PM

I just changed it to system default in bios. Let's see what happens.
Also, was the minidump useful or there's no use for me to keep attaching that if it happens again?
m
0
l
a b $ Windows 7
August 4, 2013 7:18:10 PM

Yes and no. The dump might be more valuable to someone that knows its interpretation better than me. It is indicating a memory error. But a memory error can be caused by too fast a base clock. The memory runs off the base clock like most other components in the PC.

Now that you have the BIOS set to default values, what does the memory tab of CPUZ look like?
m
0
l
a b $ Windows 7
August 4, 2013 7:40:21 PM

OK. IT is running at the memory controller's default of 1333MHZ now. I'd leave it there for the test. You can always go into BIOS and choose 1600MHZ later or whatever you want to do.

Do you think there were any other changes to the BIOS other than the bclk and memory?
m
0
l
August 4, 2013 7:47:43 PM

Not that I know of. When I bought my computer 3 years ago or something, the store added a stable oc for the setup I had (which was with different RAM and GPU). Since then I did not mess with the bios settings, until last year or something when I changed cpu's bclk to get 3.7ghz (before I added new ram+new GPU too).
m
0
l
a b $ Windows 7
August 4, 2013 8:05:35 PM

Oh. More info comes to light. You changed the RAM from the sticks that were in when they set the O/C? That may have disrupted things. Different timings possibly.
And you say the store did an O/C for you. That means they modified settings in BIOS. Settings you probably aren't aware of. I hope you saved the original BIOS settings so you can go back to it if you desire.
m
0
l
August 5, 2013 4:32:07 AM

I didn't save them. Right now I just want to get to the bottom of this and get my computer running stable. After that, I'll look into safely oc'ing with my current setup.
Yea but I changed the timings myself in the bios to what it said in the sticker, same with voltages. Maybe it was some other setting I wasn't aware of that was causing instability. Again, it's too soon to be sure that that was the problem since I already thought the problem was solved 2 or 3 times before when my computer ran without problems for like 2 or 3 days and then bsod. The interesting part is that after the first BSOD happens, it looks like it opens the bsod gates and makes booting into Windows almost impossible.
m
0
l
!