Random BSOD on Windows 7 x64

Toggle sidebar Toggle sidebar
B

Bodies

Honorable
Jul 31, 2013
20
0
10,510
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.
 
Solution
C
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.
Sort by date Sort by votes
C

chriss000

Distinguished
Feb 24, 2010
696
0
19,160
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.
 
Upvote 0 Downvote
Solution
B

Bodies

Honorable
Jul 31, 2013
20
0
10,510

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


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

Thank you for the quick responses


 
Upvote 0 Downvote
B

Bodies

Honorable
Jul 31, 2013
20
0
10,510
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.
 
Upvote 0 Downvote
B

Bodies

Honorable
Jul 31, 2013
20
0
10,510
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.

 
Upvote 0 Downvote
clutchc

clutchc

Titan
Ambassador
Apr 22, 2009
43,150
411
131,790
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.html

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.
 
Upvote 0 Downvote
B

Bodies

Honorable
Jul 31, 2013
20
0
10,510
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!
 
Upvote 0 Downvote
B

Bodies

Honorable
Jul 31, 2013
20
0
10,510
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
 
Upvote 0 Downvote
clutchc

clutchc

Titan
Ambassador
Apr 22, 2009
43,150
411
131,790
(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.
 
Upvote 0 Downvote
clutchc

clutchc

Titan
Ambassador
Apr 22, 2009
43,150
411
131,790
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.
 
Upvote 0 Downvote
B

Bodies

Honorable
Jul 31, 2013
20
0
10,510
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 :)
 
Upvote 0 Downvote
clutchc

clutchc

Titan
Ambassador
Apr 22, 2009
43,150
411
131,790
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.
 
Upvote 0 Downvote
B

Bodies

Honorable
Jul 31, 2013
20
0
10,510
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?
 
Upvote 0 Downvote
B

Bodies

Honorable
Jul 31, 2013
20
0
10,510
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.
 
Upvote 0 Downvote
B

Bodies

Honorable
Jul 31, 2013
20
0
10,510
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.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom