Random BSOD and Windows freeze

Hello everybody,

Like the title say, i have random BSOD and windows freeze. I can have 1 a day or 4-5 in 30 minutes. It happen at aniytime, when i'm listening music, surfing the net, playing games, working with Excell or Words, etc. Sometimes, when a BSOD occur, i have to make reset because the computer is frozen. I sent bak the PC where i bought it but nobody found the problem.. I tried a memtest but everything was ok.

Spec:
OS: Windows 7 Premium
Intel Pentium Core Duo E8400 3GHZ
Antec NSK4480 380 Watts
Motherboards Intel DG41TY
2 Gig DDR2 800MHZ KVR
HD: 320 Gig W..D 7200 RPM
DVD Burner LG Multi-mode 22X
Sound Intel HD 5.1
Intel Chipset G35 Express replace by Ati Radeon X1650 PCI Express

Hope everything is ok since its the 1st time i post but i tried to follow the BSOD posting instruction and sorry for my bad english

thanks
JC

These crashes were caused by memory corruption (probably a driver). Please run this two test to find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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/Win7 Startup Repair feature).

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 "Special Pool", "Force Pending I/O Requests" and "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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users

https://www.sevenforums.com/crashes-d...tructions.html? Noticed you tried to upload; if you are having problems uploading, try to do so on another computer.

yes i'll try again..

Code:

Loading Dump File [F:\Kingston\BSODDmpFiles\jcbourgault\Windows_NT6_BSOD_jcgriff2\013012-17971-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c04000 PsLoadedModuleList = 0xfffff800`02e49670
Debug session time: Mon Jan 30 14:24:35.854 2012 (GMT-7)
System Uptime: 0 days 0:00:23.368
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5003, fffff70001080000, 30ed, 3974000072f0}

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

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 00000000000030ed
Arg4: 00003974000072f0

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_5003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002c1474c to fffff80002c80c40

STACK_TEXT:  
fffff880`02895a78 fffff800`02c1474c : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`000030ed : nt!KeBugCheckEx
fffff880`02895a80 fffff800`02c7ed6e : 00000000`00000001 00000000`04ce5000 00000000`00000001 00000000`04ce0040 : nt! ?? ::FNODOBFM::`string'+0x46f0d
fffff880`02895be0 000007fe`f9d72430 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`032cdeb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f9d72430


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+46f0d
fffff800`02c1474c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+46f0d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+46f0d

BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+46f0d

Followup: MachineOwner
---------

How many passes did you run memtest for before? It needs to run for at least 7. Also, sometimes it must be run a second or third time to find errors; one day it passes, the next it fails.

Please 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).



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. Run Driver Verifier

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 System Restore 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.