BSODS always when cold boot...

A

ArgentineBoy

New member
Member
Local time
4:38 PM
Messages
89
So,always the same with my machine,first time I boot the PC in the day,BSOD,wait for a few other BSODS and then,everything fine.
Of course,when this happens to my Dad,while he's working,he's not very happy,so as to try to fix this,I'll leave some BSODS here.

Memory is 10 points,no problems.
Temperature is also fine,always below 60 degrees (celcius)

Thanks for helping.
 

My Computer

Computer Manufacturer/Model Number
Self-Made
OS
W7 ULTIMATE 64b
CPU
Intel i5 750 2.6GHZ
Motherboard
GIGABYTE H55M-USB3 REV 1.0
Memory
G.SKILL RIPJAWS 2GB 1333MHZ 8-8-8-24 4GB (2x2)
Graphics Card(s)
XFX HD5850 XXX (Factory OC'ed) @ 1150/750
Sound Card
On Board
Monitor(s) Displays
Ehhhh,one of those Toshiba '17 LCD
Hard Drives
1x old samsung 120 gb 7200
1x WD BLACK 500 GB 7200
PSU
Thermaltake 600W TR2-600
Case
CM690
Cooling
Geez,3 80mm (back,side,front)
ArgentineBoy said:
So,always the same with my machine,first time I boot the PC in the day,BSOD,wait for a few other BSODS and then,everything fine.
Of course,when this happens to my Dad,while he's working,he's not very happy,so as to try to fix this,I'll leave some BSODS here.

Memory is 10 points,no problems.
Temperature is also fine,always below 60 degrees (celcius)

Thanks for helping.
Click to expand...

Virtually all of them are caused by memory corruption. Probably caused by a driver.

Please run memtest and driver verifier

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

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.



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

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.
Click to expand...
 

My Computer

Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
If you're having cold boot issues you might not get errors when running memtest. Do what zigzag suggested and run the tests. If you get no errors then shut down the computer for the night and then in the morning boot into memtest and run it again. You most likely will get tons and tons of errors. If you do then you can try adjusting the memory settings in the BIOS and see if they help with the cold boot BSODs.

BSOD BUGCHECK SUMMARY
Code: 
[FONT=lucida console]
Built by: 7600.16792.x86fre.win7_gdr.110408-1633
Debug session time: Fri May 20 13:00:06.632 2011 (UTC - 4:00)
System Uptime: 0 days 0:09:31.600
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0x4E_99_nt!MiBadShareCount+24
BiosReleaseDate = 11/01/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = H55M-USB3
CPUID:        "Intel(R) Core(TM) i5 CPU         750  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16792.x86fre.win7_gdr.110408-1633
Debug session time: Fri May 20 12:49:38.378 2011 (UTC - 4:00)
System Uptime: 0 days 0:11:17.736
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  0x1a_41790_nt!MiDeleteVirtualAddresses+41a
BiosReleaseDate = 11/01/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = H55M-USB3
CPUID:        "Intel(R) Core(TM) i5 CPU         750  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16792.x86fre.win7_gdr.110408-1633
Debug session time: Wed May 18 10:24:18.933 2011 (UTC - 4:00)
System Uptime: 0 days 0:11:15.275
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  0x1a_41790_nt!MiDeleteVirtualAddresses+41a
BiosReleaseDate = 11/01/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = H55M-USB3
CPUID:        "Intel(R) Core(TM) i5 CPU         750  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16792.x86fre.win7_gdr.110408-1633
Debug session time: Sun May 15 13:39:43.305 2011 (UTC - 4:00)
System Uptime: 0 days 0:23:32.647
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  0x1a_5003_nt!MiAllocateWsle+6f
BiosReleaseDate = 11/01/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = H55M-USB3
CPUID:        "Intel(R) Core(TM) i5 CPU         750  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16792.x86fre.win7_gdr.110408-1633
Debug session time: Sat May 14 11:20:38.776 2011 (UTC - 4:00)
System Uptime: 0 days 0:10:12.744
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  wmpnscfg.exe
FAILURE_BUCKET_ID:  0x1a_41790_nt!MiDeleteVirtualAddresses+41a
BiosReleaseDate = 11/01/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = H55M-USB3
CPUID:        "Intel(R) Core(TM) i5 CPU         750  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]
 

My Computer

Computer Manufacturer/Model Number
Self Built
OS
Windows 7 Home Premium 64bit
CPU
Intel Core i5-2500 @ 3.8GHz
Motherboard
MSI P67A-GD65
Memory
G.SKILL Ripjaws Series 8GB (2 x 4GB) DDR3 1600
Graphics Card(s)
NVIDIA GTX 550Ti
Sound Card
On Board
Monitor(s) Displays
ASUS 23"
Hard Drives
OCZ Vertex 3 VTX3-25SAT3-60G
Keyboard
Wireless
Mouse
Wireless
mgorman87 said:
If you're having cold boot issues you might not get errors when running memtest. Do what zigzag suggested and run the tests. If you get no errors then shut down the computer for the night and then in the morning boot into memtest and run it again. You most likely will get tons and tons of errors. If you do then you can try adjusting the memory settings in the BIOS and see if they help with the cold boot BSODs.

BSOD BUGCHECK SUMMARY
Code: 
[FONT=lucida console]
Built by: 7600.16792.x86fre.win7_gdr.110408-1633
Debug session time: Fri May 20 13:00:06.632 2011 (UTC - 4:00)
System Uptime: 0 days 0:09:31.600
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0x4E_99_nt!MiBadShareCount+24
BiosReleaseDate = 11/01/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = H55M-USB3
CPUID:        "Intel(R) Core(TM) i5 CPU         750  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16792.x86fre.win7_gdr.110408-1633
Debug session time: Fri May 20 12:49:38.378 2011 (UTC - 4:00)
System Uptime: 0 days 0:11:17.736
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  0x1a_41790_nt!MiDeleteVirtualAddresses+41a
BiosReleaseDate = 11/01/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = H55M-USB3
CPUID:        "Intel(R) Core(TM) i5 CPU         750  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16792.x86fre.win7_gdr.110408-1633
Debug session time: Wed May 18 10:24:18.933 2011 (UTC - 4:00)
System Uptime: 0 days 0:11:15.275
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  0x1a_41790_nt!MiDeleteVirtualAddresses+41a
BiosReleaseDate = 11/01/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = H55M-USB3
CPUID:        "Intel(R) Core(TM) i5 CPU         750  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16792.x86fre.win7_gdr.110408-1633
Debug session time: Sun May 15 13:39:43.305 2011 (UTC - 4:00)
System Uptime: 0 days 0:23:32.647
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  0x1a_5003_nt!MiAllocateWsle+6f
BiosReleaseDate = 11/01/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = H55M-USB3
CPUID:        "Intel(R) Core(TM) i5 CPU         750  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16792.x86fre.win7_gdr.110408-1633
Debug session time: Sat May 14 11:20:38.776 2011 (UTC - 4:00)
System Uptime: 0 days 0:10:12.744
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  wmpnscfg.exe
FAILURE_BUCKET_ID:  0x1a_41790_nt!MiDeleteVirtualAddresses+41a
BiosReleaseDate = 11/01/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = H55M-USB3
CPUID:        "Intel(R) Core(TM) i5 CPU         750  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2666
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]
Click to expand...
Ok,thanks for suggestions and info.
But,what if the BSOD are made along with the standard settings for my mem (8-8-8-24;1.5v,Double Channel)?
If I change those values then things could go FUBAR.
 

My Computer

Computer Manufacturer/Model Number
Self-Made
OS
W7 ULTIMATE 64b
CPU
Intel i5 750 2.6GHZ
Motherboard
GIGABYTE H55M-USB3 REV 1.0
Memory
G.SKILL RIPJAWS 2GB 1333MHZ 8-8-8-24 4GB (2x2)
Graphics Card(s)
XFX HD5850 XXX (Factory OC'ed) @ 1150/750
Sound Card
On Board
Monitor(s) Displays
Ehhhh,one of those Toshiba '17 LCD
Hard Drives
1x old samsung 120 gb 7200
1x WD BLACK 500 GB 7200
PSU
Thermaltake 600W TR2-600
Case
CM690
Cooling
Geez,3 80mm (back,side,front)
Have you manually set those values or is everything on auto? If your memory is set correctly in the BIOS then leave it for now and run the tests. Sometimes tweaking the voltage up a tiny bit can help with memory BSODs
 

My Computer

Computer Manufacturer/Model Number
Self Built
OS
Windows 7 Home Premium 64bit
CPU
Intel Core i5-2500 @ 3.8GHz
Motherboard
MSI P67A-GD65
Memory
G.SKILL Ripjaws Series 8GB (2 x 4GB) DDR3 1600
Graphics Card(s)
NVIDIA GTX 550Ti
Sound Card
On Board
Monitor(s) Displays
ASUS 23"
Hard Drives
OCZ Vertex 3 VTX3-25SAT3-60G
Keyboard
Wireless
Mouse
Wireless
You must log in or register to reply here.
Back
Top